You want to allow instances in multiple private subnets across different Availability Zones to access the internet. What is the best practice regarding NAT Gateway deployment?

hard📝 Architecture Q8 of 15

AWS - VPC Fundamentals

ACreate a NAT Gateway in each public subnet in every Availability Zone

BCreate a single NAT Gateway in one public subnet and route all private subnets to it

CUse an Internet Gateway attached to private subnets

DAssign public IPs to all private subnet instances

Step-by-Step Solution

Solution:

Step 1: Understand high availability needs
NAT Gateway is AZ-specific; single NAT Gateway can cause cross-AZ data charges and failure risk.
Step 2: Best practice for multi-AZ
Deploy NAT Gateway in each AZ's public subnet for fault tolerance and performance.
Final Answer:
Create a NAT Gateway in each public subnet in every Availability Zone -> Option A
Quick Check:
Multi-AZ NAT Gateway deployment = one per AZ [OK]

Quick Trick: Deploy NAT Gateway per AZ for high availability [OK]

Common Mistakes:

MISTAKES

Using single NAT Gateway for all AZs
Attaching Internet Gateway to private subnets
Assigning public IPs to private instances

Master "VPC Fundamentals" in AWS

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More AWS Quizzes

You want to allow instances in multiple private subnets across different Availability Zones to access the internet. What is the best practice regarding NAT Gateway deployment?

Step 1: Understand high availability needs

Step 2: Best practice for multi-AZ

Final Answer:

Quick Check:

Want More Practice?