Validating App1 Performance in the Staging Environment with an Azure Monitor Alerts Check

AZ-400 By islever Editorial Last updated

Design and implement deployments

Short answer

D An environment check in Staging querying Azure Monitor alerts validates App1 there, so a problem blocks promotion to Production with no manual approval.

Question

You have an Azure subscription that includes an app named App1. You have an Azure DevOps project that contains two environments named Staging and Production. You use Azure Pipelines to deploy App1. You need to validate the performance of App1 in the Staging environment before it is deployed to Production. The solution must minimize administrative effort. What should you do in the Azure DevOps project?
  1. In the production branch policy, add a status check to query Azure Monitor Alerts for active alerts.
  2. In the Production environment, add a check to query Azure Monitor Alerts for active alerts.
  3. In the Production environment stage, add a post-deployment approval for the Azure Monitor Alerts group.
  4. In the Staging environment add a check to query Azure Monitor Alerts for active alerts. Correct Answer

Key Takeaways

The check belongs in the Staging environment because that is the environment whose performance the requirement asks to validate, and an environment check querying Azure Monitor alerts is the native low-effort way to make that validation a gate before Production.

App1 is deployed through Azure Pipelines and must have its performance validated in the Staging environment before it is deployed to Production, with minimal administrative effort. The validation has to happen against the environment where the performance problem would actually manifest.

Common mistake: Placing the check in the Production environment, which validates the environment the app is about to leave rather than the one it must pass through, or adding a manual post-deployment approval, which reintroduces human effort that the question explicitly asks to minimize.

Expert Analysis

Why the Answer Is Correct

The requirement is to validate the performance of App1 in the Staging environment before it is deployed to Production. The check therefore has to be attached to the Staging environment, and the mechanism that validates it with minimal effort is an environment check that queries Azure Monitor alerts, because alerts already exist as a signal and the check simply consumes them. Placing the check in Staging makes the validation a gate in the flow rather than a report generated afterward. The vote was unanimous at 100 for D. danisancho stated the reasoning directly, noting that adding a check in the Staging environment to query Azure Monitor Alerts ensures the application's performance is validated before it moves to Production, and Dankho compressed it to the observation that the requirement is to monitor Staging and D is Staging.

Why the Other Options Are Wrong

Adding a check to the Production environment (B) queries alerts for the environment the app is being promoted into, which either arrives too late to influence the decision or reports on production rather than validating the staging performance the requirement names. Adding a post-deployment approval for the Azure Monitor Alerts group to the Production environment stage (C) fails twice: it is positioned in Production rather than Staging, and a manual approval is the opposite of minimizing administrative effort since it depends on a person noticing and clicking. Adding a status check to the production branch policy (A) governs source control merges and has no visibility into Azure Monitor alerts for an environment, so it cannot validate runtime performance at all.

Community Comment Notes

The community was unanimous at 100 for D, and the two substance comments both anchor on the same word in the requirement. danisancho tied the check placement to the deployment order, that the check in Staging validates performance before the move to Production. Dankho made the shortest possible argument, that the requirement is to monitor Staging and option D is Staging, which is the cleanest form of the reasoning because it reduces the question to matching the requirement's environment against the options' environments. The distractors are all positioned in Production or in source control, so the discrimination is about where the validation has to happen.

Official Reference

https://learn.microsoft.com/en-us/azure/devops/pipelines/process/checks?view=azure-devops

This link opens the official vendor documentation in a new tab.

Community Votes

D
100%

100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 3 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 3

  1. danisancho 👍 3 Answered D
    D is the correct answer. Adding a check in the Staging environment to query Azure Monitor Alerts ensures that the app’s performance is validated before it moves to Production.
  2. Dankho 👍 1 Answered D
    Requirement is to monitor Staging, and D is Staging
  3. nyale 👍 1 Answered D
    correct

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Practice All AZ-400 Questions

Access 100 questions with complete answers and detailed explanations.

View Full AZ-400 Practice Test →

← Back to AZ-400 Study Guide