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

Question 1

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

Question 2

You need to create a GitLab CI/CD pipeline with the following requirements:The build stage compiles the code.The test stage runs unit tests.The integration stage runs integration tests but should only run if the test stage is successful.The deploy stage deploys the application but should only run if both the test and integration stages are successful and only on the production branch.Which of the following .gitlab-ci.yml configurations correctly implements this scenario?

Options :

A :

stages:
  - build
  - test
  - integration
  - deploy
 
test:
  stage: test
  script:
    - run_tests
 
integration:
  stage: integration
  script:
    - run_integration_tests
  needs:
    - test
 
deploy:
  stage: deploy
  script:
    - deploy_application
  only:
    - production
  needs:
    - integration

B :

stages:
  - build
  - test
  - integration
  - deploy
 
test:
  stage: test
  script:
    - run_tests
 
integration:
  stage: integration
  script:
    - run_integration_tests
  only:
    - production
 
deploy:
  stage: deploy
  script:
    - deploy_application
  only:
    - production

C :

stages:
  - build
  - test
  - integration
  - deploy
 
integration:
  stage: integration
  script:
    - run_integration_tests
 
deploy:
  stage: deploy
  script:
    - deploy_application
  only:
    - production

D :

Answer: A

Question 3

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 4

You are working on a project that requires deploying a web application to a Kubernetes cluster. The deployment process should include running unit tests, building a Docker image, pushing the image to a container registry, and then deploying it to the Kubernetes cluster. Which of the following CI/CD configurations would best achieve this in GitLab?

Options :

A : Use a single pipeline with stages for testing, building, and deploying, utilizing the Docker and Kubernetes executors.

B : Use separate pipelines for testing and deployment to isolate the deployment process from the main CI/CD pipeline.

C : Use a single pipeline with a manual job for deployment to ensure it is only deployed when manually triggered.

D : Use GitLab Pages to deploy the web application to a Kubernetes cluster after building and testing.

Answer: A

Question 5

A DevOps engineer is setting up a GitLab Child Pipeline to dynamically trigger jobs based on changes in different components of their repository. Which of the following is required to correctly configure a child pipeline?

Options :

A : A child pipeline must be defined in the same .gitlab-ci.yml file as the parent pipeline.

B : Use the trigger keyword in a job configuration to specify the child pipeline’s configuration file.

C : Define a job in .gitlab-ci.yml that uses extends: child-pipeline.

D : Add child-pipeline: true as a global setting in the GitLab project’s CI/CD settings.

Answer: B

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

Buying Options: