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

Become Gitlab Certified with updated GitLab-Certified-CI-CD-Associate exam questions and correct answers

Page: 1 / 61

Total 305 Questions | Updated On: Sep 09, 2025

Add To Cart

Question 1

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 2

A DevOps engineer is setting up a GitLab CI/CD pipeline to deploy applications to different environments: staging and production. The goal is to ensure that deployments are tracked and associated with the correct environment in GitLab. How should they configure the deployment in .gitlab-ci.yml?

A : Use when: manual for the staging environment to make sure it always deploys automatically.

B : Define environment globally in .gitlab-ci.yml to apply the same setting to all jobs.

C : Use environment: name: production in all jobs so that every job is associated with the production environment.

D : Use environment: name: staging for the staging job and environment: name: production for the production job

Answer: D

Question 3

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 4

A DevOps engineer is configuring a GitLab CI/CD pipeline with multiple jobs. They need to ensure that certain jobs execute before others while optimizing the pipeline's efficiency. Which of the following best describes how GitLab determines the order of job execution in a pipeline?

A : Jobs execute sequentially from top to bottom as they appear in .gitlab-ci.yml.

B : Jobs are executed in parallel by default, unless defined in separate stages.

C : The needs keyword forces all jobs to run in strict sequential order, one after another.

D : Jobs in different stages execute randomly, without any predefined sequence.

Answer: B

Question 5

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?

A : Set up manual deployment jobs for all environments and trigger them manually.

B : Use the rules keyword with conditions for each environment-specific job.

C : Define a single pipeline for all environments and use environment variables to switch between environments.

D : Define separate jobs for each environment with the only keyword specifying the respective branch.

E : Combine all deployment jobs into a single job and use the script section to handle branching logic.

Answer: B,D

Page: 1 / 61

Total 305 Questions | Updated On: Sep 09, 2025

Add To Cart