AWS - Elastic Load BalancingA load balancer is configured but users report slow responses. Which misconfiguration could cause this?AHealth check interval is too long, delaying detection of failed serversBLoad balancer is set to distribute traffic evenlyCSSL certificate is correctly installedDAuto scaling is enabled for target serversCheck Answer
Step-by-Step SolutionSolution:Step 1: Analyze impact of health check settingsIf health checks run too slowly, failed servers remain in rotation longer, causing slow responses.Step 2: Identify which option causes slow user experienceHealth check interval is too long, delaying detection of failed servers explains a delay in removing bad servers, leading to slow responses.Final Answer:Health check interval is too long, delaying detection of failed servers -> Option AQuick Check:Slow health checks = Slow user responses [OK]Quick Trick: Fast health checks keep traffic flowing smoothly [OK]Common Mistakes:MISTAKESThinking even traffic distribution causes slownessAssuming SSL affects speed directlyBelieving auto scaling causes slowness
Master "Elastic Load Balancing" in AWS9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More AWS Quizzes API Gateway - REST API creation - Quiz 6medium Auto Scaling - Auto Scaling with ELB integration - Quiz 14medium CloudWatch - Why monitoring matters - Quiz 6medium CloudWatch - Alarm actions (SNS, Auto Scaling) - Quiz 10hard DynamoDB - Secondary indexes (GSI, LSI) - Quiz 12easy DynamoDB - Partition key and sort key - Quiz 13medium Elastic Load Balancing - Target groups concept - Quiz 2easy Elastic Load Balancing - Cross-zone load balancing - Quiz 8hard Elastic Load Balancing - Network Load Balancer (NLB) - Quiz 6medium RDS and Relational Databases - RDS backup and snapshots - Quiz 12easy