You are developing an Azure Pipelines pipeline. You need to configure a check in the pipeline that will query Azure Boards to ensure that there are no active work item issues before the pipeline deplo

Question

Options

• Apost-deployment approvals
• Bmanual validations
• Cpre-deployment gates
• Dpre-deployment approvals

• A
  8% (3)
• B
  13% (5)
• C
  78% (31)
• D
  3% (1)

Explanation

Pre-deployment gates (Option C) are automated checks that run before a deployment begins, and they can query external systems - like Azure Boards - to validate conditions are met before allowing the pipeline to proceed. Gates are specifically designed for automated, condition-based queries (e.g., "are there zero active bugs?"), making them the ideal tool for this scenario.

Why the distractors are wrong:

• A (Post-deployment approvals): These occur after a deployment, so they cannot prevent a flawed build from reaching production.
• B (Manual validations): These require a human to manually confirm a step, rather than automatically querying Azure Boards programmatically.
• D (Pre-deployment approvals): These also require human sign-off before a deployment, not an automated system query.

Memory Tip: Think of Gates = Automated and Approvals = Human. If the question involves querying a system or checking a condition automatically, the answer is almost always a gate. If it involves a person reviewing or approving, it's an approval. The prefix "pre-" vs "post-" simply tells you when it runs relative to the deployment.

No community discussion yet for this question.