AWS - Security Groups and Network ACLsAn outbound rule allows all traffic to 10.0.0.0/16 but the instance cannot reach 10.0.1.5. What is a possible cause?AThe subnet mask in the rule is incorrectBThe instance has no internet gateway attachedCThe security group is not attached to the instanceDInbound rules block traffic from 10.0.1.5Check Answer
Step-by-Step SolutionSolution:Step 1: Confirm outbound rule covers 10.0.1.510.0.0.0/16 includes 10.0.1.5, so outbound rule is correct.Step 2: Check inbound rulesIf inbound rules block traffic from 10.0.1.5, communication fails despite outbound allowance.Final Answer:Inbound rules block traffic from 10.0.1.5 -> Option DQuick Check:Inbound rules must allow return traffic from destination [OK]Quick Trick: Inbound rules must allow traffic from destination IP [OK]Common Mistakes:Assuming outbound rules alone control connectivityIgnoring inbound rule restrictions
Master "Security Groups and Network ACLs" in AWS9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More AWS Quizzes AWS CLI - CLI scripting basics - Quiz 3easy Cloud Computing Fundamentals - Why cloud over on-premises - Quiz 4medium EC2 Fundamentals - EC2 pricing models (on-demand, reserved, spot) - Quiz 9hard EC2 Fundamentals - Instance metadata and user data - Quiz 10hard EC2 Fundamentals - Instance states (running, stopped, terminated) - Quiz 5medium EC2 Fundamentals - Amazon Machine Images (AMIs) - Quiz 10hard Identity and Access Management - Assuming roles for temporary access - Quiz 11easy Identity and Access Management - IAM policies (JSON structure) - Quiz 4medium S3 Fundamentals - Buckets and objects concept - Quiz 13medium S3 Fundamentals - S3 storage classes (Standard, IA, Glacier) - Quiz 9hard