Architects propose multi-AZ deployment for a county permitting API to improve reliability. Finance will not approve until the cost impact of that HA choice is visible. What should the solutions architect emphasize before approval?
Select an answer to reveal the explanation.
Short Explanation
HA is not a free lunch. Spreading across two Availability Zones often means paying for two of several things—and leadership should see that bill before they stamp yes. Visibility first, then the reliability win.
Full Explanation
Multi-AZ architectures improve fault isolation but typically increase spend for duplicated compute, storage replicas, and cross-AZ data transfer. Professional practice is to quantify those incremental costs with Pricing Calculator, Cost Explorer, or CUR-based estimates so stakeholders approve HA with eyes open. Multi-AZ does not magically cut cost, AZ labels are not free, and SCPs do not universally forbid multi-AZ.