Pass GitLab-Certified-CI-CD-Associate Exam with Free Online Practice

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 instance with several projects under a single group. To optimize resource usage and manage CI/CD pipelines more efficiently, you decide to use Group Runners instead of project-specific runners. Which of the following statements correctly describes the benefit of using Group Runners in this context?

Options :

A : Group Runners provide a unique configuration per project, leading to more customizable CI/CD pipelines.

B : Group Runners can only be used by projects that have a premium subscription.

C : Group Runners can be shared among all projects within the group, reducing the need to manage multiple runners for each project.

D : Group Runners are automatically assigned to each project, and cannot be unassigned.

Answer: C

Question 3

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 4

In a GitLab project, you want to ensure that every merge request (MR) is tested before it is merged into the main branch. You also want to run some extra tests only on the main branch after the MR is merged. How should you configure your .gitlab-ci.yml to achieve this?

Options :

A :

stages:
  - test
  - extra-tests
 
test:
  stage: test
  script:
    - echo "Running tests"
  only:
    - merge_requests
 
extra-tests:
  stage: extra-tests
  script:
    - echo "Running extra tests"
  only:
    - main

B :

stages:
  - test
  - extra-tests
 
test:
  stage: test
  script:
    - echo "Running tests"
  except:
    - main
 
extra-tests:
  stage: extra-tests
  script:
    - echo "Running extra tests"
  except:
    - merge_requests

C :

stages:
  - test
  - extra-tests
 
test:
  stage: test
  script:
    - echo "Running tests"
  only:
    - merge_requests
 
extra-tests:
  stage: extra-tests
  script:
    - echo "Running extra tests"
  only:
    - merge_requests

D :

Answer: A

Question 5

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

Higher Test Marks with Free Online GitLab-Certified-CI-CD-Associate Exam Practice

Buying Options: