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

Questions 26–29

1. 26foundation · easy

   Which of the following is NOT a valid scope level for defining CI/CD variables in GitLab?

   • AOrganization
   • BInstance
   • CProject
   • DGroup
   Reveal Solution Discussion Select an answer first
2. 27foundation · easy

   Where in .gitlab-ci.yml can you define a variable that is available to all jobs in the pipeline?

   • AIn the stages section
   • BInside a job's script section
   • CAt the top level of the file
   • DIn the before_script section
   Reveal Solution Discussion Select an answer first
4. 28application · medium

   A project has a project-level variable API_KEY set to 'project-key'. The .gitlab-ci.yml file also defines API_KEY as 'yaml-key'. A developer wants to run a pipeline with the value 'override-key' without changing any files or settings permanently. What is the simplest way?

   • AChange the project-level variable to 'override-key' and run the pipeline.
   • BEdit the .gitlab-ci.yml file to change the value, run the pipeline, then revert the change.
   • CUse the GitLab API to update the project variable, run the pipeline, then revert.
   • DUse the 'Run pipeline' form in the UI and add a variable API_KEY with the value 'override-key'.
   Reveal Solution Discussion Select an answer first
5. 29application · medium

   An instance-level variable DEPLOY_ENV is set to 'production'. A group 'qa' sets a group-level variable DEPLOY_ENV to 'staging'. A project 'qa/app' does not define this variable. A user triggers a pipeline for 'qa/app' and passes a pipeline variable DEPLOY_ENV='test'. What value will the job see?

   • Aproduction
   • BThe pipeline fails due to a conflict.
   • Cstaging
   • Dtest
   Reveal Solution Discussion Select an answer first