AZ400-Q: undo a released change safely
A bad change has already been merged to the protected default branch and included in a release. The team needs an auditable correction without rewriting shared history. What should it use?
- A) Force-push a rewritten branch history.
- B) Create a revert commit through the normal review/validation path. ✓
- C) Delete the repository.
- D) Remove the release artifact from storage without source change.
Answer: B. A revert creates a new, traceable commit that reverses a prior change while preserving shared history and normal controls.
Why not the others: Rewriting protected shared history disrupts collaborators. Deleting repositories or artifacts loses evidence and does not provide a reviewed correction.