A mobile subscriber is experiencing random limited-service outages. Customers report being unable to make calls or browse. The service provider management console is not showing any alarms, errors…

Question

Options

• AMisconfigured federation
• BIP address limitations
• CSSO failure
• DUnavailable directory service

• A
  69% (43)
• B
  5% (3)
• C
  18% (11)
• D
  8% (5)

Explanation

Federation in networking and telecom refers to the trust and routing agreements between different network systems or providers (e.g., between mobile carriers, identity providers, or interconnected networks). A misconfiguration in federation settings would cause connection requests to fail - users can't establish calls or data sessions - without triggering infrastructure-level alarms, because the underlying hardware and services are technically operational. The management console sees the connection failures but not a hardware or service fault. IP address limitations (B) would typically cause consistent exhaustion errors rather than random outages. SSO failure (C) affects user authentication portals, not mobile voice/data connectivity at this level. An unavailable directory service (D) would almost certainly generate alarms and critical logs since it's a core dependency. A silent misconfiguration in federation routing uniquely fits the pattern of failures without alarms.

No community discussion yet for this question.