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

Question 1

You want to integrate Container Scanning into your GitLab CI/CD pipeline to automatically detect vulnerabilities in your Docker images. What steps should you take to properly configure Container Scanning?

Options :

A : Add a container_scanning job in the .gitlab-ci.yml file and include security/container-scanning template.

B : Write a custom script to scan Docker images for vulnerabilities and integrate it into the build stage of the pipeline.

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

D : Use the before_script section to run container scans before any other job in the pipeline.

Answer: A

Question 2

A software engineering team wants to speed up their CI/CD pipeline execution by reducing redundant computations in GitLab CI/CD. They decide to use caching to store dependencies between runs. Which of the following is true about caching in GitLab CI/CD?

Options :

A : Cached files are automatically synchronized across different runner machines in a multi-runner setup.

B : GitLab automatically caches all files used in previous jobs unless explicitly disabled.

C : A cache is always removed after a job completes, and it cannot be retained for future jobs.

D : The cache keyword allows caching of files or directories between pipeline jobs and can be shared across different pipelines.

Answer: D

Question 3

How can a downstream pipeline in another project be triggered in a Multi-Project Pipeline configuration?

Options :

A : By using the include keyword with a reference to the other project-s YAML file

B : By using the trigger keyword with a project parameter

C : By specifying a multi-project keyword at the top level of the pipeline configuration

D : By setting the parallel keyword in the pipeline definition

Answer: B

Question 4

You are configuring a CI/CD pipeline in GitLab and want to utilize Directed Acyclic Graph (DAG) pipelines to optimize the execution of independent jobs. You have the following jobs: build, lint, test, and deploy. The deploy job should run only after both build and test jobs have completed successfully, while lint can run in parallel with any other job. How would you configure the .gitlab-ci.yml file to achieve this?

Options :

A :

build:
  stage: build
lint:
  stage: lint
test:
  stage: test
deploy:
  stage: deploy
  needs: ["build", "test"]

B :

build:
  stage: build
lint:
  stage: lint
test:
  stage: test
deploy:
  stage: deploy
  requires: ["build", "test"]

C :

build:
  stage: build
lint:
  stage: lint
test:
  stage: test
deploy:
  stage: deploy
  after: ["build", "test"]

D :

Answer: A

Question 5

In a GitLab CI/CD pipeline, how can you ensure that a job named deploy will only run after the successful completion of the build and test jobs?

Options :

A : Use the dependencies keyword to specify build and test in the deploy job.

B : Use the before_script keyword in the deploy job to run build and test scripts.

C : Use the stages keyword to define build, test, and deploy stages.

D : Use the needs keyword to specify build and test in the deploy job.

Answer: D