MS-721 Sample Questions & Answers

For Teams Rooms on Windows, the SkypeSettings.xml configuration file must be placed in the C:\Users\Skype\AppData\Local\Packages\Microsoft.SkypeRoomSystem_8wekyb3d8bbwe\LocalState directory. The Teams Rooms application process, running under the 'Skype' user account, reads this file at startup to apply any custom configurations.

Microsoft eCDN relies on WebRTC for peer-to-peer communication between clients on the same local network. This communication primarily uses UDP over a range of ports (often including the standard STUN/TURN ports 3478-3481). If a local firewall or network access control list (ACL) is blocking this peer-to-peer UDP traffic, clients cannot discover each other or share video segments, forcing them to fetch content directly from the internet and defeating the purpose of the eCDN.

For any phone number that can be used for outbound calling, including the number on a resource account used for Shared Calling, an emergency address must be assigned to it. This is a mandatory step for E911 compliance. If the emergency address is not set for the number, outbound calling will be blocked.

The Teams Rooms Pro Management portal is specifically designed for advanced management, monitoring, and reporting of Teams Rooms devices. Its 'Reports' section provides detailed analytics on usage, device health, meeting reliability, and hardware inventory, which directly addresses all the manager's requirements.

Local Media Optimization (LMO) is specifically designed for this scenario. It allows media traffic (the actual voice stream) to flow directly between the Teams client and the nearest SBC (e.g., one in Europe), while SIP signaling (call control) still goes to the central Microsoft 365 servers and follows the central routing policies. This avoids media hairpinning and significantly reduces latency, improving call quality for users at remote sites.

The pattern ^2(\d{3})$ correctly matches a 4-digit number that starts with '2'. ^ anchors the match to the beginning of the string, 2 matches the literal digit 2, (\d{3}) captures the following three digits into group 1, and $ anchors the match to the end. The translation +1425882$1 then prepends the required prefix and appends the captured 3 digits ($1), resulting in the correct E.164 number.

This scenario requires a two-stage routing logic which cannot be accomplished within a single call queue. The correct approach is to use two call queues. The first queue is configured with 'Attendant' routing to ring all agents. Its call timeout is set to 30 seconds, and the timeout action is to redirect the call to a second call queue. This second queue is then configured with the 'Longest idle' routing method.

The Teams client relies on the underlying operating system's location services to determine its location, which is then used to query the Location Information Service (LIS) for a matching emergency address. If Windows Location Services are disabled or the Teams app has been denied permission to use them, the client cannot provide location data, and dynamic emergency address updates will fail.

The Teams Shared Device license is specifically designed for devices like common area phones that will be used by multiple people and supports features like hot desking.

The feature itself is enabled and controlled through a Teams IP Phone policy where the 'Hotdesking' setting is turned on. This policy must be assigned to the resource account associated with the phone.

To meet the requirement for automatic sign-out, a SignInMode of UserSignIn must be selected and a HotdeskingTimeout value must be configured within the same IP Phone policy. This ensures sessions are not left open indefinitely.

Microsoft Calling Plans are the ideal solution for this scenario. They provide an all-in-one voice solution where Microsoft acts as the PSTN carrier. This allows the business to acquire and manage phone numbers and calling minutes directly within the Microsoft 365 admin center, offering the simplest deployment and management experience for a new company with no existing carrier relationships.