Route 53 weighted records with 50/50 weights are sending almost all traffic to one version. What is the likely cause?
Show answer and explanation
Answer: D
Weighted routing considers only the records that are currently healthy, so a failing health check effectively sets that record's weight to zero. If version B is unhealthy, every answer comes from version A even though the configured weights are equal. Checking the health status of each record, and whether a health check is attached at all, explains most reports of weightings that appear ignored.
Why the other options are wrong
- A. Weights are relative to each other, so 50/50, 1/1, or 10/10 all produce an even split; there is no 255 requirement.
- B. Weighted record sets distribute answers globally, not within a Region.
- C. Equal names with different weights are exactly the supported configuration, and the weights decide the proportion.
Exam tip. Unhealthy records drop out of weighted routing entirely, which looks like a weighting bug.