Manage Meetings and Calling practice questions

Modify the Global (Org-wide default) meeting policy to disable webinars.

Why it fails: Changing the global policy would affect every user in the entire tenant, preventing anyone from hosting webinars. This does not meet the specific requirement of allowing the Marketing department to continue using webinar features while only restricting the Sales team from accessing those specific capabilities in their workflow.

Adjust the Live Events policy to restrict scheduling for the Sales department.

Why it fails: Live Events and webinars are distinct features within Microsoft Teams with different underlying architectures and use cases. Modifying a Live Events policy will have no impact on a user's ability to schedule or host webinars, which are governed specifically by the meeting policy settings in the admin center.

Configure a Messaging policy to remove the webinar icon from the Teams client.

Why it fails: Messaging policies govern chat and channel communication features such as Giphy usage or message deletion, rather than meeting types. Removing icons via messaging policies is not a supported method for controlling the functional ability of a user to schedule or participate in different types of Microsoft Teams meetings.

Check if the user has a Communications Credits balance.

Why it fails: Communications Credits are typically used for Microsoft Calling Plans or toll-free numbers provided by Microsoft. In a Direct Routing scenario, the PSTN connectivity is provided by your own carrier via the SBC, so the call costs and credits are managed externally and do not affect the internal Teams routing logic.

Ensure the user has an Audio Conferencing license assigned.

Why it fails: An Audio Conferencing license allows users to host meetings with dial-in numbers for participants. It is not a requirement for making individual outbound PSTN calls via Direct Routing. Direct Routing requires a Teams Phone license and a properly configured Voice Routing Policy, but not necessarily conferencing capabilities.

Verify the Emergency Calling policy is set to 'Direct Routing'.

Why it fails: Emergency Calling policies define how 911 calls are handled and how location information is transmitted. While critical for safety and compliance, an incorrectly configured emergency policy will not prevent standard, non-emergency outbound calls from being successfully routed through the SBC and out to the public switched telephone network.

The 'Screen sharing mode' setting in the meeting policy.

Why it fails: The screen sharing mode determines whether a user can share their entire screen, a single window, or nothing at all. While it controls the initiation of sharing, it does not directly govern the interactive 'Request Control' feature that allows another participant to take over the sharer's mouse and keyboard inputs.

The 'Allow PowerPoint sharing' setting in the meeting policy.

Why it fails: PowerPoint Live sharing is a specific feature that uploads a presentation to the meeting for interactive viewing. It has its own set of controls and is separate from the standard desktop or window sharing where the 'Request Control' functionality is typically utilized by participants to collaborate on a live document.

The 'Allow IP Video' setting in the meeting policy.

Why it fails: This setting controls whether a user can transmit their own camera feed during a meeting. It has no technical relationship with screen sharing or the ability to remotely control another participant's computer. Video and content sharing are handled by different streams and policy configurations within the Microsoft Teams service architecture.

Attendant routing

Why it fails: Attendant routing rings all agents in the queue simultaneously for every incoming call. The first agent to pick up the call gets it. This method is highly effective for smaller teams where the goal is to ensure the fastest possible response time regardless of which specific agent handles the inquiry.

Overflow routing

Why it fails: Overflow is a condition or a destination for calls when a queue is full or wait times are too long, rather than a method for distributing calls among agents. It defines what happens to the call after it has failed to be answered by the primary group of available agents.

Presence-based routing

Why it fails: Presence-based routing is a toggleable setting that can be applied to any routing method, rather than being a routing method itself. It ensures that calls are only sent to agents whose Teams status is set to 'Available', preventing calls from ringing for users who are currently busy or away.

Direct routing

Why it fails: Direct Routing is a PSTN connectivity option that links your on-premises telephony infrastructure to Microsoft Teams. It is not a call distribution logic used within a Call Queue configuration to manage how calls are presented to a group of internal users or support agents.

The 'Anonymous join' toggle in the Meeting settings.

Why it fails: The anonymous join setting controls whether people who are not signed into a Microsoft 365 account can enter a meeting. While it relates to meeting access and identity, it does not specifically address the visual display or masking of phone numbers for those who dial in via the PSTN.

The 'Caller ID' policy assigned to the meeting organizer.

Why it fails: Caller ID policies are used to control the outbound identity of users when they make calls from Teams to the PSTN. They do not affect how the phone numbers of incoming PSTN participants are displayed or masked within the Teams meeting interface for other attendees to see.

The 'Identity' section of the user's Microsoft 365 profile.

Why it fails: Profile settings in Microsoft 365 manage a user's name, photo, and job title. These are personal identity attributes for authenticated users and do not provide any mechanism for masking the external phone numbers provided by the PSTN network when a guest dials into a Teams conference bridge.

The user has 'Turn on new meeting experience' disabled in their client settings.

Why it fails: While the 'new meeting experience' was once a separate setting, it has long been the standard and only experience in modern Teams clients. Disabling it is no longer an option in current versions, so it cannot be the reason for missing features like Large Gallery in a modern deployment.

The 'Allow IP Video' setting is set to 'false' in the meeting policy.

Why it fails: If 'Allow IP Video' were set to false, the user wouldn't be able to see any video at all, not just the Large Gallery view. Since the issue is specifically about the view mode and not the total absence of video, the problem likely lies with the client-side rendering capabilities.

The meeting was scheduled as a 'Channel Meeting' instead of a private meeting.

Why it fails: The type of meeting—whether channel-based or private—does not restrict the available video view modes. Large Gallery is available in any meeting type as long as the minimum number of participants (usually 10 or more) have their cameras turned on and the client supports the rendering.

Modify the global audio conferencing settings to assign default numbers per user.

Why it fails: Configuring default audio conferencing numbers allows administrators to specify which toll or toll-free numbers appear on meeting invitations generated by users in designated geographic regions or organizational units, ensuring proper departmental branding and routing.

Create a new emergency location policy for every conference bridge.

Why it fails: Emergency location policies apply primarily to dynamic emergency calling for direct routing and phone system users, not audio conferencing bridges. Audio conferencing bridges handle inbound dial-in participants and do not require emergency address associations for inbound toll routing.

Deploy a dedicated Session Border Controller for inbound toll calls.

Why it fails: Microsoft manages audio conferencing bridges natively through Microsoft-provided service numbers and cloud infrastructure. Deploying an on-premises Session Border Controller is unnecessary unless implementing hybrid operator connect or custom direct routing voice trunks.

Assign a Communications Credits license to every meeting participant.

Why it fails: Communications Credits are required by the meeting organizer or tenant to cover outbound dialing or toll-free dial-in charges. Individual external participants dialing in using local toll numbers do not require individual licenses or credits.

The user's assigned dial plan contains incorrect normalization rules.

Why it fails: Dial plans normalize outbound phone numbers typed by users into standard E.164 format. Inbound calls are routed directly from the operator using the E.164 number provisioned in the Microsoft tenant, meaning outbound dial plan errors will not prevent inbound ringing.

The user's emergency calling policy lacks a registered location.

Why it fails: Missing emergency locations trigger compliance warnings or restrict outbound calling in certain jurisdictions, but they do not block inbound calls from routing to a properly licensed and provisioned Teams user endpoint.

Media bypass is disabled on the operator trunk connection.

Why it fails: Media bypass optimizes media path routing by connecting calls directly between the client and the operator's SBC. Disabling it routes media through Microsoft cloud media processors, increasing latency but never causing inbound calls to fail completely.

Location-based routing

Why it fails: Location-based routing restricts PSTN usage based on network topology to prevent toll bypass in regulated countries. It addresses regulatory compliance and cost management rather than optimizing audio media path latency across global regions.

Dynamic emergency calling

Why it fails: Dynamic emergency calling tracks user locations to provide accurate dispatch addresses to public safety answering points during emergency calls. It has no impact on general media routing performance or audio latency for standard business telephone calls.

A localized tenant dial plan

Why it fails: Dial plans handle number normalization and digit translation prior to call setup. They determine how dialed numbers are formatted but do not dictate the network path that audio packets traverse once the call session is established.

Meeting join policy

Why it fails: Meeting join policies govern who can bypass the lobby and join meetings directly. This setting does not provide granular control over the hardware permissions like microphones or cameras once the user has successfully entered the meeting interface, making it ineffective for managing device-level input during an active session.

Calling policy

Why it fails: Calling policies are designed to manage peer-to-peer calling features, such as call forwarding, group calls, and voicemail settings. These policies do not affect participant behaviors or hardware permissions within a scheduled Teams meeting, as they operate independently of the meeting-specific policy framework provided by Microsoft 365.

Live events policy

Why it fails: Live events policies are specific to the Teams Live Events framework, which uses a producer-presenter model. These policies do not apply to standard Teams meetings, which use the meeting policy framework. Using live events for standard meetings would unnecessarily restrict interaction capabilities and complicate the user experience.

Allow private meeting scheduling

Why it fails: This setting controls whether users are allowed to schedule private meetings in their calendar. It has no impact on the recording or transcription capabilities of a meeting once it has started. Changing this setting will only affect the scheduling experience, not the security of the meeting content.

Allow PowerPoint Live

Why it fails: PowerPoint Live is a presentation feature that optimizes the sharing experience for slides. Disabling this does not prevent users from recording or transcribing the meeting. It only forces presenters to share their screen or window, which is unrelated to the security concerns regarding recording and transcription services.

Allow meeting chat

Why it fails: Meeting chat settings control the persistence of the conversation window within the meeting. While important for communication, it does not manage or restrict audio recording or speech-to-text transcription services. This setting operates independently of the recording controls and does not mitigate the risk of audio data collection.

Call Quality Dashboard

Why it fails: While the Call Quality Dashboard provides high-level trends across the organization, it is not the primary interface for investigating a specific user's individual meeting issues. Admins use the user-specific view to drill down into single calls, whereas CQD is intended for aggregate reporting and organizational health monitoring.

Teams Advisor

Why it fails: Teams Advisor is a deployment tool designed to guide administrators through the initial setup and configuration of Microsoft Teams workloads. It does not provide real-time or historical diagnostic data regarding meeting quality, making it useless for troubleshooting individual audio issues after a meeting has already concluded.

Microsoft 365 Audit Logs

Why it fails: Audit logs track administrative actions and user events, such as file deletions or policy changes. They do not store technical telemetry data regarding media quality, such as audio jitter or packet loss, which are essential for troubleshooting poor user experience during Teams calls or meetings.

Meeting room policy

Why it fails: There is no 'Meeting room policy' in the Teams Admin Center that handles the specific device-level automation of joining meetings. Room behaviors are typically managed through the device's configuration profile and the associated Exchange resource mailbox settings, rather than a broad organizational Teams meeting policy.

Calling policy

Why it fails: Calling policies control user-level voice features such as call forwarding and PSTN dial-out permissions. They do not interact with the calendaring or automatic meeting-join functionality of room systems. Applying a calling policy to a room account would not enable the requested meeting automation behavior.

Live events policy

Why it fails: Live events policies define the configuration for broadcasting large-scale events using Teams. They are not intended for managing the standard, recurring meeting join behaviors of conference room hardware. Utilizing these policies would not accomplish the goal of automating daily meeting attendance for room systems.

Messaging policy - Screen sharing

Why it fails: Messaging policies manage chat and channel interaction features, such as message editing or Giphy usage. They do not control meeting-specific media sharing capabilities like screen sharing. Screen sharing is a real-time media function managed by meeting policies, not a text-based communication feature managed by messaging policies.

App permission policy

Why it fails: App permission policies control which third-party or internal applications are available for users to add to their Teams client. They have no impact on the core meeting functionality, such as the ability to share a screen, which is built into the Teams platform itself.

Calling policy - Screen sharing

Why it fails: Calling policies control voice and video call settings, such as hold, transfer, and call forwarding. There is no 'screen sharing' setting within the calling policy. Screen sharing for calls is actually governed by the same meeting policy that governs scheduled meetings, making this option technically incorrect for administration.

Allow chat in meetings

Why it fails: Controlling the chat availability for guests prevents them from sending potentially malicious links or files during the session. If the risk is high, disabling chat for guests ensures that all communication must be verbal and monitored by the organizer, effectively reducing the surface area for social engineering attacks.

Allow meeting recording

Why it fails: While disabling recording is a good practice for data security, it is not a setting specifically designed to manage the 'external guest' experience. It applies to all users in the meeting regardless of their guest status, making it a general policy setting rather than a guest-specific security control.

Audio conferencing dial-in

Why it fails: Audio conferencing settings allow users to join via telephone. While relevant for remote access, this is not a security configuration used to manage guest behavior or permissions within the meeting. It is a connectivity feature that enables broader access rather than securing the meeting environment against unauthorized participants.

The user can only join live events as an attendee.

Why it fails: Setting 'BroadcastMeetingMode' to 'Disabled' does not just limit the user to attendee status; it restricts the creation and potentially the participation in the broadcast infrastructure entirely. The user would be unable to organize or produce events, preventing them from using the broadcast functionality in any capacity.

The user can record broadcasts but not stream them.

Why it fails: The command explicitly sets 'AllowBroadcastRecording' to $False. Therefore, the user is prohibited from recording, and with the broadcast mode disabled, they cannot stream either. The premise that they can record is directly contradicted by the policy settings provided in the command output.

The user can only schedule private meetings.

Why it fails: The 'TeamsMeetingBroadcastPolicy' governs live event/broadcast features only. It has absolutely no impact on the user's ability to schedule or host standard, private, or public Teams meetings. These functions are governed by the standard 'TeamsMeetingPolicy', meaning the user's private meeting capabilities remain completely unaffected by this.

Microsoft 365 Device Management

Why it fails: Microsoft 365 Device Management (Intune) focuses on managing mobile and workstation device compliance, such as patching and OS security settings. It does not provide real-time diagnostic data regarding the specific headset hardware used inside the Teams client during a call, making it irrelevant for troubleshooting call audio.

Teams Meeting Policy

Why it fails: Teams Meeting policies manage the features and security settings for meetings, not the hardware configuration or status of individual peripherals like headsets. While a policy might block hardware, it won't show the real-time status or error codes of a user's headset, making it useless for this troubleshooting task.

Teams Organization-wide settings

Why it fails: Organization-wide settings define global configurations for Teams, such as external access or guest permissions. They are not designed to report on the status of individual client hardware or peripherals. Checking these settings would only provide information about global features, not specific user-level hardware diagnostics needed for troubleshooting.

Security Reader

Why it fails: The Security Reader role is focused on auditing security alerts and compliance data within the Microsoft 365 Security & Compliance center. It does not include the specific permissions required to access the Call Quality Dashboard, as this data is considered telephony and network telemetry, not generic security information.

Billing Administrator

Why it fails: Billing Administrators are focused exclusively on subscription management, invoicing, and payment methods. They have no requirement for access to technical call telemetry or the Call Quality Dashboard. Giving this role access would violate the principle of least privilege, as they perform functions unrelated to Teams technical infrastructure management.

Configure a Session Border Controller (SBC) with a certificate.

Why it fails: The SBC is already configured according to the scenario, and it must have a valid certificate for secure communication with Direct Routing. However, the question states that the SBC is already configured, so this is not an additional component needed. The missing pieces are the PSTN usage and dial plan, which are necessary for call routing and number normalization.

Create a Teams emergency calling policy.

Why it fails: Emergency calling policies define how emergency calls are handled, such as notifying security personnel. They are not required for general PSTN connectivity. While important for compliance, they do not enable outbound or inbound PSTN calls; the essential components are the voice route, PSTN usage, dial plan, and voice policy.

Configure a network topology and assign sites to users.

Why it fails: Network topology and sites are used for Location-Based Routing and dynamic emergency calling, not for basic PSTN connectivity. While they can be important for advanced voice features, they are not required to enable outbound and inbound PSTN calls via Direct Routing. The core components are the SBC, voice route, PSTN usage, and voice policy.

Enable 'Sensitivity labels' and apply a label that enforces encryption to all meetings.

Why it fails: Sensitivity labels can apply encryption to meeting content and invitations, but they are not the same as end-to-end encryption for the meeting media itself. While labels can enforce encryption for data at rest, they do not provide the real-time end-to-end encryption of audio, video, and screen sharing that the policy requires.

Configure a conditional access policy that requires compliant devices for all users.

Why it fails: Conditional access policies control device and network access conditions, not meeting content encryption. They can restrict which devices can join, but they do not provide end-to-end encryption for meeting media. This does not satisfy the requirement for encrypted meetings.

Set the 'AllowCloudRecording' parameter to False in the meeting policy.

Why it fails: AllowCloudRecording controls whether meetings can be recorded. Disabling it prevents recording but does not enforce end-to-end encryption. End-to-end encryption is a separate setting that must be explicitly enabled for meetings, and it is not related to recording capabilities.