A bad Container Apps deploy of a clerk redaction API is hurting production. What should the municipal team do to restore service quickly?
Select an answer to reveal the explanation.
Short Explanation
When the new clerk redaction revision goes sideways, you can restore service by shifting traffic back to the last healthy revision—like reopening a proven bridge while you fix the new one. This rollback gets you back to a working API without rebuilding the whole environment or settling permanently for paper checklists.
Full Explanation
Container Apps retains prior revisions, so you can restore the clerk redaction API quickly by shifting traffic back to a previous healthy revision. Reactivating or directing traffic to the last known-good revision is the supported rollback path after a bad deploy, limiting downtime without recreating the environment from staff recollection. Revision history is a core operational advantage for civic services. Leaving the bad revision at 100% traffic while updating only the marketing website FAQ fails because the broken API continues to affect users; documentation does not restore service. Deleting the Container Apps environment and rebuilding every app from memory fails because it discards revision history, secrets wiring, and configuration, turning a rollback into a risky rebuild. Permanently requiring every clerk to use an offline paper redaction checklist fails because it abandons the available platform rollback and makes a temporary incident a lasting process regression. Exam caveat: rollback depends on a previous healthy revision still being available to receive traffic; if old revisions have been deactivated and deleted, a fast rollback may not be possible. Traffic changes to a known-good revision can be faster than waiting for a new fix. Distinguish rollback to a previous revision from a forward fix using a corrected revision. Practical check: identify the last healthy revision, shift traffic to it, and confirm API success rates and latency recover; then patch forward with a new revision under canary weights. Retain enough revisions to meet civic rollback SLOs.