Bird
0
0

An engineer created a NAT Gateway in a public subnet but forgot to attach an Elastic IP. What will be the result?

medium📝 Debug Q7 of 15
AWS - VPC Fundamentals
An engineer created a NAT Gateway in a public subnet but forgot to attach an Elastic IP. What will be the result?
APrivate subnet instances will access internet directly
BNAT Gateway will assign public IPs automatically
CInternet Gateway will route traffic without issues
DInstances in private subnet will not have internet access
Step-by-Step Solution
Solution:

  1. Step 1: Understand Elastic IP role

    NAT Gateway requires Elastic IP to communicate with internet.

  2. Step 2: Effect of missing Elastic IP

    Without Elastic IP, NAT Gateway cannot route outbound traffic properly.

  3. Final Answer:

    Instances in private subnet will not have internet access -> Option D

  4. Quick Check:

    NAT Gateway needs Elastic IP for internet access [OK]
Quick Trick: NAT Gateway without Elastic IP blocks internet access [OK]
Common Mistakes:
  • Assuming NAT Gateway auto-assigns public IPs
  • Thinking Internet Gateway fixes NAT Gateway issues
  • Believing private subnet can access internet directly

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