A company has a group-level CI/CD variable named DEPLOY_ENV set to 'staging' for the 'development' group. A project within this group defines a project-level variable with the same name set to 'production'. The .gitlab-ci.yml file for this project also defines DEPLOY_ENV as 'test' in the `variables` keyword at the top level. A pipeline runs for a merge request. What value will the DEPLOY_ENV variable have in the pipeline job?

The pipeline fails due to a variable conflict

A project has a project-level variable CONFIG set to 'project'. The .gitlab-ci.yml file defines CONFIG as 'yaml'. A user triggers a pipeline via the API and passes a variable CONFIG='api'. What is the value of CONFIG in the pipeline?

The pipeline fails due to a conflict.

An instance-level variable is defined in the Admin Area. Which projects will have access to this variable?

Only projects in the default group

Only projects with the 'Use instance variables' setting enabled

Only projects created after the variable is defined

Which of the following lists the variable precedence order from highest to lowest?

Instance > Group > Project > Pipeline

Project > Pipeline > Group > Instance

Pipeline > Project > Group > Instance

Group > Project > Instance > Pipeline

A team defines a variable LOG_LEVEL in the `variables` section of their .gitlab-ci.yml file. They also have a project-level variable LOG_LEVEL set to 'debug'. They want the project-level value to be used in all pipelines. What is the correct action?

Set the project-level variable to be 'protected'.

Move the variable definition to the group level.

Change the project-level variable to have a different name.

Remove the LOG_LEVEL variable from the .gitlab-ci.yml file.

GitLabCertified CI/CD Associate

Domain 2Objective 3

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

Part of the Domain 2: CI/CD Fundamentals domain, which makes up ~30% of our current practice bank.

29questions here

6free pages

8concepts

Questions 11–15

11application · medium
A company has a group-level CI/CD variable named DEPLOY_ENV set to 'staging' for the 'development' group. A project within this group defines a project-level variable with the same name set to 'production'. The .gitlab-ci.yml file for this project also defines DEPLOY_ENV as 'test' in the `variables` keyword at the top level. A pipeline runs for a merge request. What value will the DEPLOY_ENV variable have in the pipeline job?
Select an answer first
12expert · medium
A project has a project-level variable CONFIG set to 'project'. The .gitlab-ci.yml file defines CONFIG as 'yaml'. A user triggers a pipeline via the API and passes a variable CONFIG='api'. What is the value of CONFIG in the pipeline?
Select an answer first
13foundation · easy
An instance-level variable is defined in the Admin Area. Which projects will have access to this variable?
Select an answer first
14foundation · easy
Which of the following lists the variable precedence order from highest to lowest?
Select an answer first
15application · medium
A team defines a variable LOG_LEVEL in the `variables` section of their .gitlab-ci.yml file. They also have a project-level variable LOG_LEVEL set to 'debug'. They want the project-level value to be used in all pipelines. What is the correct action?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to GITLAB-CERTIFIED-CICD-ASSOCIATE

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by GitLab. “GITLAB-CERTIFIED-CICD-ASSOCIATE” is a trademark of its owner, used for identification only.