ExamTopics Logo
Mail Us[email protected]
Menu
Microsoft Discussions
exam questions

Exam AZ-400 All Questions

View all questions & answers for the AZ-400 exam
Go to Exam

Exam AZ-400 topic 8 question 67 discussion

Actual exam question from Microsoft's AZ-400
Question #: 67
Topic #: 8
[All AZ-400 Questions]

DRAG DROP
-

You have an Azure Pipeline.

You need to store configuration values as variables.

At which four scopes can the variables be defined, and what is the precedence of the variables from the highest precedence to lowest precedence? To answer, move the appropriate scope from the list of scopes to the answer area and arrange them in the correct order.

Show Suggested Answer Hide Answer
Suggested Answer:
by mrg998 at Jan. 19, 2023, 5:40 p.m.

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Submit Cancel
lugia4000
Highly Voted 1 year, 2 months ago
Eliminate task and the answer is from the least letters to most letters, to memorize better
upvoted 60 times
hotspot02103
3 months, 2 weeks ago
This is how I learned at school, now I don't remember anything. Start studying by understanding not memorizing!
upvoted 2 times
mjansen
3 days, 6 hours ago
I agree, but I don't think tests like this help that haha.
upvoted 1 times
...
...
Dankho
3 months, 3 weeks ago
Great way to memorize it, gotta love it!
upvoted 1 times
...
...
zellck
Highly Voted 10 months, 3 weeks ago
1. job 2. stage 3. pipeline root 4. pipeline settings UI https://learn.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=yaml%2Cbatch#variable-scopes In the YAML file, you can set a variable at various scopes: - At the root level, to make it available to all jobs in the pipeline. - At the stage level, to make it available only to a specific stage. - At the job level, to make it available only to a specific job. When you define a variable at the top of a YAML, the variable is available to all jobs and stages in the pipeline and is a global variable. Global variables defined in a YAML aren't visible in the pipeline settings UI. Variables at the job level override variables at the root and stage level. Variables at the stage level override variables at the root level.
upvoted 12 times
xRiot007
8 months, 3 weeks ago
What about tasks ? The task can have and env (environment) section that maps from other values. Can those variables instead of mapping have direct assignment ? That would mean that a task can have its own variables too.
upvoted 2 times
...
...
Fal991l
Most Recent 1 year ago
GTP: The task scope is a valid scope for defining variables in Azure Pipelines, and it has the highest precedence among all scopes. So, it is definitely a valid choice for defining variables.
upvoted 1 times
Fal991l
1 year ago
In Azure Pipelines, you can define variables at four different scopes: pipeline root, pipeline settings UI, stage, and job. The precedence of these variables from highest to lowest is as follows: e. task b. job a. stage c. pipeline settings UI d. pipeline root
upvoted 2 times
Fal991l
1 year ago
Variables defined at the task scope have the highest precedence and will override any variables with the same name defined at lower scopes. Variables defined at the job scope will override any variables with the same name defined at the stage, pipeline settings UI, or pipeline root scopes. Variables defined at the stage scope will override any variables with the same name defined at the pipeline settings UI or pipeline root scopes. Finally, variables defined at the pipeline settings UI scope will override any variables with the same name defined at the pipeline root scope.
upvoted 2 times
oskarq
6 months, 2 weeks ago
I checked and the code below gives na error. Task can't accept property variables. task: variables: string: string # Name/value pairs
upvoted 2 times
...
...
...
...
crymo99
1 year, 3 months ago
Seems correct. When you set a variable with the same name in multiple scopes, the following precedence applies (highest precedence first). Job level variable set in the YAML file Stage level variable set in the YAML file Pipeline level variable set in the YAML file Variable set at queue time Pipeline variable set in Pipeline settings UI https://learn.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=yaml%2Cbatch
upvoted 8 times
dottLorenz
1 year, 2 months ago
Variable scopes In the YAML file, you can set a variable at various scopes: At the root level, to make it available to all jobs in the pipeline. At the stage level, to make it available only to a specific stage. At the job level, to make it available only to a specific job. When a variable is defined at the top of a YAML, it will be available to all jobs and stages in the pipeline and is a global variable. Global variables defined in a YAML are not visible in the pipeline settings UI. Variables at the job level override variables at the root and stage level. Variables at the stage level override variables at the root level.
upvoted 1 times
...
mrg998
1 year, 2 months ago
Incorrect, that article states that is the case if "When you set a variable with the same name in multiple scopes, the following precedence appliies"...key word here SAME NAME. Thats not what this question is asking.
upvoted 2 times
petitbilly
1 year, 2 months ago
This is specially the case in which you want the precedence to take effect. If they are named differently, there is no need of preference. The answer from crymo99 is correct. Double checked from here: https://learn.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=yaml%2Cbatch#expansion-of-variables
upvoted 2 times
...
...
...
mrg998
1 year, 3 months ago
In the YAML file, you can set a variable at various scopes: At the root level, to make it available to all jobs in the pipeline. At the stage level, to make it available only to a specific stage. At the job level, to make it available only to a specific job.
upvoted 1 times
...
mrg998
1 year, 3 months ago
correct
upvoted 1 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago