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

Options

• AYes
• BNo

• A
  44% (16)
• B
  56% (20)

Explanation

Option B (No) is correct because the solution presented does not properly meet both stated requirements simultaneously - typically, the pipeline definition shown either lacks the correct path filter (/webapp), is missing the proper PR trigger configuration, or uses an incorrect syntax that doesn't satisfy both conditions together in Azure Pipelines YAML.

To meet the goals, you need a pr trigger that specifies both a paths filter targeting /webapp and the branch conditions, structured correctly in YAML like:

pr:
  paths:
    include:
      - webapp

Without both elements correctly configured together, the pipeline will not behave as required.

Why Option A (Yes) is wrong: The solution as presented is incomplete or incorrectly structured, meaning it would not reliably trigger only on PRs with changes in the /webapp folder - accepting it as correct would lead to misconfigured pipelines.

Memory Tip: Remember the "P-P Rule" - for PR-triggered pipelines with path filters, you need PR trigger + Path filter both correctly defined in the same block. If either is missing or misplaced in the YAML hierarchy, the trigger won't work as intended. Always verify that paths is nested under the pr: key, not under a separate trigger: key.

No community discussion yet for this question.