Objective: Scope and Persist Variables at Various Levels GITLAB-CERTIFIED-CICD-ASSOCIATE Practice Questions (Page 5)

Questions 21–25

1. 21application · medium

   A pipeline has a 'build' job that generates a version number and a 'deploy' job that needs to use that version number. The version number is not known before the pipeline starts. What is the recommended way to pass the version number from the 'build' job to the 'deploy' job?

   • AUse a group-level variable and override it in the deploy job.
   • BDefine the version number as a project-level variable and update it before each pipeline run.
   • CUse the `variables` keyword in the deploy job to reference the build job's output.
   • DWrite the version number to a file and use the `artifacts` keyword to pass it to the deploy job.
   Reveal Solution Discussion Select an answer first
2. 22foundation · easy

   Which role is required to define instance-level CI/CD variables in GitLab?

   • AOwner
   • BDeveloper
   • CAdministrator
   • DMaintainer
   Reveal Solution Discussion Select an answer first
4. 23foundation · easy

   A CI/CD administrator wants to define a variable that will be available to every pipeline in the entire GitLab instance. Which variable scope level should they use?

   • AGroup level
   • BInstance level
   • CPipeline level
   • DProject level
   Reveal Solution Discussion Select an answer first
5. 24foundation · easy

   What is the purpose of using a dotenv report artifact in a pipeline?

   • ATo cache dependencies between jobs
   • BTo define variables in the .gitlab-ci.yml file
   • CTo store build artifacts for download
   • DTo pass variables from one job to later jobs
   Reveal Solution Discussion Select an answer first
6. 25expert · hard

   A pipeline has a 'generate' job that creates a configuration file with a random token. A 'deploy' job needs to use this token. The 'deploy' job should not run if the 'generate' job fails. What is the correct way to pass the token to the 'deploy' job?

   • AUse a group-level variable to store the token.
   • BUse `artifacts` in the 'generate' job and `dependencies` in the 'deploy' job, and ensure the 'deploy' job has `needs: ['generate']`.
   • CUse the `variables` keyword in the 'deploy' job to define the token.
   • DUse a project-level variable to store the token and update it in the 'generate' job.
   Reveal Solution Discussion Select an answer first