An engineer is designing a load balancing solution for two Cisco Unified Border routers. The first router (cube1.abc.com) takes 60% of the calls and the second router (cute2.abc.com) takes 40% of…

Question

Options

• Asip_udp.abc.com 60 IN SRV 1 40 5060 cube2.abc.com
• Bsip_udp.abc.com 60 IN SRV 3 60 5060 cube2.abc.com
• Csip_udp.abc.com 60 IN SRV 60 1 5060 cube1.abc.com
• Dsip_udp.abc.com 60 IN SRV 2 60 5060 cube1.abc.com
• Esip_udp.abc.com 60 IN SRV 1 60 5060 cube1.abc.com

• A
  81% (21)
• B
  4% (1)
• C
  12% (3)
• D
  4% (1)

Explanation

DNS SRV records have the format: _service._protocol.domain TTL IN SRV Priority Weight Port Target. For load balancing (not failover), both records must have the same Priority value so DNS clients distribute traffic based on Weight. A higher weight means more traffic. Option E: 'SRV 1 60 5060 cube1.abc.com' - Priority 1, Weight 60, routes 60% to cube1. Option A: 'SRV 1 40 5060 cube2.abc.com' - Priority 1, Weight 40, routes 40% to cube2. With equal priority (1) and weights of 60 and 40, the DNS resolver distributes calls proportionally: 60/(60+40) = 60% to cube1, 40/(60+40) = 40% to cube2. Options B, C, and D use different priorities or incorrect weight values that would not achieve a 60/40 load balance.

No community discussion yet for this question.