AZ400-Q: prevent infrastructure drift
An engineer changes a production resource manually in the portal. The next deployment silently leaves the undocumented setting in place. The platform team needs a durable solution. What should it do?
- A) Define the required configuration in version-controlled IaC, review and deploy it through the pipeline, and detect/remediate drift against that desired state. ✓
- B) Ban every portal user from viewing Azure.
- C) Put a comment in the pipeline that says not to make manual changes.
- D) Export a template once each year.
Answer: A. Desired state, source control, and repeatable deployment make configuration reviewable and allow drift to be detected and corrected.
Why not the others: Viewing is not modification. A comment is not control. An annual export neither prevents nor promptly detects drift.