A company manages several AWS accounts within an AWS Organization. A system administrator notices that when deploying EC2 instances in the Availability Zone named 'us-east-1a' in Account A and Account B, the physical data centers hosting these instances might be different.
Which of the following statements explains this behavior and identifies the correct method to reference the same physical infrastructure across both accounts?
- AAWS automatically assigns the same Availability Zone name to the same physical data center across all accounts. To coordinate resource placement, the company should use the default subnet mappings in each account.
- BAvailability Zone names are based on the geographical coordinates of the IAM user creating the resources. To reference the same physical location, both accounts must create resources from the same physical office location.
- AWS maps Availability Zone names (such as 'us-east-1a') independently for each AWS account to ensure resource distribution. To reference the same physical Availability Zone across accounts, the company must use the Availability Zone ID (AZ ID), such as 'use1-az1'.Answer
- DAWS regions are logically partitioned into virtual environments that prevent physical sharing of hardware. To share the same physical infrastructure, the company must deploy all resources in a single virtual private cloud (VPC) across both accounts.
Answer
AWS maps Availability Zone names (such as 'us-east-1a') independently for each AWS account to ensure resource distribution. To reference the same physical Availability Zone across accounts, the company must use the Availability Zone ID (AZ ID), such as 'use1-az1'.
The correct answer explains that AWS maps Availability Zone names (like 'us-east-1a') independently to physical infrastructure for each AWS account to ensure even resource distribution. To reference the same physical Availability Zone across accounts, the company must use the Availability Zone ID (AZ ID), such as 'use1-az1'.
Step-by-Step Solution
Key Concept
AWS Availability Zone Logical Names vs. Physical AZ IDs