Place a service for domestic users in the cloud.
Consider legal requirements, latency, and continuity during failures.
Which item should be considered when selecting a region?
A region is a physical location, so data residency, user latency, and failure-domain distribution matter.
Detailed explanation
Incorrect. Keyboard layout is not a primary factor in physical region design.
Incorrect. Hostname length does not determine legal or availability requirements.
Incorrect. A console theme is unrelated to region placement.
Correct. Region selection should account for latency, regulatory location requirements, and disaster separation.
Try it yourself
An example you can run in a temporary verification environment.
printf '%s\n' 'latency, data residency, and disaster separation'Expected result
latency, data residency, and disaster separationKey points
- Region
- Data residency
- Failure distribution
Notes
- Environment: クラウド配置設計の概念確認
- Command output formatting can vary slightly by distribution or tool version.
- Run the example in a temporary directory or process when possible.
Foundation review
Placement
Choosing a Region or Availability Zone affects availability, latency, and regulatory requirements.
Data transfer
Cross-Region replication and data-transfer conditions must be checked against the contract and residency requirements.