A business team wants to test a feature quickly, while the service must continue during an AZ failure.
Map each requirement to a cloud benefit.
Which TWO mappings are appropriate?
Agility supports rapid experimentation, and multi-AZ redundancy supports high availability.
Detailed explanation
Multiple AZs separate failure domains and support continued service.
Multiple AZs separate failure domains and support continued service.
Physical procurement slows experimentation and is not agility.
Physical procurement slows experimentation and is not agility.
Agility supports short feedback cycles and quick resource changes.
Agility supports short feedback cycles and quick resource changes.
One instance in one AZ remains a single failure domain.
One instance in one AZ remains a single failure domain.
Check official documentation
Compare the following points with the official documentation.
AWS Regions and Availability Zones User GuideとAWS Cloudの価値提案を確認する。
What to confirm
事業要件を俊敏性と高可用性の設計目標へ対応付けられる。
Key points
- Agility
- High availability
- 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.