Situations to work through: a failing rollout, an exhausted node, a leaked credential, a 3am pager.
3 questions in DevOps & Cloud.
Stabilise first and diagnose second, which usually means reverting the change before you understand it. Take one artefact of evidence on the way out, time-box the decision aloud, communicate impact on a fixed cadence, and treat the incident as open until the damage the deploy caused is repaired.
You cannot answer it from configuration, only by performing a restore into an isolated environment and timing it. Establish the recovery targets first, then test each mechanism separately, because backup jobs that report success and replicas that are not backups are the two ways this claim is usually wrong.
Evaluating the engineering leader's capability to drive complex, long-running programs across the finish line when initial momentum has faded and organisational fatigue sets in. Use this engineering leadership answer to show the decision, trade-off, and evidence rather than a memorised definition. It also connects program delivery to the point an interviewer is testing.