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

Question 1

A team wants to configure GitLab Group Runners for multiple projects but needs to ensure that only specific types of jobs run on them while other jobs should execute on shared GitLab-hosted runners. What is the best way to achieve this?

A : Configure job-level tags in .gitlab-ci.yml to match the group runner’s tags and define specific jobs to use it.

B : Assign runner tags at the instance level and let projects override them in .gitlab-ci.yml.

C : Configure the group runner as locked so that only default pipeline jobs can use it.

D : Disable shared runners at the group level to force all jobs to run on the group runner.

Answer: A

Question 2

A GitLab CI/CD pipeline is taking too long to execute because all jobs run sequentially. The DevOps team wants to optimize it by running independent jobs in parallel while maintaining proper execution order for dependent jobs. Which approach should they take?

A : Remove stages and rely on job naming conventions to determine execution order.

B : Use when: always for all jobs so they execute immediately when a commit is pushed.

C : Use stages: [build, test, deploy] and configure jobs within the same stage to run in parallel.

D : Set needs: [test] in the deploy job to force deployment to happen before testing.

Answer: C

Question 3

You have multiple GitLab Runners in your project, each configured to run specific types of jobs. You want to ensure that your Docker-based CI/CD jobs run only on runners that have been explicitly configured for Docker. Which of the following is the correct way to ensure this behavior in your .gitlab-ci.yml file?

A :

B :

C :

D :

Answer: D

Question 4

You are responsible for a CI/CD pipeline that must deploy a complex application composed of multiple services, each with its own repository. You need to ensure that the deployment process only proceeds if the builds and tests for all services are successful. How can you orchestrate this in GitLab?

A : Utilize Multi-Project Pipelines with a Parent-Child relationship

B : Set up Manual Jobs for each service

C : Use a Monorepo for all services

D : Create a Custom Runner for each service