300-445 · Question #66
Refer to the exhibit. An engineer receives an alert for high packet loss from the ISP edge for a BGP test, and the path visualization shows the ISP is peering in another city rather than the local…
The correct answer is A. Contact the ISP and request to peer locally. Option A is correct because the alert reveals the ISP is peering in a different city instead of locally, which introduces unnecessary latency and increases the chance of packet loss - the very symptom being observed. The fix is straightforward: request that the ISP establish a…
Question
Options
- AContact the ISP and request to peer locally.
- BContact the ISP and request to peer in another city.
- CContact the ISP and request to change the routing protocol.
- DContact the ISP and request to change the ASN.
How the community answered
(56 responses)- A75% (42)
- B14% (8)
- C4% (2)
- D7% (4)
Explanation
Option A is correct because the alert reveals the ISP is peering in a different city instead of locally, which introduces unnecessary latency and increases the chance of packet loss - the very symptom being observed. The fix is straightforward: request that the ISP establish a local peering point so traffic takes the shortest, most direct path.
Why the distractors are wrong:
- B is the opposite of the fix - peering in another city is already the problem causing packet loss.
- C is irrelevant; BGP is the standard exterior routing protocol for ISP peering, and changing protocols wouldn't resolve a geographic path issue.
- D is irrelevant; ASN (Autonomous System Number) is an identifier, not a routing path decision - changing it wouldn't move where the peer physically connects.
Memory tip: Think "path visualization = geography problem." When a test shows traffic taking a longer geographic route than expected, the answer is almost always about where you peer, not how (protocol) or who (ASN). Local problem → request local peering.
Topics
Community Discussion
No community discussion yet for this question.