Your team is using Infrastructure as Code (IaC) to manage cloud resources in a GitLab project. To enhance security, you want to ensure that all IaC files are scanned for potential vulnerabilities and misconfigurations during the CI/CD pipeline. What is the correct step to enable IaC scanning in GitLab?
You are responsible for deploying a large-scale application that requires different environments for development, staging, and production, all running on Kubernetes clusters. You need to ensure that each environment has its own namespace and deployment strategy within the same pipeline. Which approach would best suit this scenario in GitLab CI/CD?
You want a child pipeline to run only if the parent pipeline's test stage is successful. Which configuration ensures this conditional execution in your GitLab CI/CD setup?
You are managing a complex GitLab CI/CD pipeline for a project that has multiple stages including build, test, and deploy. The build stage must compile the code, the test stage should run unit tests, and the deploy stage should push the code to a staging server. However, the deploy stage should only run if the build and test stages are successful. How can you ensure that the deploy stage only runs after the successful completion of the build and test stages?
In GitLab CI/CD, different types of executors can be used to run jobs in different environments. Which of the following is an uncommon executor for running CI/CD jobs in GitLab?