A county runs RDS for both production tax systems and short-lived developer sandboxes. How should Multi-AZ be applied to control database cost without harming production RTO?
Select an answer to reveal the explanation.
Short Explanation
Pay for the spare parachute on the plane that carries taxpayers, not on the weekend sandbox glider. Single-AZ for nonprod, Multi-AZ where RTO earns its keep.
Full Explanation
Multi-AZ RDS provides synchronous standby failover that supports production RTO objectives but roughly doubles instance cost. Nonproduction sandboxes rarely need that HA spend, so Single-AZ is appropriate there. Disabling production Multi-AZ to fund sandbox HA inverts risk. Spot self-managed MySQL and Global Database for laptop sandboxes are poor cost and architecture fits.