Objective: Explain What GitLab CI/CD Is and Why Teams Use It GITLAB-CERTIFIED-CICD-ASSOCIATE Practice Questions (Page 1)

Questions 1–5

1. 1foundation · easy

   When a developer pushes a commit to a GitLab repository with CI/CD configured, what happens automatically?

   • AThe commit is immediately deployed to production.
   • BThe commit is rejected if it does not follow a naming convention.
   • CThe repository is forked to a new project.
   • DA pipeline is triggered to run the defined jobs.
   Reveal Solution Discussion Select an answer first
2. 2application · medium

   A developer commits a change to the repository. The .gitlab-ci.yml file defines a job named 'compile' in the 'build' stage and a job named 'integration-test' in the 'test' stage. Both jobs are assigned to the same runner. What is the execution order of these jobs?

   • A'integration-test' runs first, then 'compile' runs after it completes
   • B'compile' runs first, then 'integration-test' runs after 'compile' completes successfully
   • CBoth jobs run simultaneously on the same runner
   • DThe order depends on the runner's available resources
   Reveal Solution Discussion Select an answer first
4. 3application · medium

   A development team is experiencing frequent production incidents caused by configuration drift and manual deployment errors. They want to reduce human intervention in the release process while still requiring a manual approval before production deployment. Which GitLab CI/CD approach best addresses their need?

   • AContinuous Delivery with a manual approval job before the production deploy
   • BContinuous Deployment with automatic production releases
   • CManual pipeline execution for every release
   • DContinuous Integration with no deployment automation
   Reveal Solution Discussion Select an answer first
5. 4application · medium

   A company's leadership wants to shorten the time between a developer committing code and the code being available to end users. They currently have a fully automated pipeline that builds, tests, and deploys to production without human intervention. Which practice are they using?

   • ARelease Orchestration
   • BContinuous Deployment
   • CContinuous Delivery
   • DContinuous Integration
   Reveal Solution Discussion Select an answer first
6. 5expert · hard

   A team has a pipeline that deploys to production. They want to prevent a pipeline from running when a commit message contains '[skip ci]'. However, they also want to ensure that merge request pipelines still run even if the commit message contains this tag. Which configuration achieves this?

   • ARemove the '[skip ci]' feature entirely from the repository
   • BUse a webhook to cancel pipelines after they start
   • CUse a rule that skips the pipeline for push events with '[skip ci]' but allows merge_request_event pipelines
   • DConfigure the runner to ignore commits with '[skip ci]'
   Reveal Solution Discussion Select an answer first