You have a Microsoft Teams Phone deployment. You are deploying a new remote site. You have a Session Border Controller (SBC) that has an E1/T1 Primary Rate Interface (PRI) deployed to the remote…

Question

Options

• AMicrosoft Teams Windows desktops
• Baudio conferencing in Microsoft Teams
• Cauto attendants in Microsoft Teams
• DMicrosoft Skype for Business 3PIP phones

• A
  93% (39)
• C
  2% (1)
• D
  5% (2)

Explanation

Option A is correct because a Teams Phone Survivable Branch Appliance is specifically designed to support Microsoft Teams clients - including Windows desktop apps - during a WAN outage, allowing users to continue making and receiving PSTN calls through the local SBC/PRI connection.

Option B (audio conferencing) is wrong because audio conferencing is a Microsoft cloud-hosted service; it requires an active connection to Microsoft 365 and cannot be delivered locally by an SBA during an outage.

Option C (auto attendants) is wrong for the same reason - auto attendants are cloud-based resources that live entirely in Microsoft's infrastructure and are unavailable without WAN connectivity, regardless of SBA presence.

Option D (Skype for Business 3PIP phones) is wrong because the Teams SBA only supports native Microsoft Teams clients; legacy Skype for Business third-party IP phones are not compatible with the Teams SBA architecture.

Memory tip: Think of the SBA as a "Teams-only lifeboat." It keeps your Teams desktop/mobile clients afloat during a WAN outage, but anything that lives in the cloud (conferencing, auto attendants) or belongs to a different platform (SfB 3PIP) sinks with the WAN link.

No community discussion yet for this question.