The service must continue after a major disaster, and latency for overseas users should be reduced.
Review reasons for using multiple AWS Regions.
Choose TWO valid reasons.
Multiple Regions can support disaster recovery and business continuity, and can place workloads closer to geographically distributed users.
Detailed explanation
Regional placement can reduce the network distance to users in different geographic areas.
Regional placement can reduce the network distance to users in different geographic areas.
A separate Region is an option for recovery and continuity after a wide-area failure or disaster.
A separate Region is an option for recovery and continuity after a wide-area failure or disaster.
Using multiple Regions does not make data transfer unconditionally free.
Using multiple Regions does not make data transfer unconditionally free.
Failures within one AZ are addressed by AZ-level redundancy; adding a Region does not guarantee that a failure cannot occur.
Failures within one AZ are addressed by AZ-level redundancy; adding a Region does not guarantee that a failure cannot occur.
Check official documentation
Compare the following points with the official documentation.
AWS CLF-C02 Domain 3.2の複数Regionの利用目的を確認する。
What to confirm
DRと利用者のレイテンシーを複数Regionの代表的な目的として説明できる。
Key points
- Multiple Regions
- Disaster recovery
- Business continuity
- Latency
Notes
- Environment: AWS公式CLF-C02試験ガイドの確認
- Confirm current capabilities and terminology in the official AWS documentation.
Foundation review
Regional trade-off
Additional Regions can improve recovery and proximity but introduce replication, operations, and transfer considerations.
Failure scope
An AZ failure and a Region-wide disaster are different failure domains.