Free Online GitLab-Certified-CI-CD-Associate Exam Mock for Best Practice

Question 1

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 2

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 3

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

Question 4

You are managing a CI/CD pipeline in GitLab where you need to deploy a multi-tier application with separate services for the frontend, backend, and database. Each tier must be deployed in a specific order and verified before proceeding to the next. How would you configure this pipeline to ensure proper deployment and verification?

Options :

A : Use the stages keyword to define stages for each tier and configure jobs within each stage to handle deployment and verification.

B : Configure all deployment jobs to run as manual jobs and trigger them sequentially.

C : Use parallel keyword to deploy all tiers simultaneously and verify them in a single job.

D : Create separate GitLab projects for each tier and manage deployments individually.

Answer: A

Question 5

You are working on a project in GitLab that involves multiple environments (development, staging, production). Each environment requires different configurations and credentials. Recently, you’ve observed that the deployment to the production environment sometimes fails due to incorrect configurations being used. Which approach is best to ensure that each environment gets the correct configurations and credentials during deployment?

Options :

A : Manually change the configurations and credentials in the code before each deployment.

B : Store all configurations and credentials directly in the .gitlab-ci.yml file.

C : Use GitLab environment variables to manage different configurations and credentials.

D : Deploy only to the development environment and manually move the code to staging and production.

Answer: C

Free GitLab-Certified-CI-CD-Associate Mock Exam – Practice Online Confidently

Buying Options: