Latest GitLab-Certified-CI-CD-Associate Practice Test for Free Online Preparation

Question 1

You are managing a GitLab CI/CD pipeline and need to ensure that certain jobs are only run for tagged commits, specifically for version releases like "v1.0.0". Which configuration correctly specifies that a job should only run for these tagged commits?

Options :

A :

only:
  - /^v\d+\.\d+\.\d+$/

B :

only:
  - tags

C :

only:
  - branches

D :

Answer: A

Question 2

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?

Options :

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 3

You are managing a CI/CD pipeline in GitLab for a monorepo containing multiple services. Some services need to be tested and deployed only when specific files are modified. How should you configure the pipeline to achieve this efficiently?

Options :

A : Use only keyword with specific branch names.

B : Use except keyword with specific branch names.

C : Use dependencies keyword to link jobs based on file changes.

D : Use rules keyword with changes parameter to specify the files.

Answer: D

Question 4

In a GitLab CI/CD pipeline, you need to execute a script that requires specific environment variables to be set dynamically based on the branch name. How can you configure the job to set these variables?

Options :

A : Use the tags keyword to specify different runners that set different environment variables.

B : Use the before_script section to write a script that sets the environment variables dynamically.

C : Set the environment variables in the job script section.

D : Define the environment variables in the .gitlab-ci.yml file under the variables section.

Answer: B

Question 5

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?

Options :

A : Use a single pipeline with environment-specific jobs and Kubernetes executor, utilizing environment variables to manage namespaces.

B : Use child pipelines to manage each environment within the same repository.

C : Create separate repositories for each environment with their own pipelines.

D : Use GitLab Pages to deploy different versions of the application.

Answer: A

Smartly Prepare Exam with Free Online GitLab-Certified-CI-CD-Associate Practice Test

Buying Options: