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 h

Question

Exhibits

Options

• AYes
• BNo

• A
  22% (8)
• B
  78% (28)

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.

No community discussion yet for this question.