nerdexam
Microsoft

MS-721 · Question #127

Case Study 2 - Contoso 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 Deploy a local internet connection.; Implement VPN split tunneling. The correct interaction is to drag 'Deploy a local internet connection' to 'Vancouver facility users' and 'Implement VPN split tunneling' to 'Remote users' to optimize network connectivity for Microsoft 365 services.

Plan and design collaboration communications systems

Question

Case Study 2 - Contoso 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. Drag and Drop Question You need to recommend network design changes that must be implemented before the Skype for Business Server to Microsoft Teams migration. What should you recommend for the Vancouver facility users and the remote sale team users? To answer, drag the appropriate recommendation to the correct users. Each recommendation may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content. NOTE: Each correct selection is worth one point. Answer:

Exhibit

MS-721 question #127 exhibit

Answer Area

Drag items

Decrease the NAT pool size.Implement VPN split tunneling.Deploy a local internet connection.Implement a web proxy server for media traffic.Force TCP instead of UDP for the media traffic of Teams.

Correct arrangement

  • Deploy a local internet connection.
  • Implement VPN split tunneling.

Explanation

The correct interaction is to drag 'Deploy a local internet connection' to 'Vancouver facility users' and 'Implement VPN split tunneling' to 'Remote users' to optimize network connectivity for Microsoft 365 services.

Approach. Based on the case study: The Vancouver facility's internet access is currently provided through the Toronto and London offices (i.e., backhauling internet traffic over the WAN). For a manufacturing facility, this setup can introduce significant latency and consume valuable WAN bandwidth, especially for cloud-based services like Microsoft 365 or real-time media. 'Deploy a local internet connection' (dragged to 'Vancouver facility users') is the optimal solution to provide direct and efficient access to internet-based resources, improving performance and reducing WAN congestion. For remote users, the case study states they connect via VPN and that 'Skype for Business Server traffic for the remote users is routed through the VPN connections.' This implies a full-tunnel VPN setup where all internet traffic, including to Microsoft 365 services, is routed through the corporate network. This increases latency, consumes corporate internet bandwidth, and degrades performance for cloud services. 'Implement VPN split tunneling' (dragged to 'Remote users') allows traffic destined for the internet (like M365 services) to bypass the VPN tunnel and go directly to the internet, while corporate network traffic still uses the VPN, thus optimizing performance for remote users accessing cloud resources.

Common mistakes.

  • common_mistake. Other recommendations are incorrect: 'Decrease the NAT pool size' addresses IP address exhaustion, not network performance or routing bottlenecks. 'Implement a web proxy server for media traffic' is generally not recommended for real-time media in Microsoft 365/Teams, as it can introduce latency and is often bypassed for optimal performance. Additionally, a web proxy handles HTTP/HTTPS, not typically UDP-based real-time media. 'Force TCP instead of UDP for the media traffic of Teams' would degrade real-time media quality, as UDP is preferred for its lower latency and tolerance for packet loss; forcing TCP adds overhead and retransmission delays, which negatively impact real-time communication. These options do not resolve the core routing and performance issues identified for the Vancouver facility or remote users.

Concept tested. Network connectivity optimization for Microsoft 365, including internet breakout for branch offices and VPN split tunneling for remote users, to ensure optimal performance for cloud services and real-time communication (e.g., Teams/Skype for Business).

Topics

#Teams Direct Routing#Network Optimization#Emergency Calling#VPN Split Tunneling

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full MS-721 Practice