AWS - Elastic Load BalancingYou created a target group but your load balancer shows no healthy targets. What is the most likely issue?ALoad balancer is in a different regionBSecurity group blocks health check trafficCTargets are not registered with the target groupDTarget group protocol is set to FTPCheck Answer
Step-by-Step SolutionSolution:Step 1: Check common causes for no healthy targetsTargets not registered or security blocking health checks cause no healthy targets.Step 2: Analyze optionsSecurity group blocking health check traffic prevents health checks from succeeding, causing targets to be unhealthy.Final Answer:Security group blocks health check traffic -> Option BQuick Check:Blocked health checks cause no healthy targets [OK]Quick Trick: Check security groups allow health check ports [OK]Common Mistakes:MISTAKESIgnoring security group rulesAssuming region mismatch causes health check failureUsing unsupported protocols like FTP
Master "Elastic Load Balancing" in AWS9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More AWS Quizzes CloudWatch - CloudWatch metrics - Quiz 10hard CloudWatch - Default vs custom metrics - Quiz 2easy DynamoDB - Partition key and sort key - Quiz 7medium DynamoDB - Scan vs query performance - Quiz 1easy DynamoDB - Creating a DynamoDB table - Quiz 4medium Elastic Load Balancing - Cross-zone load balancing - Quiz 1easy RDS and Relational Databases - Launching an RDS instance - Quiz 5medium SNS and SQS - SNS notification types (email, SMS, Lambda) - Quiz 12easy SNS and SQS - Standard vs FIFO queues - Quiz 13medium SNS and SQS - SNS topics and subscriptions - Quiz 13medium