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

Question 1

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

Question 2

You are managing a complex CI/CD pipeline in GitLab for an application that requires deploying to multiple environments (development, staging, and production). Each environment requires specific configurations and a sequence of deployment steps. Which GitLab feature should you use to manage this process efficiently?

Options :

A : Scheduled Pipelines

B : Environments and Deployments

C : GitLab Runners

D : Git Submodules

Answer: B

Question 3

You want to integrate Dependency Scanning into your GitLab CI/CD pipeline to automatically detect vulnerabilities in your project's dependencies. What steps should you take to properly configure Dependency Scanning?

Options :

A : Write a custom script to parse dependencies and check for vulnerabilities during the build stage.

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

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

D : Install a third-party tool on your CI runners and manually configure it to scan dependencies.

Answer: C

Question 4

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?

Options :

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

Question 5

You are managing a complex GitLab CI/CD pipeline for a project that has multiple stages including build, test, and deploy. The build stage must compile the code, the test stage should run unit tests, and the deploy stage should push the code to a staging server. However, the deploy stage should only run if the build and test stages are successful. How can you ensure that the deploy stage only runs after the successful completion of the build and test stages?

Options :

A : Use dependencies keyword to specify that the deploy stage depends on the build and test stages.

B : Use allow_failure: true in the build and test stages.

C : Place the deploy stage after the build and test stages in the pipeline configuration.

D : Use needs keyword to ensure the deploy stage waits for build and test stages to complete.

Answer: C

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

Buying Options: