Bird
0
0

Why does AWS recommend using a NAT Gateway instead of a NAT instance for private subnet internet access?

hard📝 Conceptual Q10 of 15
AWS - VPC Fundamentals
Why does AWS recommend using a NAT Gateway instead of a NAT instance for private subnet internet access?
ANAT Gateway is fully managed, scalable, and requires less maintenance
BNAT Gateway allows inbound internet traffic to private instances
CNAT Gateway automatically assigns public IPs to private instances
DNAT Gateway can be deployed without a public subnet
Step-by-Step Solution
Solution:

  1. Step 1: Compare NAT Gateway and NAT instance

    NAT Gateway is a managed AWS service that scales automatically and needs no patching.

  2. Step 2: Understand benefits

    NAT Gateway reduces operational overhead and improves availability compared to NAT instances.

  3. Final Answer:

    NAT Gateway is fully managed, scalable, and requires less maintenance -> Option A

  4. Quick Check:

    NAT Gateway benefits = managed and scalable [OK]
Quick Trick: NAT Gateway is managed and scalable, unlike NAT instance [OK]
Common Mistakes:
  • Thinking NAT Gateway allows inbound traffic
  • Assuming NAT Gateway assigns public IPs to private instances
  • Believing NAT Gateway works without public subnet

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes
AWS Account and Billing - AWS Cost Explorer basics - Quiz 10hard AWS CLI - Using profiles for multiple accounts - Quiz 7medium AWS CLI - Why CLI matters for automation - Quiz 10hard AWS CLI - CLI scripting basics - Quiz 6medium EC2 Fundamentals - Why EC2 matters for compute - Quiz 2easy EC2 Fundamentals - Instance states (running, stopped, terminated) - Quiz 4medium Identity and Access Management - Assuming roles for temporary access - Quiz 2easy Identity and Access Management - IAM policies (JSON structure) - Quiz 2easy S3 Fundamentals - Uploading and downloading objects - Quiz 10hard S3 Fundamentals - S3 lifecycle rules - Quiz 4medium