AWS - VPC FundamentalsHow can you allow inbound HTTPS traffic to a web server in a private subnet without assigning it a public IP?AAdd a route to the internet gateway in the private subnet's route table.BPlace an Application Load Balancer in a public subnet and route traffic to the private subnet.CAssign a public IP to the instance in the private subnet.DUse a NAT Gateway to forward inbound HTTPS traffic.Check Answer
Step-by-Step SolutionSolution:Step 1: Understand inbound access to private subnetInstances in private subnets cannot receive direct inbound internet traffic without public IP or special setup.Step 2: Use Load Balancer in public subnetAn Application Load Balancer (ALB) in a public subnet can accept HTTPS traffic and forward it to instances in private subnet.Final Answer:Place an Application Load Balancer in a public subnet and route traffic to the private subnet. -> Option BQuick Check:ALB in public subnet enables inbound to private subnet [OK]Quick Trick: Use ALB in public subnet for private instance access [OK]Common Mistakes:MISTAKESAssigning public IP to private subnet instanceAdding IGW route to private subnetUsing NAT Gateway for inbound traffic
Master "VPC Fundamentals" in AWS9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More AWS Quizzes AWS Account and Billing - Root user vs IAM user - Quiz 13medium EC2 Fundamentals - Elastic IP addresses - Quiz 10hard EC2 Fundamentals - Key pairs for SSH access - Quiz 13medium EC2 Fundamentals - Why EC2 matters for compute - Quiz 1easy Identity and Access Management - Multi-factor authentication setup - Quiz 11easy Identity and Access Management - Why IAM is foundational - Quiz 5medium Identity and Access Management - Policy evaluation logic - Quiz 1easy S3 Fundamentals - Static website hosting on S3 - Quiz 15hard VPC Fundamentals - Internet Gateway for public access - Quiz 7medium VPC Fundamentals - Default VPC overview - Quiz 14medium