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

Question 1

Which of the following steps is typically the first in a basic CI/CD pipeline?

Options :

A : Deployment to Production

B : Source Code Checkout

C : Running Integration Tests

D : Sending Notifications

Answer: B

Question 2

A team wants to configure GitLab Group Runners for multiple projects but needs to ensure that only specific types of jobs run on them while other jobs should execute on shared GitLab-hosted runners. What is the best way to achieve this?

Options :

A : Configure job-level tags in .gitlab-ci.yml to match the group runner’s tags and define specific jobs to use it.

B : Assign runner tags at the instance level and let projects override them in .gitlab-ci.yml.

C : Configure the group runner as locked so that only default pipeline jobs can use it.

D : Disable shared runners at the group level to force all jobs to run on the group runner.

Answer: A

Question 3

In your GitLab CI/CD pipeline, you need to deploy an application to a staging environment for testing before it goes to production. What GitLab feature allows you to preview and manage deployments to different environments such as staging and production?

Options :

A : Runners

B : Environments

C : Artifacts

D : Tags

Answer: B

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

You have a CI/CD pipeline in GitLab with several jobs. One of your jobs, critical_task, must run and complete successfully before any other jobs in its stage can execute. You have configured the .gitlab-ci.yml as follows:stages: - setup - test critical_task: stage: setup script: - echo "Critical Task Running" secondary_task: stage: setup script: - echo "Secondary Task Running" needs: - critical_task unit_tests: stage: test script: - echo "Running unit tests"

Options :

A : secondary_task will run only after critical_task completes successfully.

B : unit_tests will run regardless of the outcome of critical_task.

C : unit_tests will run only if both critical_task and secondary_task succeed.

D : The needs keyword ensures critical_task and secondary_task run sequentially.

E : If critical_task fails, secondary_task will not run.

Answer: A,D,E

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

Buying Options: