AWS - Elastic Load BalancingYou set up a load balancer but all traffic goes to a single server. What is the likely mistake?ASecurity group blocks all trafficBListener is set to forward on wrong portCLoad balancer is not createdDTarget group has only one instance registeredCheck Answer
Step-by-Step SolutionSolution:Step 1: Check target group configurationIf only one instance is registered in the target group, all traffic goes to that instance.Step 2: Verify listener and load balancer existenceListener forwarding on wrong port or missing load balancer would cause no traffic or errors, not single server traffic.Final Answer:Target group has only one instance registered -> Option DQuick Check:Single server traffic = one target instance [OK]Quick Trick: Check target group instance count first [OK]Common Mistakes:Assuming listener port causes single server trafficThinking load balancer absence sends trafficBlaming security group for traffic routing
Master "Elastic Load Balancing" in AWS9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More AWS Quizzes API Gateway - Lambda integration - Quiz 4medium API Gateway - API deployment and stages - Quiz 12easy API Gateway - API Gateway throttling - Quiz 7medium API Gateway - REST API creation - Quiz 2easy AWS Lambda - Lambda pricing model - Quiz 14medium Auto Scaling - Scaling policies (target tracking, step, simple) - Quiz 13medium Auto Scaling - Scheduled scaling - Quiz 7medium DynamoDB - DynamoDB capacity modes (on-demand, provisioned) - Quiz 9hard SNS and SQS - Dead letter queues - Quiz 6medium SNS and SQS - SQS queue concept - Quiz 10hard