Bird
0
0

You configured weighted routing but all traffic still goes to one server. What is the most likely cause?

medium📝 Debug Q14 of 15
AWS - Route 53
You configured weighted routing but all traffic still goes to one server. What is the most likely cause?
ADNS records have different names
BLatency routing is enabled instead of weighted
CSimple routing policy is selected by mistake
DWeights are set to zero for other servers
Step-by-Step Solution
Solution:

  1. Step 1: Check weight values in weighted routing

    If weights for other servers are zero, all traffic goes to the server with non-zero weight.

  2. Step 2: Rule out other causes

    Latency routing or simple routing would behave differently; different record names do not affect routing weights.

  3. Final Answer:

    Weights are set to zero for other servers -> Option D

  4. Quick Check:

    Zero weights = no traffic [OK]
Quick Trick: Check weights are not zero for all servers [OK]
Common Mistakes:
  • Confusing routing policy type
  • Ignoring zero weights effect
  • Assuming DNS names affect weighted routing

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes
Advanced Security - Secrets Manager for credentials - Quiz 10hard Advanced Security - AWS Config for compliance - Quiz 12easy CloudFormation - Outputs for cross-stack references - Quiz 8hard CloudFormation - CloudFormation vs Terraform awareness - Quiz 12easy Cost Optimization - Data transfer cost awareness - Quiz 1easy Cost Optimization - Why cost management matters - Quiz 1easy EKS - EKS networking with VPC CNI - Quiz 8hard EKS - Why managed Kubernetes matters - Quiz 1easy Route 53 - Why DNS management matters - Quiz 3easy Serverless Architecture - Lambda with S3 event triggers - Quiz 14medium