Free Gitlab GitLab-Certified-CI-CD-Associate Exam Questions

You are managing a complex GitLab CI/CD pipeline that involves multiple stages and needs to deploy to different environments (development, staging, and production) only after successful testing. Which GitLab CI/CD feature would you use to organize and manage this complexity efficiently?

You are managing a project with multiple environments (development, staging, production) in GitLab CI/CD. You need to ensure that any changes pushed to the development branch trigger deployments to the development environment, changes to the staging branch trigger deployments to the staging environment, and only approved changes can be deployed to production from the main branch. Which two .gitlab-ci.yml configurations should you use to achieve this?

What is the primary function of a GitLab Runner in a CI/CD pipeline?

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?

In a GitLab project, you want to ensure that every merge request (MR) is tested before it is merged into the main branch. You also want to run some extra tests only on the main branch after the MR is merged. How should you configure your .gitlab-ci.yml to achieve this?