Gitlab GitLab-Certified-CI-CD-Associate Answers

You are working on a project in GitLab that involves multiple environments (development, staging, production). Each environment requires different configurations and credentials. Recently, you’ve observed that the deployment to the production environment sometimes fails due to incorrect configurations being used. Which approach is best to ensure that each environment gets the correct configurations and credentials during deployment?

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 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 GitLab project that includes three environments: development, staging, and production. You need to ensure that any changes pushed to the develop branch are deployed to the development environment, changes to the staging branch go to the staging environment, and only approved changes from the main branch are deployed to production. How would you set up your GitLab CI/CD pipeline to handle these environment-specific deployments?

You want to integrate API Security Scanning into your GitLab CI/CD pipeline to automatically detect vulnerabilities in your APIs. What steps should you take to properly configure API Security Scanning?