A county permit system uses active-passive databases with a manual promote during outages. Tabletop reviews show promote steps often miss the published RTO. What should the architect emphasize first?
Select an answer to reveal the explanation.
Short Explanation
Manual promote is like a fire drill where nobody knows who grabs the hose. Write the runbook, then automate the promote so the clock does not beat you. Stretching the RTO or hiding alerts does not fix a slow handoff.
Full Explanation
Active-passive designs often depend on a promotion or cutover step. If that step is manual and slow, the architecture can miss RTO even when standby capacity exists. Architects should document runbooks and automate promotion and traffic shift where possible so recovery is repeatable and timed. Extending RTO after failures, silencing health checks, or concentrating scripts on one laptop worsens operational risk rather than meeting objectives.