AWS - Route 53You created a private hosted zone but your EC2 instances cannot resolve the domain names inside it. What is the most likely cause?AThe private hosted zone is not associated with the VPCBThe hosted zone is public instead of privateCThe domain name is misspelled in the recordDThe EC2 instances do not have internet accessCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand private hosted zone requirementsPrivate hosted zones must be linked to one or more VPCs to work.Step 2: Identify why EC2 can't resolve namesIf the private hosted zone is not associated with the VPC where EC2 runs, DNS queries fail.Final Answer:The private hosted zone is not associated with the VPC -> Option AQuick Check:Private hosted zone needs VPC association [OK]Quick Trick: Private hosted zones must link to VPCs to resolve names [OK]Common Mistakes:Assuming public/private mix-up causes resolution failureIgnoring VPC association requirementThinking internet access affects private DNS resolution
Master "Route 53" in AWS9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More AWS Quizzes Architecture Best Practices - Disaster recovery strategies (backup, pilot light, warm standby) - Quiz 15hard Architecture Best Practices - Multi-tier architecture patterns - Quiz 15hard CloudFormation - Outputs for cross-stack references - Quiz 2easy CloudFormation - Stack drift detection - Quiz 8hard Cost Optimization - Why cost management matters - Quiz 2easy ECS and Fargate - Fargate vs EC2 launch type - Quiz 2easy ECS and Fargate - Task definitions - Quiz 3easy Route 53 - Health checks with Route 53 - Quiz 3easy Serverless Architecture - Lambda with API Gateway pattern - Quiz 11easy Serverless Architecture - Cognito for user authentication - Quiz 2easy