AWS global infrastructure (regions, AZs) - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding AWS Regions and Availability Zones

Which statement correctly describes the relationship between AWS Regions and Availability Zones (AZs)?

A An Availability Zone is a global network hub connecting all AWS Regions.

B An Availability Zone is a collection of Regions grouped by geographic proximity.

C Regions and Availability Zones are the same; the terms can be used interchangeably.

D An AWS Region is a physical location with multiple isolated Availability Zones, each AZ is a separate data center.

💡 Hint

Think about how AWS separates its data centers to improve fault tolerance.

AWS Regions are geographic areas that contain multiple isolated Availability Zones. Each AZ is a separate data center designed to be independent to avoid single points of failure.

❓ Architecture

intermediate

Designing for High Availability Across AWS AZs

You want to design a web application that remains available even if one Availability Zone fails. Which AWS infrastructure setup best supports this requirement?

A Deploy the application across multiple Availability Zones within the same Region.

B Deploy the application in a single Region without specifying AZs.

C Deploy the application in multiple Regions but only one AZ per Region.

D Deploy the application in a single Availability Zone within one Region.

💡 Hint

Consider how AWS AZs provide fault isolation within a Region.

Deploying across multiple AZs in the same Region ensures that if one AZ fails, the application remains available in the other AZs.

❓ service_behavior

advanced

Impact of Region Selection on Latency and Data Residency

You have users primarily in Europe and want to minimize latency while complying with data residency laws. Which AWS Region choice best meets these needs?

A Use the AWS US East (N. Virginia) Region for all users.

B Use the AWS Europe (Frankfurt) Region to serve European users.

C Use the AWS Asia Pacific (Mumbai) Region for European users.

D Use the AWS South America (São Paulo) Region for European users.

💡 Hint

Think about geographic proximity and legal requirements.

Choosing a Region physically located in Europe reduces latency for European users and helps comply with data residency regulations.

❓ security

advanced

Security Implications of Multi-Region Deployments

What is a key security consideration when deploying applications across multiple AWS Regions?

A Security groups automatically synchronize across Regions.

B Data replication between Regions is always encrypted by default without configuration.

C You must manage compliance and data protection policies separately for each Region.

D IAM roles created in one Region are valid in all Regions without changes.

💡 Hint

Think about how AWS Regions are isolated from each other.

Each AWS Region is isolated, so compliance and data protection policies must be managed per Region to meet local laws and security requirements.

✅ Best Practice

expert

Optimizing Cost and Resilience with AWS Global Infrastructure

You want to optimize your AWS deployment for cost while maintaining resilience. Which strategy best balances these goals?

A Deploy critical resources in multiple AZs within one Region and use backups to another Region.

B Deploy all resources in a single AZ to reduce cross-AZ data transfer costs.

C Deploy all resources in multiple Regions with full active-active replication.

D Deploy resources only in the Region with the lowest pricing regardless of user location.

💡 Hint

Consider cost of cross-Region replication and fault tolerance.

Deploying across multiple AZs in one Region provides resilience with lower cost than multi-Region active-active setups. Backups to another Region add disaster recovery without continuous replication costs.