A business application must not stop when one data-center facility has a failure.
Use AWS location boundaries for redundancy.
Which design is closest to high availability?
Deploy redundant resources across multiple Availability Zones in the same Region and distribute traffic between them.
Detailed explanation
Multiple AZs reduce dependence on one facility and support continued service.
Multiple AZs reduce dependence on one facility and support continued service.
Suppressing information does not improve availability.
Suppressing information does not improve availability.
One instance and one AZ create a single failure domain.
One instance and one AZ create a single failure domain.
Additional permissions do not create compute redundancy.
Additional permissions do not create compute redundancy.
Check official documentation
Compare the following points with the official documentation.
AWS Regions and Availability Zones User Guideの複数AZ配置の説明を確認する。
What to confirm
単一AZ障害時に別AZのリソースへ処理を継続できる構成を説明できる。
Key points
- High availability
- Failure domain
- Multiple AZs
Notes
- Environment: AWS公式Global Infrastructureドキュメントの確認
- AWS global infrastructure and service availability can change; verify current details in official AWS documentation.
Foundation review
Benefit versus implementation
Agility and elasticity describe cloud capabilities; a particular Region or AZ is an implementation choice that must satisfy other constraints.
Availability and proximity
Use multiple AZs for failure isolation and suitable Regions or Local Zones for geographic proximity and latency.