nerdexam
Microsoft

MS-720 · Question #13

Case Study 2 - Litware, Inc Overview General Overview The network contains an Active Directory forest named contoso.com that syncs to Microsoft 365 by using Azure AD Connect. Domain controllers run…

The correct answer is A. Register an application in Azure Active Directory (Azure AD). B. Run the New-CsTeamsSurvivableBranchAppliancePolicy cmdlet D. Configure the SBC for media bypass. Registering an Azure AD application (A) is a mandatory prerequisite for Teams SBA deployment - the appliance must authenticate with Microsoft 365 services using an app identity. Running New-CsTeamsSurvivableBranchAppliancePolicy (B) creates the policy object that links the SBA…

Plan and configure Direct Routing

Question

Case Study 2 - Litware, Inc Overview General Overview The network contains an Active Directory forest named contoso.com that syncs to Microsoft 365 by using Azure AD Connect. Domain controllers run Windows Server 2019. Physical Locations Contoso has offices in Toronto, New York, and London. Contoso has a manufacturing facility in Vancouver. Contoso has a global sales team that works remotely without a physical corporate office. Existing Environment Active Directory Environment The network contains an Active Directory forest named contoso.com that syncs to Microsoft 365 by using Azure AD Connect. Domain controllers run Windows Server 2019. Microsoft Office 365 Contoso has a Microsoft 365 subscription. All users are assigned Microsoft 365 E3 licenses. Contoso uses Microsoft Exchange Online for email. Network Infrastructure All the offices connect to each other by using a private WAN. The Toronto office has a 1-Gbps internet circuit and the London office has a 100-Mbps internet circuit. Internet access for all the offices is provided through the Toronto and London offices. The remote sales team users connect to the networks by using VPN connections. The remote users use various connection types, including wireless and mobile. Skype for Business Server traffic for the remote users is routed through the VPN connections. Telephony Contoso uses a centralized Skype for Business Server 2015 deployment configured for disaster recovery between the Toronto and London datacenters. Each frontend pool connects to the PSTN through a pair of managed Session Border Controllers (SBCs) that provide Enterprise Voice and dial-in conferencing. Contoso has a Skype for Business Server Survivable Branch Appliance (SBA) and a local SBC that connects to a Primary Rate Interface (PRI) in the Vancouver manufacturing facility. Contoso has hybrid connectivity deployed between Skype for Business Server and Office 365. All SBCs are Microsoft Teams-certified. The returns department has an auto attendant that uses an ID or [email protected]. Requirements Planned Changes Contoso plans to migrate all existing services from Skype for Business Server to Teams. Direct Routing will be deployed for the existing SBCs. Existing meeting rooms have Skype for Business Server video endpoints that are Skype for Business Server-certified. The endpoints are not Teams-certified. You plan to use the video endpoints in Teams until the equipment is replaced with Microsoft Teams Rooms. A limited pilot of the Teams migration and the Direct Routing deployment will occur in the Vancouver facility before deployment to the entire company. Technical Requirements Contoso identifies the following technical requirements: During the limited pilot, the media path must be optimized. Media flow for the remote sales team users must be optimized. All sales team users require inbound toll-free audio conferencing. Users in the Vancouver facility must be able to place emergency calls regardless of internet availability. When users in the returns department dial out, the outbound calls must display Contoso and the department's phone number. The video endpoints for the existing meeting rooms must be able to be used for both voice and video conferencing in Teams meetings. Once Direct Routing is deployed, you need to prepare the environment to support a reams SBA in the Vancouver facility. The solution must meet the technical requirements. Which three actions should you perform? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.

Options

  • ARegister an application in Azure Active Directory (Azure AD).
  • BRun the New-CsTeamsSurvivableBranchAppliancePolicy cmdlet
  • CEnroll the SBA server in Microsoft Intune.
  • DConfigure the SBC for media bypass.
  • EConfigure the SBC for call forking.
  • FEnable ForwardPAI on the online voice gateway.

How the community answered

(34 responses)
  • A
    68% (23)
  • C
    9% (3)
  • E
    18% (6)
  • F
    6% (2)

Explanation

Registering an Azure AD application (A) is a mandatory prerequisite for Teams SBA deployment - the appliance must authenticate with Microsoft 365 services using an app identity. Running New-CsTeamsSurvivableBranchAppliancePolicy (B) creates the policy object that links the SBA to users in Vancouver, enabling call continuity when internet connectivity fails. Configuring the SBC for media bypass (D) directly satisfies the stated technical requirement that "the media path must be optimized" during the Vancouver pilot - bypass routes media directly between the client and SBC, avoiding the Teams Media Processor.

Why the distractors are wrong:

  • C (Intune enrollment): SBA appliances are managed via Teams Admin Center and PowerShell, not Intune - Intune is for user devices/endpoints, not SBCs or branch appliances.
  • E (Call forking): Forking enables simultaneous ringing to multiple endpoints; it plays no role in SBA provisioning or the stated requirements.
  • F (ForwardPAI): This header is used for caller ID passthrough, relevant to the returns department's outbound display requirement - but that's a separate task, not part of SBA deployment prep.

Memory tip: For Teams SBA, think "A-B-D = App, Branch policy, Direct bypass" - you register the App, create the Branch policy, and enable Direct media flow. If a choice sounds like device management (Intune) or call routing features unrelated to survivability (forking, PAI), it's a distractor.

Topics

#Direct Routing#Teams Survivable Branch Appliance (SBA)#Media Bypass#Device Integration

Community Discussion

No community discussion yet for this question.

Full MS-720 Practice