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

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. You need to validate the limited pilot has been optimized on the technical requirements. What should you use?