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
  20% (9)
• B
  80% (36)

Explanation

Explanation

Option B (No) is correct because the solution presented fails to properly meet both requirements simultaneously - it either incorrectly configures the path filter (missing the /webapp folder trigger), incorrectly sets up the PR trigger, or uses an incompatible combination of trigger types that doesn't restrict pipeline execution as specified.

To meet both goals, the pipeline YAML must include a pr trigger (not a trigger for CI) combined with a paths filter pointing to the /webapp folder, structured like:

pr:
  branches:
    include:
      - '*'
  paths:
    include:
      - /webapp

Option A (Yes) is incorrect because the proposed solution is incomplete or misconfigured - for example, using a trigger block instead of pr, or omitting the paths section entirely, meaning not both conditions are enforced.

Memory Tip: Remember the key pairing - pr: controls when (pull request only) and paths: include: controls where (specific folder). If either piece is wrong or missing in the solution shown, the answer is always No.

No community discussion yet for this question.