AZ-400 · Question #564
AZ-400 Question #564: Real Exam Question with Answer & Explanation
The correct answer is B: No. Option B (No) is correct because the solution presented fails to properly meet both stated requirements simultaneously - typically, the configuration shown either uses incorrect syntax, applies the wrong trigger type, or omits a required path filter combined with a PR trigger. To
Question
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You use an Azure Pipelines pipeline to build and release web apps. You need to configure the pipeline to meet the following requirements: - Only run when there is a change in the /webapp folder. - Only run when a pr is created. Solution: You configure the pipeline definition by using the following elements. Does this meet the goal?
Options
- AYes
- BNo
Explanation
Option B (No) is correct because the solution presented fails to properly meet both stated requirements simultaneously - typically, the configuration shown either uses incorrect syntax, applies the wrong trigger type, or omits a required path filter combined with a PR trigger. To satisfy both conditions, the pipeline YAML must use a pr: trigger (not a ci: or trigger: block) and include a paths: include: ['/webapp'] filter within that PR trigger definition.
Why Option A (Yes) is wrong: The proposed solution does not correctly implement both requirements together. A common mistake is using a standard trigger: (CI trigger) instead of a pr: trigger, or specifying the path filter in the wrong section, meaning changes outside the PR context or outside the /webapp path could still trigger the pipeline.
Why other configurations fail: Azure Pipelines treats trigger: (push/CI) and pr: (pull request) triggers as separate, distinct blocks - mixing them up or missing the path scope under the correct trigger block means the pipeline behavior won't match the stated goals.
Memory Tip: Remember "PR = Pull Request trigger block" - whenever a question specifies "only run when a PR is created," you must use the pr: trigger key, and path filters must live inside that same block. If either piece is missing or misplaced, the solution is incomplete.
Topics
Community Discussion
No community discussion yet for this question.