Real GitLab-Certified-CI-CD-Associate Exam Cram

Question 1

In GitLab CI/CD, different types of executors can be used to run jobs in different environments. Which of the following is an uncommon executor for running CI/CD jobs in GitLab?

Options :

A : Shell Executor

B : Kubernetes Executor

C : Docker Executor

D : Azure Pipelines Executor

Answer: D

Question 2

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 3

You are managing a project where multiple teams are working on different microservices, and each team has its own GitLab repository. You want to ensure that all microservices are tested and integrated simultaneously before deploying to production. Which two strategies would be most effective in achieving this using GitLab CI/CD?

Options :

A : Use scheduled pipelines to run tests at regular intervals.

B : Set up cross-repository triggers to run pipelines in dependent projects.

C : Manually trigger deployment after each team has tested their microservice.

D : Use a monorepo for all microservices.

E : Implement a multi-project pipeline using parent-child pipelines.

Answer: B,E

Question 4

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?

Options :

A : Parent-Child Pipelines

B : Scheduled Pipelines

C : Manual Jobs

D : Auto DevOps

Answer: A

Question 5

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?

Options :

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

Confidently Practice Online with Free GitLab-Certified-CI-CD-Associate Exam Cram

Buying Options: