300-445 · Question #10
Refer to the exhibit. For an over hour during the workday, users trying to join Webex meetings experienced significant issues joining and creating meeting invites. What is a reason for this issue?
The correct answer is C. routing loop in one of the ISP nodes leading to the Webex data center. A routing loop in an ISP node means packets destined for the Webex data center bounce repeatedly between routers without ever arriving, causing timeouts and connection failures for all users routed through that path - this perfectly matches a widespread, prolonged outage…
Question
Options
- AVPN gateway to which the user connected
- Bforwarding loss from one of the nodes in the Webex data center
- Crouting loop in one of the ISP nodes leading to the Webex data center
- DISP of the user's location
How the community answered
(25 responses)- A4% (1)
- B12% (3)
- C68% (17)
- D16% (4)
Explanation
A routing loop in an ISP node means packets destined for the Webex data center bounce repeatedly between routers without ever arriving, causing timeouts and connection failures for all users routed through that path - this perfectly matches a widespread, prolonged outage affecting both meeting joins and invite creation simultaneously. A VPN gateway issue (A) would only impact users connected to that specific VPN, not the broader user population. Forwarding loss within the Webex data center (B) would be an internal Webex infrastructure problem that Webex engineers would resolve quickly and typically appears in their status page, not an ISP routing anomaly visible in a traceroute exhibit. A single user ISP issue (D) would be geographically isolated, not a company-wide incident lasting over an hour.
Memory tip: Think "loop = no delivery" - a routing loop is like a package stuck on a conveyor belt going in circles; no one at Webex ever receives the connection request, so the issue scales to everyone hitting that ISP path.
Topics
Community Discussion
No community discussion yet for this question.