Bird
0
0

You configured an NLB but notice it is not distributing UDP traffic as expected. What is the most likely cause?

medium📝 Debug Q14 of 15
AWS - Elastic Load Balancing
You configured an NLB but notice it is not distributing UDP traffic as expected. What is the most likely cause?
AHealth checks are disabled for the target group
BThe target group is configured for TCP instead of UDP
CNLB does not support UDP traffic
DNLB requires HTTP listeners for UDP traffic
Step-by-Step Solution
Solution:

  1. Step 1: Check protocol configuration

    NLB supports UDP, but the target group must be set to UDP to handle UDP traffic.

  2. Step 2: Identify misconfiguration

    If the target group is set to TCP, UDP traffic won't be routed correctly.

  3. Final Answer:

    The target group is configured for TCP instead of UDP -> Option B

  4. Quick Check:

    Target group protocol must match traffic [OK]
Quick Trick: Match target group protocol to traffic type [OK]
Common Mistakes:
  • Thinking NLB does not support UDP
  • Ignoring target group protocol settings
  • Assuming health checks cause traffic issues

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
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