AWS - Elastic Load BalancingAn NLB is not forwarding traffic to targets even though they are healthy. What could be a common misconfiguration?ATargets registered with correct port numbersBSecurity group attached to targets blocking inbound traffic from client IP addressesCNLB configured with cross-zone load balancing enabledDHealth checks passing successfullyCheck Answer
Step-by-Step SolutionSolution:Step 1: Identify common network issuesIf security groups on targets block inbound traffic from client IP addresses, traffic will not reach targets despite health checks passing.Step 2: Evaluate other optionsCross-zone load balancing enabled is not a cause for blocking traffic; correct ports and passing health checks indicate proper setup.Final Answer:Security group attached to targets blocking inbound traffic from client IP addresses -> Option BQuick Check:Security group blocking = no traffic forwarded [OK]Quick Trick: Check security groups allow inbound from clients [OK]Common Mistakes:Ignoring security group rulesBlaming cross-zone load balancingAssuming health checks guarantee traffic flow
Master "Elastic Load Balancing" in AWS9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More AWS Quizzes API Gateway - API keys and usage plans - Quiz 4medium API Gateway - API keys and usage plans - Quiz 13medium CloudWatch - Alarm actions (SNS, Auto Scaling) - Quiz 12easy DynamoDB - Why DynamoDB for NoSQL - Quiz 13medium Elastic Load Balancing - Listener rules and routing - Quiz 4medium Elastic Load Balancing - Health checks configuration - Quiz 8hard Elastic Load Balancing - Listener rules and routing - Quiz 11easy RDS and Relational Databases - Launching an RDS instance - Quiz 8hard SNS and SQS - Sending and receiving messages - Quiz 2easy SNS and SQS - SQS queue concept - Quiz 8hard