You created a subnet with MapPublicIpOnLaunch: false but instances still get public IPs. What is the likely issue?

medium📝 Debug Q14 of 15

AWS - VPC Fundamentals

You created a subnet with MapPublicIpOnLaunch: false but instances still get public IPs. What is the likely issue?

AThe subnet is associated with a route table that routes to an internet gateway.

BThe instance launch configuration overrides subnet settings to assign public IPs.

CThe VPC has no internet gateway attached.

DThe subnet CIDR block overlaps with another subnet.

Step-by-Step Solution

Solution:

Step 1: Understand subnet vs instance IP assignment
Subnet setting disables automatic public IP assignment, but instance launch settings can override this.
Step 2: Identify cause of public IP despite subnet config
If instance launch config explicitly assigns public IPs, it overrides subnet default behavior.
Final Answer:
The instance launch configuration overrides subnet settings to assign public IPs. -> Option B
Quick Check:
Instance config can override subnet IP assignment [OK]

Quick Trick: Instance launch config can override subnet IP settings [OK]

Common Mistakes:

MISTAKES

Master "VPC Fundamentals" in AWS

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More AWS Quizzes