nerdexam
Microsoft

MS-720 · Question #1

Case Study 1 - Litware, Inc Overview Litware, Inc. is an online retailer. Litware is replacing its telephony platform with Microsoft Teams Phone. Currently, all users are assigned Microsoft 365 E3…

The correct answer is A. Teams Calling Plans. Teams Calling Plans (A) is correct because retail sites have no existing PSTN infrastructure, rely on mobile devices with cellular data, and the technical requirements explicitly state to use "natively supported Teams solutions whenever possible." With Calling Plans, PSTN…

Plan and configure Microsoft Teams Phone

Question

Case Study 1 - Litware, Inc Overview Litware, Inc. is an online retailer. Litware is replacing its telephony platform with Microsoft Teams Phone. Currently, all users are assigned Microsoft 365 E3 licenses. Existing Environment Telephony Environment The existing telecommunications system has several third-party IP-PBXes at the corporate and warehouse sites. Currently, the PBXes are linked through the corporate WAN and an inter-office dial plan is in place. A unique PSTN direct inward dial (DID) is assigned to each user. The last five digits of each DID are used as an extension. Litware piloted Microsoft Skype for Business Server Enterprise Voice, but has since decided to migrate directly to Teams Phone. During the pilot, a response group was created, and the response group is still in use. Agents in the response group use Skype for Business Server- certified handsets. Locations Litware has global retail stores and datacenters. The telephony topology contains the following four types of sites: Corporate sites The corporate sites contain information workers who collaborate by using the Teams desktop client and SharePoint Online. The reception desk at each corporate site has an analog intercom with an integrated door control. Each intercom connects to an existing PBX by using an FXS Analog Telephony Adapter (ATA). SIP trunks are delivered directly to the site by using a resilient WAN that connects directly to the on-site PBX solution. Warehouse sites The warehouse sites are critical to the business. Users at these sites use either the Teams desktop client or the Teams mobile client. Each warehouse has a public announcement (PA) system that connects to the PBX by using a SIP ATA, along with the sites' existing ISDN trunks. Currently, users at the company's warehouse in Georgia can call the PA system by dialing 123456. All calls to emergency services from the warehouses are played over the warehouses' PA system automatically. WAN connectivity at the warehouses can be unreliable, so local PSTN connectivity is preferred as compared to centrally hosted connectivity. Retail sites Each retail site has only one or two desk phones and a specialized point of sale (POS) computer that cannot run the desktop or web versions of the Teams client. Users at the retail sites have the Teams app and an associated data plan installed on their mobile device. Currently, each retail uses a managed SD-WAN appliance to connect to both the internet and the corporate WAN. The users report that in the event of an internet outage at the retail sites, they can use their mobile devices, which have strong reception. Requirements Planned Changes Litware plans to implement the following changes: Maintain the existing emergency call PA integration. Replace the existing IP-PBX solutions by using Teams Phone. Consolidate all its PSTN trunks by using region-specific datacenters, whenever possible During the planned deployment of Teams Phone, Litware will open a new retail site in the United Kingdom that will have five users. Litware does not have any existing telephony in the United Kingdom. Management at the new retail site wants to use Microsoft Teams Calling Plans for the users. You are opening a new warehouse site in Melbourne. The new warehouse will connect to a phone carrier by using a Session Border Controller (SBC). Dialing rules are an area code of two digits beginning with a zero followed by a subscriber number of eight digits. For example, an E.164 number of +61370105550 will be translated to 03 7010 5550 and +61255505550 will be translated to 02 5550 5550. Technical Requirements Litware identifies the following technical requirements: Minimize the amount of voice traffic over the WAN. Whenever possible, use natively supported Teams solutions. Avoid replacing existing analog device adapters and SIP phones. Assign a Microsoft 365 Phone System license to all the users listed in a CSV file. Ensure that the retail sites can place and receive calls in the event of a WAN failure. Assign a phone number of +61370105550 to a user named User1. User1 is located at a corporate site. Ensure that the warehouse sites maintain calling in the event of an internet outage or Teams service failure. Provide users at the United Kingdom retail site with phone numbers. The users must only be allowed to make in-country calls. Replace the response group from the Skype for Business Server Voice Enterprise pilot with a call queue. The agents must be able to use their existing handset. You need to recommend a PSTN solution for the Teams Phone deployment at the retail sites. The solution must meet the technical requirements. What should you include in the recommendation?

Options

  • ATeams Calling Plans
  • BDirect Routing without media bypass
  • COperator Connect
  • DDirect Routing with media bypass

How the community answered

(32 responses)
  • A
    75% (24)
  • B
    3% (1)
  • C
    6% (2)
  • D
    16% (5)

Explanation

Teams Calling Plans (A) is correct because retail sites have no existing PSTN infrastructure, rely on mobile devices with cellular data, and the technical requirements explicitly state to use "natively supported Teams solutions whenever possible." With Calling Plans, PSTN connectivity lives entirely in Microsoft's cloud - so when the local WAN/internet fails, mobile users can still place and receive calls over cellular data without depending on any on-premises equipment.

Option C (Operator Connect) is also a cloud-based approach but introduces a third-party carrier relationship and is less "natively supported" than Calling Plans. The case study also explicitly calls out Calling Plans for the new UK retail site, signaling Microsoft-managed trunking is the preferred route here.

Options B and D (Direct Routing) both require deploying a Session Border Controller (SBC). If the WAN fails, an SBC hosted at a central datacenter becomes unreachable, breaking the survivability requirement - the opposite of what's needed. Media bypass (D) worsens this by routing media directly to the SBC, further exposing the solution to WAN dependency.

Memory tip: Retail = Light footprint. Calling Plans = No SBC, no WAN dependency, runs in Microsoft's cloud. Whenever a scenario says "no existing telephony + mobile users + WAN unreliable," Calling Plans is the Teams-native answer. Reserve Direct Routing for sites that already have an SBC or need carrier flexibility.

Topics

#Teams Calling Plans#PSTN connectivity#Business Continuity#Mobile connectivity

Community Discussion

No community discussion yet for this question.

Full MS-720 Practice