Free Microsoft MS-721 Practice Test Questions MCQs

Explanation:
To receive proactive alerts when a specific device (like an executive's handset) goes offline, you need to configure device monitoring and alerting rules. In the Teams admin center, this is done by creating or modifying Device State Rules (or Alert Rules) under the monitoring or device health section. These rules allow you to define conditions (e.g., device goes offline) and specify who receives notifications.

Correct Option:

D. Modify the device state rule.
This is the correct action. In the Teams admin center, you navigate to the area for monitoring device health (often under Devices > Device alerts or similar). Here, you can create or modify a rule that triggers an alert when the specified executive's handset's status changes to "Offline" and configure the notification recipients.

Incorrect Option:

A. Create a Teams app setup policy and assign the policy to all executives.
App setup policies control which apps are pinned to a user's Teams client. They have no relation to monitoring the physical online/offline status of hardware handsets.

B. Create a configuration profile for IP phones.
Configuration profiles define settings on the phone (like screen timeout, ringtones). They cannot be used to create alerts about the phone's connectivity status.

C. Register the handsets by using remote provisioning.
Remote provisioning is the initial process of getting a device registered and managed by Teams. It is a one-time setup step, not a method for ongoing health monitoring and alerting.

Reference:
Monitoring capabilities for Teams devices, including IP phones, are part of the device management and health features in the Teams admin center. Administrators can set up alert rules based on device state changes, such as going offline or experiencing poor network health.

Explanation:
Microsoft Teams Rooms on Windows are specialized devices running a locked-down version of Windows with a dedicated Teams Rooms app. When joining them to an on-premises Active Directory domain, it is critical to prevent standard user or computer Group Policy Objects (GPOs) from being applied to them. These generic policies can disable essential services, change power settings, or apply restrictions that break the certified Teams Rooms experience. The standard best practice is to place them in a separate Organizational Unit (OU) and block policy inheritance on that OU.

Correct Option:

C. Create a separate organizational unit (OU) in Active Directory and block Group Policy Object (GPO) policy inheritance.
This is the correct preparatory step. By creating a dedicated OU for the Teams Rooms devices and blocking inheritance, you ensure that no unintended GPOs from parent OUs are applied. You can then selectively link only the necessary, approved GPOs to this OU.

Incorrect Option:

A. Disable Windows Update on each device.
This is not recommended. Teams Rooms devices require Windows updates and Teams app updates for security and functionality. Updates are managed through the Teams admin center or Intune, not by disabling the service locally.

B. Create a separate organizational unit (OU) in Active Directory and enable No Override for the parent Group Policy Object (GPO) policies.
"Enforced" (No Override) on a parent GPO does the opposite of what you need—it forces that GPO to apply to all child OUs, even if they block inheritance. This would prevent you from shielding the Teams Rooms from harmful policies.

D. Modify the authentication settings in the SkypeSettings.xml file of each device.
The SkypeSettings.xml file is for configuring the Teams Rooms application settings (like account, peripherals). It is not used for configuring domain join authentication or Group Policy settings. Domain join is an OS-level operation.

Reference:
Microsoft's documentation on "Prepare your environment for Microsoft Teams Rooms" explicitly recommends: "Create a separate organizational unit (OU) in Active Directory Domain Services (AD DS) for Microsoft Teams Rooms devices. Block policy inheritance for this OU." This is to prevent GPOs that could interfere with the device operation.

Explanation:
Automatic acceptance of proximity-based meeting invitations is a feature for Teams Rooms that allows the room system to automatically join a meeting when a user with a Bluetooth-enabled device (like a laptop or phone) is detected nearby. This behavior is controlled by a Meeting Policy assigned to the Teams Rooms resource account. The specific setting within the meeting policy is "Automatically admit people" set to "Everyone" or a similar value, along with enabling proximity-based join features.

Correct Option:

B. a meeting policy.
This is the correct configuration point. In the Teams admin center, you create or modify a meeting policy that includes settings for "Automatically admit people" and "Meeting join experience". You then assign this policy to the resource account of the Teams Room to enable automatic admission based on proximity detection.

Incorrect Option:

A. front row.
Front Row is a specific meeting layout in Teams Rooms that optimizes the screen for hybrid meetings with remote participants. It is not related to the automatic acceptance of invitations.

C. Bluetooth beaconing.
Bluetooth beaconing is the underlying technology that enables proximity detection (the Room device broadcasts a Bluetooth signal). However, enabling Bluetooth is a device-level setting on the Teams Room console, not the policy that controls the behavior of automatically accepting the invitation. The policy (B) dictates the action taken when the beacon is detected.

D. coordinated meetings.
This is a feature for scheduling and managing meetings across multiple meeting rooms (like a series of rooms for a large event). It does not control automatic join behavior based on proximity.

E. a customization policy.
Customization policies control organizational branding, such as custom backgrounds and meeting lobby logos. They have no relation to meeting join behavior or proximity settings.

Reference:
Microsoft's documentation on "Use a proximity-based join in Microsoft Teams Rooms" outlines the prerequisites, which include configuring the Meeting policy assigned to the room to "Automatically admit people" as "Everyone" and enabling the proximity join setting. The policy is the administrative control that enables the feature.

Explanation:
Local Media Optimization (LMO) is designed to improve call quality and reduce WAN bandwidth by allowing media to flow directly between a Teams client and the local SBC when both are on the same network. However, LMO has a specific impact on call transfers when the transfer target (the person receiving the transferred call) is outside the local network site. In such a scenario, the media path may need to be re-established through the Microsoft cloud or a different SBC, which can cause a brief interruption or prevent a seamless transfer.

Correct Option:

C. Transfer calls to other users.
This action will be affected. When LMO is enabled and a user transfers a PSTN call to another user who is not located at the same network site (and therefore not behind the same local SBC), the direct media path between the original caller and the local SBC may be broken. The transfer might require the media to be re-anchored through the Microsoft cloud, which can cause a momentary drop in audio or a failed transfer if not configured correctly. It's a known consideration when implementing LMO.

Incorrect Option:

A. Park calls.
Call park is a signaling and cloud-based feature. The parked call is held in a cloud "orbit." LMO, which optimizes the media path for active calls, does not directly interfere with the call park signaling process.

B. Place calls on hold.
Putting a call on hold is a basic call control function that signals the SBC or carrier to play hold music. The media path optimization from LMO does not prevent this action from working.

D. Escalate calls to conference calls.
Escalating a two-party call to a conference (adding participants) is managed by the Teams cloud conferencing service. While LMO might optimize the initial media leg, the conference itself is hosted in the cloud, and media flows to the cloud bridge. LMO does not block this escalation; it may just change the initial media path before the conference starts.

Reference:
Microsoft's documentation on "Local Media Optimization" notes considerations for call transfers, especially consultative transfers, when participants are in different network sites. It explains that the media path may need to be re-established, which can affect the user experience during the transfer operation.

Explanation:
You are enabling PSTN services (meaning Phone System + a PSTN connection method) for new users in a mixed environment with Calling Plans, Direct Routing, and Operator Connect. The action that centrally enables a user for enterprise voice and assigns a specific PSTN usage (which determines their connection method) in the Teams cloud is performed with the Set-CsOnlineVoiceUser cmdlet. This cmdlet is the primary tool for bulk-enabling users with minimal effort, as it can set the EnterpriseVoiceEnabled status and assign the OnlineVoiceRoutingPolicy in one step via PowerShell scripting.

Correct Option:

A. Set-CsOnlineVoiceUser.
This is the correct cmdlet for a cloud-first Teams deployment. You would use it in a script to enable the 100 users, set their EnterpriseVoiceEnabled property to $true, and assign the appropriate OnlineVoiceRoutingPolicy (for Direct Routing/Operator Connect) or confirm licensing (for Calling Plans). This minimizes administrative effort through automation.

Incorrect Option:

B. Set-CsUser.
This is a Skype for Business Server on-premises cmdlet. It is used to configure users homed on a local Skype for Business Server deployment (e.g., EnterpriseVoiceEnabled $true). In a Teams Phone deployment, especially one using cloud PSTN services, this cmdlet is not applicable.

C. Set-CsIPPhonePolicy.
This cmdlet is for managing device configuration policies for Teams IP phones (like screen timeouts, button layouts). It has nothing to do with enabling users for PSTN calling services.

D. Set-CsPhoneNumberAssignment.
This cmdlet is used specifically to assign or remove a phone number from a user. While a critical step, it is typically used after the user has been enabled for enterprise voice (e.g., via Set-CsOnlineVoiceUser). It is not the single cmdlet that "enables PSTN services"; it handles the number assignment part of the process.

Reference:
For enabling users in a cloud Teams Phone environment, the Set-CsOnlineVoiceUser cmdlet is documented as part of the provisioning process, allowing administrators to set the user's voice configuration properties in bulk. Using a PowerShell loop with this cmdlet is the standard method to efficiently enable a large number of users.

Explanation:
The default audio conferencing bridge number is the primary dial-in number that is automatically added to meeting invitations. This setting is configured within the Audio Conferencing settings for your organization, specifically under the Conference bridges section. This is where you manage the bridge's properties, including setting the default toll and toll-free numbers.

Correct Option:

A. the Conference bridges node under Meetings.
This is the correct location. Navigate to Meetings > Conference bridges in the Teams admin center. Here, you can view your organization's conference bridge. By editing the bridge settings, you can select the new Dallas number (which must first be assigned as a Conference Bridge number type) and set it as the default number.

Incorrect Option:

B. the Networks & locations node under Locations.
This section is used for defining network regions, sites, and subnets for purposes like Location-Based Routing (LBR) and Dynamic Emergency Calling. It is not used for configuring audio conferencing dial-in numbers.

C. the Phone numbers node under Voice.
This section (Voice > Phone numbers) is where you acquire, assign, and manage phone numbers (including assigning numbers to the conference bridge). However, simply assigning the number here does not set it as the default for the bridge. That action is performed in the Conference bridges node.

D. the Auto attendants node under Voice.
This section is for creating and managing Cloud Auto Attendants (interactive voice response menus). It has no relation to setting the default dial-in number for audio conferencing.

Reference:
Microsoft's documentation on "Change the phone numbers on your audio conferencing bridge" specifies that to set a default number, you go to the Microsoft Teams admin center > Meetings > Conference bridges, select the bridge, and then change the "Default toll number" or "Default toll-free number" from the available assigned numbers.

Explanation:
This scenario requires setting up a Resource Account Number Routing Rule (also known as an Unassigned Number Routing Rule). This rule catches inbound calls to numbers within a specified range that are not explicitly assigned to a user or service in Teams, and routes them to a designated destination—in this case, the Reception call queue.

Correct Option:

C. Add the DID range of +14035554300 to +14035554309 to the phone number range.
This is the range of unassigned numbers. Numbers +14035554310 to +14035554325 are assigned, so the unassigned blocks are +14035554300-4309 and +14035554326-4329. The rule in the question uses the first unassigned block.

E. From the Microsoft Teams admin center, select Phone numbers, select Routing rules, and then select Add a new rule.
This is where you create the Resource Account Number Routing Rule to handle unassigned numbers.

F. Set Routing options to Voice application and assign the Reception call queue.
A call queue is a Voice Application (along with Auto Attendants). You select this option and then choose the specific "Reception" call queue resource account as the destination.

Incorrect Option:

A. From the Microsoft Teams admin center, select Phone numbers, select Numbers, and then select Add.
This action is for acquiring new numbers from Microsoft's inventory, not for creating routing rules for existing numbers.

B. Add the DID range of +14035554300 to +14035554329 to the phone number range.
This is incorrect because it includes already assigned numbers (+14035554310 to +14035554325). A routing rule for an unassigned number range must not include numbers that are actively assigned to users or services, as it would interfere with their normal operation.

D. Set Routing options to Person in organization and assign the Reception call queue.
"Person in organization" is for routing to a user, not to a call queue (which is a voice application). The wrong destination type.

Reference:
Microsoft's documentation on "Set up resource account number routing rules" details the process: 1) Navigate to Voice > Phone numbers > Routing rules, 2) Add a rule, 3) Define the range of unassigned numbers, and 4) Set the Routing option to "Voice app" and select the target Auto Attendant or Call Queue.

Explanation:
The requirement is to ensure outbound PSTN calls from User1 use the SBC at Site2 after their relocation. The policy that directly controls which SBC is selected for outbound PSTN routing is the Voice Routing Policy. This policy contains PSTN Usage records that are linked to specific Voice Routes, and each route is associated with one or more SBCs. By updating the user's assigned voice routing policy to one configured for Site2's SBC, you control the routing path.

Correct Option:

B. The voice routing policy.
This is the correct policy to change. A voice routing policy authorizes the user for certain types of calls (via PSTN Usages) and determines the specific SBC (or pool) used to route those calls based on the user's location or assignment. Assigning a policy configured with routes pointing to the Site2 SBC ensures User1's calls use that local gateway.

Incorrect Option:

A. The calling policy.
Calling policies control user capabilities like call forwarding, delegation, and call park. They do not determine which SBC is used for outbound PSTN call routing.

C. The caller ID policy.
Caller ID policies control what caller ID number and name are presented on outbound calls. They do not affect the selection of the SBC used to place the call.

D. The dial plan.
A dial plan contains normalization rules that translate dialed numbers (e.g., short extensions) into E.164 format for routing. While a user might have a dial plan for their new site, the dial plan itself does not specify which SBC handles the call. That mapping is done by the voice routes referenced in the voice routing policy.

Reference:
Microsoft's documentation on "Manage voice routing policies" explains that voice routing policies define the available PSTN routes and the associated SBCs. To change the SBC used by a user, you assign a voice routing policy that includes the PSTN usages linked to the desired SBC's routes. This is the standard method for location-based SBC selection in Direct Routing.

Explanation:
This scenario requires manipulating outbound caller ID for a specific Call Queue (a resource account) so that it shows a custom Calling Party Name (CNAM) and a specific phone number. This is achieved by configuring a Caller ID Policy that targets the call queue's resource account. The policy must be set to override the default, replace the caller ID with the resource account's details, and optionally set the Calling Party Name.

Correct Option:

A. From the Microsoft Teams admin center, configure a new caller ID policy.
You must create a new, custom Caller ID Policy specifically for the Customer Service call queue's resource account. This policy will contain the specific settings to modify the outbound caller ID.

D. Set Replace the caller ID with to Resource account.
Within the new caller ID policy, the "Replace the caller ID with" setting must be configured as "Resource account". This ensures the outbound call uses the phone number assigned to the Customer Service call queue's resource account as the caller ID number.

E. Set Override the caller ID policy to On.
In the same custom caller ID policy, the "Override the caller ID policy" setting must be set to On. This is the master switch that allows the policy to replace the caller ID. Without this enabled, the policy will not apply the "Replace the caller ID with" rule.

Incorrect Option:

B. Set Calling Party Name to the organization name.
This setting, within a Caller ID Policy, controls the CNAM (Calling Party Name) sent to the PSTN. For this requirement, you would configure this to "Contoso" within the custom policy. However, option B is listed but not selected in the correct answer set (A, D, E). This indicates the exam question expects the core three actions to be creating the policy (A), setting it to replace with the resource account (D), and turning the override on (E). Setting the Calling Party Name is implied or a subsequent step within the policy creation, not listed as a separate primary action in the correct answer choices provided.

C. From the Microsoft Teams admin center, modify the global (Org-wide default) caller ID policy.
Modifying the global default policy would affect all users in the organization, which violates the requirement that "Other users must NOT be affected." You must create a new policy and assign it only to the specific resource account.

Reference:
Microsoft's documentation on "Caller ID policies in Teams" explains that to change the outbound caller ID for a call queue, you create a caller ID policy with "Override the Caller ID policy" set to On and "Replace the caller ID with" set to "Resource account", then assign that policy to the resource account of the call queue. The Calling Party Name can be set separately within that policy.

Explanation:
The issue is internet link saturation at a remote office caused by 100 attendees each streaming the same live event video independently. This creates redundant traffic. An Enterprise Content Delivery Network (eCDN) is specifically designed to solve this problem for live events and large video broadcasts. It optimizes delivery by caching the video stream locally within the office network (e.g., on a local server or peer-to-peer among clients), so only one copy of the stream crosses the WAN/internet link, drastically reducing bandwidth consumption.

Correct Option:

D. Configure a video distribution provider eCDN.
This is the correct and most effective solution. An eCDN (like from Hive, Kollective, or Ramp) integrates with Teams Live Events to intelligently cache and distribute video streams within the local network of a branch office. This minimizes redundant WAN traffic and prevents link saturation.

Incorrect Option:

A. Configure a network roaming policy.
Network roaming policies in Teams are used to define network sites and subnets for location-based services like Dynamic Emergency Calling. They do not manage bandwidth consumption or video distribution.

B. From Meeting policies, modify Media bit rate (KBs).
Reducing the media bit rate in meeting policies lowers the quality and bandwidth per stream, which could help slightly. However, with 100 attendees, you still have 100 separate streams entering the office. This is a less efficient and impactful solution compared to an eCDN, which eliminates redundancy entirely.

C. Configure Quality of Service (QoS).
QoS prioritizes certain types of network traffic (like voice or video) over others within a congested network. It can help ensure video gets priority but does not reduce the total amount of video traffic crossing the saturated internet link. The root problem is total bandwidth exceedance, not traffic prioritization.

Reference:
Microsoft's documentation on "Use eCDN with Teams live events" explicitly recommends using an eCDN for large events to "optimize network bandwidth utilization" and "avoid network congestion" in scenarios with many viewers in the same location, which is precisely the described problem.