Objective: Identify the Key Components Needed for a CI/CD Pipeline GITLAB-CERTIFIED-CICD-ASSOCIATE Practice Questions (Page 3)

Questions 11–15

1. 11expert · medium

   A team is migrating from a Jenkins pipeline to GitLab CI/CD. Their current pipeline has a 'build' stage that compiles code and a 'test' stage that runs unit tests. They want to ensure that the test stage receives the compiled code. In Jenkins, they used a shared workspace. How should they achieve this in GitLab CI/CD?

   • AUse the same runner for both jobs and rely on the shared workspace
   • BUse artifacts to pass the compiled code from the build job to the test job
   • CRecompile the code in the test job to ensure it is available
   • DStore the compiled code in a Git branch and check it out in the test job
   Reveal Solution Discussion Select an answer first
2. 12expert · hard

   A company has a monorepo with multiple projects. They want to run a pipeline only when files in a specific directory change. For example, changes to 'backend/' should trigger the backend pipeline, and changes to 'frontend/' should trigger the frontend pipeline. They also want to prevent unauthorized users from triggering pipelines manually. Which approach best meets these requirements?

   • AUse 'rules:changes' in .gitlab-ci.yml to conditionally run jobs based on which files changed, and configure project permissions to restrict manual pipeline creation
   • BUse a pipeline schedule that runs all jobs every hour
   • CCreate separate repositories for each project to avoid the need for path filtering
   • DUse a single pipeline for the whole repository and run all jobs on every push
   Reveal Solution Discussion Select an answer first
4. 13application · medium

   A development team uses GitLab with a repository hosted on GitLab.com. They want a pipeline to run automatically whenever a developer pushes a new commit to the 'main' branch, but not when they push to feature branches. What is the most appropriate way to configure this?

   • AUse a webhook from an external CI system to trigger the pipeline on every push
   • BConfigure a pipeline schedule that runs every hour on the 'main' branch
   • CManually run the pipeline from the GitLab UI after each push to 'main'
   • DDefine a pipeline in .gitlab-ci.yml with a rule that limits the pipeline to the 'main' branch
   Reveal Solution Discussion Select an answer first
5. 14expert · hard

   A company deploys an application to multiple environments: development, staging, and production. They want to use the same deployment job definition for all environments, but with different variables for each. They also want to require manual approval for production, but not for development or staging. Which GitLab CI/CD feature best supports this?

   • AUse a pipeline schedule to deploy to all environments automatically
   • BCreate three separate jobs with duplicated deployment scripts
   • CUse a single job with a 'when: manual' rule for all environments
   • DUse a job template with 'parallel:matrix' to run the job for each environment, and use 'rules' to make the production instance manual
   Reveal Solution Discussion Select an answer first
6. 15foundation · easy

   Which stage in a CI/CD pipeline is specifically designed to catch bugs and regressions before deployment?

   • AMonitor stage
   • BDeploy stage
   • CTest stage
   • DBuild stage
   Reveal Solution Discussion Select an answer first