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

Question 1

You are setting up a GitLab CI/CD pipeline that needs to execute specific jobs only when certain conditions are met, such as changes to a particular file or directory. Which GitLab CI/CD feature allows you to define these conditions within your pipeline?

Options :

A : Rules

B : Job Dependencies

C : Only/Except Keywords

D : CI/CD Templates

Answer: A

Question 2

In a GitLab CI/CD pipeline, a job named build generates files that will be used in subsequent jobs. How should you configure the pipeline to efficiently use these files in later jobs?

Options :

A : Commit the files to the repository and pull them in subsequent jobs.

B : Use environment variables to store the file paths and access them in subsequent jobs.

C : Use the artifacts keyword to save the files in the build job and retrieve them in subsequent jobs using dependencies.

D : Use the cache keyword to save the files and specify the paths in the subsequent jobs.

Answer: C

Question 3

You need to optimize a GitLab CI/CD pipeline to include caching to speed up subsequent pipeline runs, and also ensure that artifacts from the build stage are available to the deployment stage. Which two configurations should you use in the .gitlab-ci.yml file?

Options :

A : Define artifacts in the build stage and specify the paths and when to be used.

B : Use the dependencies keyword to define job dependencies.

C : Set up a before_script section to manually handle caching and artifact creation.

D : Use the cache keyword to define paths to be cached between jobs.

E : Combine all stages into a single job to avoid the need for caching and artifact sharing.

Answer: A,D

Question 4

You want to integrate License Scanning into your GitLab CI/CD pipeline to automatically check for compliance with your organization’s licensing policies. What steps should you take to properly configure License Scanning?

Options :

A : Use the license-check job before deployment to ensure compliance with licensing policies.

B : Configure a webhook to trigger a license scan after every commit.

C : Add a license_scan job in the .gitlab-ci.yml file and include security/license-scanning template.

D : Install a third-party license scanning tool on your CI runners and configure it to run during the pipeline.

Answer: C

Question 5

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?

Options :

A : Use GitLab’s only and except keywords in the pipeline jobs to control which branches deploy to which environments.

B : Use separate .gitlab-ci.yml files for each branch to handle the deployments.

C : Create separate GitLab projects for each environment and link them using pipeline triggers.

D : Define environments within a single .gitlab-ci.yml file using job rules to target specific branches.

E : Set up manual pipelines for each environment and manually trigger them based on the branch.

Answer: A,D