AZ400-Q: design a hotfix path
A severe production defect requires a fix before the next scheduled release train. The team must preserve traceability and avoid bypassing normal validation. What is the best hotfix approach?
- A) Commit directly to the production server.
- B) Edit the deployed artifact in the package feed.
- C) Create a controlled hotfix branch from the affected release, run the required validation and deployment path, tag the released version, and merge the fix back according to the branching policy. ✓
- D) Wait for the next release train regardless of impact.
Answer: C. A hotfix path accelerates delivery while retaining source control, validation, versioning, deployment controls, and reconciliation with ongoing work.
Why not the others: Direct production changes and mutable artifacts lose traceability. Waiting may be inappropriate for a severe incident.