Microsoft MS-700 Microsoft 365 Certified: Teams Administrator Associate Exam Dumps and Practice Test Questions Set 5 Q81-100

Visit here for our full Microsoft MS-700 exam dumps and practice test questions.

Question 81: 

Your organization wants to prevent users from sending messages to large numbers of internal users simultaneously to reduce message noise. What should the Teams administrator configure?

A) Messaging policy restricting mass messaging
B) App permission policy
C) Teams update policy
D) External access restrictions

Answer: A)

Explanation: 

A messaging policy contains the settings that regulate communication behavior within Teams, especially when controlling who can initiate certain types of messaging interactions. Restricting mass messaging is governed within this policy, because the communication limits are built into how internal users interact with one another. When mass messaging is restricted, users cannot send messages to large groups or create unnecessary communication overload. This aligns exactly with the requirement of preventing users from distributing messages too broadly throughout the organization.

An app permission policy is used to allow or block apps within the Teams environment. This configuration does not regulate messaging behavior between internal users and does not provide controls for limiting broad distribution messages. Since the goal is to prevent users from sending messages to many recipients simultaneously, adjusting which apps are permitted would not influence this communication pattern.

A Teams update policy is designed to regulate how clients receive updates. It controls behavior like preview features or update channels. This type of policy affects the Teams user interface or available features but does not govern how many internal recipients a user can message at once. Because it concerns software behavior rather than communication limits, it cannot fulfill the requirement.

External access restrictions determine whether users can communicate with domains outside the organization. These restrictions apply to communication between different tenants, not within a single organization. Managing external domains does not regulate the message volume or message distribution inside the organization, making it irrelevant for controlling internal messaging noise.

Evaluating these four configurations makes clear that the only mechanism capable of restricting broad internal communication is the messaging policy. By adjusting the settings within this policy, administrators can ensure users are prevented from sending messages to large groups or creating unnecessary internal communication disruptions, making it the correct configuration.

Question 82: 

A company wants to ensure that only specific senior managers can bypass the lobby when joining any internal meeting. What should the administrator configure?

A) Assign a custom meeting policy
B) Modify global messaging policies
C) Change external access settings
D) Create a new app setup policy

Answer: A)

Explanation: 

Assigning a custom meeting policy allows an organization to provide unique meeting permissions to a specific set of users. This includes configuring who is allowed to bypass the lobby automatically. By assigning a policy only to senior managers, they will receive this elevated privilege while other users follow the standard behavior. This ensures internal meeting controls remain consistent but also flexible enough to provide exceptions to designated individuals.

Modifying global messaging policies would change how users communicate within Teams, but it would not control how they join meetings. Messaging rules focus on chat, file uploads, and similar communication mechanisms. Adjusting these rules would not influence whether a user bypasses a lobby or waits for the organizer to admit them.

Changing external access settings would affect communication with users in other organizations. External access does not determine how internal users join internal meetings. Internal users will not be impacted by these rules when joining internal organizational meetings, making it irrelevant to the requirement of allowing specific internal managers to bypass a lobby.

A new app setup policy determines which apps appear pinned for a user group. While useful for customizing user interface experiences, it does not influence meeting admittance rules. Changing app layouts would not determine whether someone bypasses the lobby upon joining a meeting.

Through evaluation, only meeting policies contain the controls needed to uniquely assign lobby bypass permissions to specific internal users. A custom meeting policy allows fine control over joining behavior and ensures only designated senior managers receive this capability.

Question 83: 

Your organization requires that all Teams recordings created by a specific department expire after 60 days automatically. Which configuration meets this requirement?

A) Meeting recording expiration policy
B) OneDrive storage quota
C) App permission policy
D) Live captions settings

Answer: A)

Explanation: 

A meeting recording expiration policy directly controls how long recordings remain accessible before they are automatically deleted. By setting this value to 60 days for a specific department through policy assignment, the recordings created by that group will follow the defined retention period without manual intervention. This fulfills the requirement precisely because expiration is built directly into the recording policy.

A OneDrive storage quota determines how much data individuals are allowed to store. While recordings consume space in OneDrive or SharePoint, adjusting the quota does not automatically delete content. Instead, it sets maximum storage limits. Because the requirement mandates automatic deletion after a specific number of days, storage quotas cannot accomplish the timing-based requirement.

An app permission policy governs which applications users are allowed to access. This has no impact on recording retention or expiration timing. Whether an application is allowed or blocked does not determine when recordings are deleted. Thus, it does not address the need to automatically expire recordings.

Live captions settings regulate whether users can enable captions in meetings. Captions help accessibility, but they are unrelated to the lifecycle of meeting recordings. Adjusting caption settings will not cause a recording to expire or be deleted automatically.

By comparing these configurations, only a meeting recording expiration policy provides a mechanism that targets a specific department and enforces automatic deletion timelines. Therefore, it is the correct configuration.

Question 84: 

The IT department wants to block anonymous users from joining meetings unless explicitly invited. Which configuration should be updated?

A) Teams meeting policy
B) Email security rules
C) App setup policy
D) Teams device policy

Answer: A)

Explanation: 

A Teams meeting policy governs who can join meetings and under what circumstances. Adjusting the setting that controls anonymous join behavior ensures that individuals who are not authenticated cannot enter meetings unless permitted by the organizer. This aligns precisely with the requirement of limiting anonymous attendance while still allowing invited participants.

Email security rules relate to email filtering and access protection. They do not govern meeting attendance in Teams and therefore cannot determine whether anonymous individuals are allowed to join meetings. Adjusting email controls will not affect Teams meeting access.

An app setup policy controls which applications appear for users inside Teams. While this shapes user interface elements, it has no relationship to meeting join permissions or authentication requirements. Changing app presentation does not restrict anonymous conferencing access.

A Teams device policy is used for Teams-certified devices and handles hardware-specific behaviors. It does not regulate meeting access for anonymous attendees. Device policies apply only to specialized devices, not the meeting environment itself.

After reviewing these configurations, the meeting policy stands out as the correct method for blocking anonymous join behavior while still allowing specific exceptions for invited participants.

Question 85: 

You want to prevent users from sharing their screen during Teams meetings unless they are presenters. What should be configured?

A) Teams meeting policy
B) Voice routing policy
C) App permission policy
D) Teams update policy

Answer: A)

Explanation: 

A Teams meeting policy includes settings related to screen sharing, presentation permissions, and other meeting behaviors. By configuring screen-sharing permissions to be available only to presenters, users who join as attendees will automatically be prevented from sharing their screen. This provides a structured and secure meeting environment, aligning exactly with the requirement.

A voice routing policy governs how calls are routed through PSTN networks. Because voice routing controls telephony flow rather than meeting interaction behavior, it does not affect screen-sharing capabilities within Teams meetings.

An app permission policy regulates which applications users are allowed to access. It has no impact on screen-sharing privileges, which occur within the meeting framework rather than application controls.

A Teams update policy determines how the Teams client receives updates. Although important for feature rollouts, update settings do not affect presentation privileges in meetings.

Evaluating all these configurations reveals that only the meeting policy includes the necessary controls for restricting screen sharing to presenters only.

Question 86:

A Teams administrator must ensure that only users with the E5 license can create Teams meeting recordings, while all other users should be prevented from recording. What should the administrator configure?

A) Assign a separate Teams meeting policy that disables recording to non-E5 users
B) Disable cloud recording at the tenant level
C) Block access to OneDrive and SharePoint for non-E5 users
D) Create a compliance retention policy for recordings

Answer: A)

Explanation: 

To limit recording capabilities based on licensing tiers, assigning a separate meeting policy for non-E5 users is the correct configuration. This meeting policy can disable recording for that population while allowing E5 users to retain their recording privileges through a different policy. Meeting policies are applied at the user level and directly control the ability to initiate a recording, making this approach perfectly aligned with the requirement.

Disabling cloud recording at the tenant level removes recording for everyone in the organization, regardless of licensing. This is far more restrictive than required. Since the goal is to allow E5 users to record while blocking others, a tenant-wide disablement would eliminate recording entirely. That would conflict with the need for selective functionality and therefore is not suitable for the scenario.

Blocking access to OneDrive and SharePoint introduces storage and collaboration problems that extend far beyond recording restrictions. Even though meeting recordings are stored in OneDrive or SharePoint, disabling these services prevents users from performing essential daily tasks, including file storage, sharing, and teamwork. Additionally, blocking these services does not prevent the ability to start a recording; it only prevents storage, which would cause errors rather than proper feature restriction.

A compliance retention policy governs how long content is stored and managed. It does not determine whether someone can create a recording. Retention policies are applied after a recording exists, not before. They regulate lifecycle, not capability. While important for data governance, they offer no means of enforcing who can or cannot initiate a recording.

After examining all configurations, using a dedicated meeting policy assigned to non-E5 users is the only method that fulfills the objective. Meeting policies allow precise, user-level control over recording permissions and can differentiate behaviors between license types. This is the intended way to implement recording restrictions, ensuring licensing-based functionality is respected.

Question 87:

A company wants all new Teams to be created with private membership by default. Which setting should the administrator configure?

A) Teams creation template
B) Sensitivity labels for Teams
C) Microsoft 365 group creation policy
D) Default privacy type in Teams policies

Answer: D)

Explanation: 

Adjusting the default privacy type in Teams policies establishes whether newly created Teams default to public or private membership. By configuring this setting to private, every new Team automatically restricts access, ensuring only invited members can join. This is the precise behavior the requirement describes and gives administrators centralized control over default creation behavior without restricting the ability to create Teams.

Using Teams creation templates allows the administrator to preconfigure channels, tabs, and apps for new Teams. While templates streamline structural consistency, they do not inherently dictate privacy defaults. Templates focus on configuration and layout, not membership controls. Therefore, templates cannot meet the requirement of forcing all new Teams to begin as private.

Applying sensitivity labels to Teams indeed influences privacy, external sharing, and guest access restrictions, but they rely on users selecting the appropriate label during Team creation. Sensitivity labels do not automatically impose a default privacy state for all new Teams unless manually chosen. The requirement asks for a universal default without user action, meaning labels cannot enforce the setting consistently.

A Microsoft 365 group creation policy regulates who can create groups. Restricting group creation does not affect the privacy state of the Team created by those who still have permission. This setting governs permissions, not privacy defaults. Even with limited group creators, Teams may still be created publicly unless privacy defaults are configured elsewhere.

Ultimately, modifying the default privacy type within Teams policies ensures that every Team created system-wide begins as private, fulfilling the requirement exactly.

Question 88:

An organization wants to limit the use of @mentions so only Team owners can use @team and @channel mentions. What should be configured?

A) Team-level settings
B) Messaging policies
C) App setup policies
D) Meeting policies

Answer: A)

Explanation: 

Team-level settings offer direct control over who may use @team and @channel mentions within a specific Team. These settings allow administrators or Team owners to specify whether only owners or all members may use broad notification tags. This is the precise configuration that limits the mention capabilities as described and affects only the Teams where the settings are applied.

Messaging policies control chat and messaging behaviors across the tenant, such as private chat permissions, thread deletion, and read receipts. They do not provide granular control over in-Team mention rights. While messaging policies regulate text-based communication, they cannot restrict @team or @channel mentions because those are governed at the Team level.

App setup policies specify which apps appear in the Teams interface. They organize pinned apps and determine what users see by default, but they do not have any relevance to mentions or notification behavior. As such, changing app setup policies does nothing to address the requirement concerning mention permissions.

Meeting policies regulate behaviors within Teams meetings, such as screen sharing, recording, and attendee roles. They do not impact Team-wide messaging or mentions outside of meetings. Since the requirement focuses on mentions within Teams channels, meeting policies are unrelated.

Team-level settings remain the only configuration granting the requested control. By adjusting who may use @team and @channel notifications, administrators can reduce notification overload and ensure that only authorized individuals broadcast messages to everyone.

Question 89:

A company needs to prevent users from installing third-party apps in Microsoft Teams but still allow Microsoft apps. What should the administrator configure?

A) App permission policies
B) App setup policies
C) Conditional access policies
D) Teams update policies

Answer: A)

Explanation: 

App permission policies regulate which applications users can install or use. They allow administrators to block or allow entire app categories, including third-party apps, Microsoft apps, and custom apps. By configuring an app permission policy that allows only Microsoft apps while blocking third-party ones, the exact requirement is met. This configuration provides granular, targeted control over application access.

App setup policies determine which apps are pinned or visible by default in the Teams client. They do not control whether a user can install third-party apps. Even if apps are not pinned, users can still install and use them unless blocked by a permission policy. Thus, setup policies cannot enforce the restriction described.

Conditional access policies govern authentication and access control across Microsoft apps and services. They operate at a security level focused on access rather than app installation behavior. These policies do not manage whether a user can install an app inside Teams, so they have no bearing on blocking third-party applications specifically.

Teams update policies control the rollout of feature updates to the Teams client. They do not impact which apps are installable. Since the requirement does not involve feature availability or update timing, update policies are unrelated to the scenario.

App permission policies remain the only method that precisely meets the requirement, ensuring users can install Microsoft apps while restricting all third-party apps.

Question 90:

A school district wants to ensure that students cannot start unsupervised meetings in Microsoft Teams. Which setting should be configured?

A) Disable “Meet now” in Teams meeting policies
B) Remove Teams Calendar app from students
C) Disable channel meetings
D) Allow only external participants to start meetings

Answer: A)

Explanation: 

Meeting policies contain a setting that controls whether users can use the “Meet now” feature. Disabling this feature prevents students from starting ad-hoc, unsupervised meetings. This aligns exactly with the requirement: preventing spontaneous meetings unless supervised or scheduled by authorized staff.

Removing the Teams Calendar app would block scheduled meetings but does not disable instant meetings launched through chats or channels. Students might still find alternate methods to initiate meetings unless meeting policy controls are used. Removing the calendar is overly restrictive and does not fully prevent unsupervised meeting creation.

Disabling channel meetings prevents users from starting meetings tied to specific channels but does not prevent ad-hoc meetings in private chats or group chats. This only solves a subset of the problem and does not fully restrict meeting initiation across all methods.

Allowing only external participants to start meetings does not align with Teams meeting architecture. External users cannot be granted exclusive meeting initiation privileges, nor does this address internal misuse by students. It is not a meaningful or valid configuration for restricting meeting creation.

Meeting policies provide the exact control needed. Disabling “Meet now” ensures students cannot launch spontaneous meetings, effectively fulfilling the requirement.

Question 91: 

A company needs to ensure that only specified users can schedule channel meetings in Teams. Which configuration should be updated?

A) Channel moderation settings
B) Teams meeting policy
C) Messaging policy
D) App permission policy

Answer: B)

Explanation: 

The Teams meeting policy determines which users can schedule channel meetings by providing the necessary permissions around scheduling behaviors. Adjusting this policy enables administrators to restrict or allow meeting scheduling capabilities for specific groups. When this policy is correctly assigned, only intended individuals gain access to the scheduling tools, creating a controlled environment over who can generate channel-based meetings. This directly meets requirements for targeted availability.

Channel moderation settings address the permissions related to posting, replying, and publishing within the channel’s conversation area. These settings allow channel moderators to control who can create new posts or initiate discussions, but they do not manage the meeting creation capabilities connected to Teams channels. Since meeting scheduling is not governed through moderation tools, altering moderation settings would not achieve the intended outcome.

Messaging policy controls user-level chat experiences such as private chat, GIFs, stickers, file uploads, and other chat-centric communication actions. These features affect user interactions within chat threads, both private and group-based. Although highly customizable, messaging configurations provide no mechanism to restrict or grant the ability to schedule channel meetings. Messaging policy focuses entirely on communication preferences rather than scheduling abilities.

App permission policies control which applications users can install or interact with, specifying whether third-party apps, Microsoft apps, or custom apps are permitted. However, this does not govern meeting scheduling behavior or channel-level functionality. Even removing the calendar app entirely would disable all meeting scheduling, not selectively control channel meetings. Therefore, modifying app permissions does not provide the targeted control required.

Evaluating all four configurations shows that only the Teams meeting policy contains the required administrative controls that regulate who may schedule channel meetings. Adjusting this policy precisely aligns with the described organizational need, making it the correct solution.

Question 92: 

Your call center requires certain supervisors to monitor active Teams calls in real time. What should you configure?

A) Teams call queue
B) Teams supervisor monitoring policy
C) Compliance call recording
D) Teams voice routing policy

Answer: B)

Explanation: 

Supervisor monitoring policies enable supervisors to listen to live calls in Teams. This configuration is designed specifically to support call center or help desk environments where real-time oversight is necessary. With this feature, supervisors can silently join ongoing calls without interrupting active conversations, ensuring quality assurance, training, and compliance capabilities. This aligns directly with the described scenario.

Call queues distribute incoming calls to available agents. These tools help manage high-volume call environments, automate distribution, and ensure calls reach the correct personnel. While call queues assist with overall call center flow, they do not provide any functionality for supervisors to monitor calls. Their purpose is routing, not monitoring.

Compliance call recording ensures that calls and meetings are recorded for compliance, legal holds, or industry regulations. This involves controlled recording initiated by the system rather than humans. Although useful for reviewing past interactions, compliance recording does not enable supervisors to monitor live calls as they occur. It is strictly post-interaction content.

Voice routing policies determine how outbound calls are handled by the Teams telephony system. These policies direct calls to specific PSTN trunks or SBCs and support global voice architecture. They do not control supervisory features and provide no mechanism for live monitoring.

Based on this evaluation, only the supervisor monitoring policy delivers the functionality required for supervisors to listen to active Teams calls in real time.

Question 93: 

Your organization wants to allow PSTN callers to reach a department without assigning individual phone numbers to each agent. Which feature should you configure?

A) Auto attendant
B) Call queue
C) Shared voicemail
D) Teams channel

Answer: B)

Explanation: 

A call queue provides the ability to route PSTN callers to a group of agents without requiring each agent to have an individual phone number. Incoming callers dial a single number or are transferred through an auto attendant, and the queue distributes calls according to configured routing rules. This meets the exact scenario of handling department-wide calls through one contact point.

Auto attendants provide routing menus and automated navigation options. While they can direct callers toward departments, they do not handle the distribution of calls to multiple agents. Instead, they pass callers to a queue or a specific destination. On their own, auto attendants are not sufficient to manage simultaneous calls for a department without additional components.

Shared voicemail offers a centralized voicemail box for groups but does not provide live call routing or agent distribution. It captures missed calls instead of directing them to available representatives, making it irrelevant to active PSTN call handling.

Teams channels facilitate collaboration, chat, file sharing, and team communication. Channels have no telephony features and cannot route or distribute PSTN calls to users. They serve collaborative purposes rather than call-handling functions.

Therefore, the call queue provides the required capability of enabling PSTN callers to reach a department using one number while distributing calls efficiently among designated agents.

Question 94: 

A company wants to ensure that all external meeting participants cannot annotate shared screens during Teams meetings. What should you configure?

A) Teams meeting policy
B) External access policy
C) SharePoint sharing settings
D) Messaging policy

Answer: A)

Explanation: 

Screen annotation permissions are controlled within Teams meeting policies. These policies allow administrators to regulate whether participants outside the organization can annotate or interact with shared content. By updating the meeting policy, administrators can disable annotation capabilities for external participants while leaving internal permissions unchanged. This addresses the scenario directly and gives precise administrative control.

External access policy determines whether users from other domains can communicate with the organization via chat or calls. While important for federated communication, external access settings have no impact on annotation permissions during meetings. These policies regulate user-to-user communication but do not govern in-meeting collaboration features.

SharePoint sharing settings control access to files stored in SharePoint or OneDrive. Although related to external collaboration in a general sense, they do not affect real-time meeting features such as screen annotation. These are content-level access settings rather than live meeting behavior controls.

Messaging policies determine what users can do within chats, including sending messages, GIFs, stickers, and files. These settings operate within chat spaces and do not modify meeting-specific behaviors. Messaging settings cannot restrict annotation capabilities.

Therefore, modifying the Teams meeting policy is the correct administrative step to disable annotations for external participants.

Question 95: 

An organization wants to automatically block meeting chat for any meeting with more than 200 participants. Which configuration should be updated?

A) Meeting policy
B) Live event policy
C) Teams device policy
D) App setup policy

Answer: A)

Explanation: 

Meeting policies allow administrators to control chat behavior within meetings, including turning chat on, off, or moderated. Policies can be applied to specific groups, enabling differentiated behavior based on user role or meeting type. These settings directly control whether meeting participants may send messages and can be configured to address environments where large meetings require strict communication control. Adjusting this policy is the appropriate way to enforce chat restrictions for large meetings.

Live event policies apply only to Teams live events, which differ from standard meetings. Live events function like broadcast environments, with presenters and producers rather than typical meeting participants. These policies do not influence chat behavior in large Teams meetings. Even though live events often include large audiences, they employ a different feature set, making live event policies irrelevant to the requirement.

Teams device policies configure settings for Teams-certified hardware devices such as Teams displays or Teams Phones. These policies do not influence meeting chat behaviors and serve a completely different administrative purpose.

App setup policies control what apps are pinned or available within the Teams interface. While useful for customizing user experiences, these settings do not impact whether meeting chat is available during a meeting.

Thus, updating the meeting policy is the only configuration that addresses the requirement of blocking chat for meetings exceeding 200 participants.

Question 96: 

A Teams administrator must ensure that only executives can schedule Teams live events, while all other users can schedule regular Teams meetings but not live events. What should be configured?

A) Assign executives a custom meeting policy enabling live events
B) Change the Teams update policy for all other users
C) Adjust Teams device policies for standard users
D) Block live events through compliance retention settings

Answer: A)

Explanation: 

The first configuration grants a specific group the ability to schedule events that require additional broadcast capabilities. By applying a meeting policy created specifically for executives while restricting the same feature in the default policy, an administrator can precisely allow live event scheduling for one group and not for others. This method aligns with granular control of meeting-related features and is the only approach that targets scheduling rights without altering other Teams behaviors.

The second configuration relates to controlling how client features are released to users. Although it modifies how quickly Teams users receive updates, it does not govern feature permissions for live event scheduling. Changing update channels influences user interface rollout and experimental features, not administrative permissions to host advanced meeting formats. Therefore, applying this setting would not accomplish the goal of restricting or allowing live event creation.

The third configuration controls settings on Teams-certified hardware, including displays, panels, and shared devices. These policies manage device behaviors, kiosk setups, and interactions but bear no relevance to user permissions for creating advanced broadcast sessions. Applying device-level restrictions cannot regulate meeting scheduling capabilities for users.

The fourth configuration pertains to data retention and content lifecycle management. These tools ensure compliance, retention, and removal of content but do not offer settings that enable or disable features such as live events. Restricting live events through compliance systems is not possible because retention settings operate after content is generated rather than controlling what users can create.

Through comparison, the correct action is assigning a unique meeting policy to executives that explicitly enables Teams live events. Adjusting policies at this level gives the organization full control, allowing privileged staff to schedule broadcast-style sessions while preventing regular users from doing so. This approach maintains standard meeting functionality for everyone but preserves advanced capabilities for those who require them.

Question 97: 

A company wants external users to join Teams meetings but must prevent them from accessing chat. What should the administrator modify?

A) Teams meeting policy disabling external meeting chat
B) External access domain restrictions
C) Messaging policy that blocks private chat for internal users
D) SharePoint external sharing controls

Answer: A)

Explanation: 

The first configuration directly controls in-meeting behavioral permissions for external participants. By disabling meeting chat for people outside the organization through a policy, administrative staff ensure guests can join meetings but cannot read or send messages. This satisfies the requirement while still preserving meeting participation, screen viewing, and audio and video capabilities for external attendees.

The second configuration affects whether communication between domains is allowed. Blocking or restricting external access domains either allows or denies calls and chats with external organizations completely. However, external access does not granularly control specific meeting features such as restricting chat while still permitting meeting attendance. These settings govern entire communication channels, not meeting feature behavior.

The third configuration affects the internal communication environment. These settings determine whether individuals within the organization can message each other privately. These restrictions do not control guest or external user behavior during meetings. Internal messaging policies cannot remove chat visibility from external users inside a real-time meeting.

The fourth configuration handles external file-sharing permissions for content stored within collaboration sites. While important for document governance, SharePoint settings do not influence how chat behaves in meetings. Meeting chat resides within Teams conversation spaces, not SharePoint content repositories.

Since only meeting policies contain controls for chat behavior targeted at external participants, adjusting this setting meets the requirement precisely. This prevents external attendees from participating in meeting chat channels while maintaining full access to the meeting itself.

Question 98: 

A Teams admin needs to ensure that PSTN callers hear a custom welcome message before being routed to a call queue. What should be configured first?

A) Auto attendant with an audio greeting
B) Direct routing SBC configuration
C) Caller ID policies
D) Teams dial plan normalization rules

Answer: A)

Explanation: 

The first configuration represents the foundational component responsible for shaping how callers experience the system before their calls enter any operational workflow. An auto attendant is designed specifically to handle greetings, menus, prompts, and routing logic. When a Teams administrator wants PSTN callers to hear a custom welcome message, the system requires an entry point capable of playing audio immediately when a call is received. Only an auto attendant provides this ability because it allows administrators to upload or record an audio greeting, define call-handling rules, and route callers to call queues after the greeting completes. This ensures that every inbound caller receives a uniform, professional, and branded experience before reaching any queue or agent. Auto attendants also support configurable behaviors such as business hours, holiday schedules, interactive keypress menus, and fallback options, all of which prepare the call flow prior to reaching the queue.

The second configuration relates to Direct Routing, which concerns the integration of a Session Border Controller (SBC) to facilitate PSTN connectivity through third-party carriers. While Direct Routing is essential for enabling Teams phone capabilities when using external telephony providers, it does not create or manage audio prompts for inbound callers. SBC configurations ensure signaling, security, and routing between on-premises telephony and Teams, but they do not offer mechanisms for greeting playback, call menus, or automated flow logic. Thus, although important for voice infrastructure, it does not provide the greeting functionality required for this scenario.

The third configuration deals with controlling how outbound caller identification appears when users place calls. Caller ID policies determine what number is displayed to call recipients but have no role in receiving or processing PSTN calls. Since the question involves playing a message before routing, caller ID policy does not intersect with any audio or call-flow requirement for inbound calls.

The fourth configuration focuses on dialing behavior within Teams by ensuring that numbers entered by users are formatted correctly for routing. Dial plan normalization applies to outbound dialing only and does not influence how incoming calls are processed. It plays no part in introducing audio greetings or managing caller experiences.

Considering these elements, the only configuration that enables the playback of a custom welcome message before callers reach a call queue is the auto attendant. It provides the necessary greeting, structure, and call flow control, making it the correct and required starting point.

Question 99: 

A company needs to ensure recordings of Teams channel meetings are stored and accessible only within the associated team. What setting is required?

A) Channel meeting storage behavior in SharePoint
B) OneDrive sharing restrictions
C) Teams update policies
D) Messaging policies for file attachments

Answer: A)

Explanation: 

The first configuration is essential because Teams channel meetings follow a structured and predetermined method of storing their recordings. By design, any meeting scheduled within a channel automatically stores its recording in the team’s associated SharePoint document library under the “Recordings” folder. This ensures the recordings inherit the team’s existing permissions model, meaning only members of that team can access the stored content. Reviewing or modifying the channel’s SharePoint storage behavior guarantees that these recording files remain securely confined to the team environment and are not inadvertently stored in unrelated locations. This preserves governance, supports compliance, and avoids additional administrative effort such as manually adjusting sharing permissions or relocating files after meetings conclude.

The second configuration deals with OneDrive sharing restrictions, which apply primarily to personal meeting recordings—those generated from meetings scheduled outside a channel. OneDrive controls are irrelevant to channel meeting storage because channel meetings never store recordings in personal OneDrive accounts. Their storage location is determined exclusively by the team’s SharePoint structure. As a result, adjusting OneDrive settings would have no impact on ensuring that channel meeting recordings remain accessible only within the associated team.

The third configuration, Teams update policies, governs feature rollout behavior, such as whether users receive early access to preview features. These policies affect interface elements, client capabilities, and release timing but have no influence on file storage locations, meeting recording storage rules, or the permission structures applied to channel recordings. Because update policies do not control content governance, they cannot ensure that recordings remain accessible strictly within the team.

The fourth configuration relates to messaging controls that determine how users interact with attachments and shared content within chats. Messaging policies influence capabilities like deleting messages or uploading attachments but have no relation to how recording files are stored, protected, or permissioned. They do not define the repository for recordings nor regulate access to those files at the team level.

By validating and ensuring proper use of the SharePoint-based storage mechanism tied to channel governance, administrators can guarantee that recordings remain secure and accessible only to authorized team members. Therefore, managing channel meeting storage behavior in SharePoint is the required setting to meet the organization’s objective.

Question 100: 

An organization wants to ensure that Teams users can join meetings from unmanaged devices but cannot download shared files. What must be configured?

A) Conditional Access with session controls
B) Guest access settings
C) App setup policy
D) Teams calling policy

Answer: A)

Explanation: 

The first configuration is the only mechanism that enables administrators to enforce precise controls on how users interact with Teams resources when accessing from devices that are not managed, compliant, or trusted. Conditional Access rules—paired with session controls—allow the organization to restrict the ability to download files, copy content, or synchronize data while still permitting users to join meetings via the browser. By applying Conditional Access with Conditional Access App Control or limited session-level restrictions, an organization can create an environment where the user can participate in collaboration but cannot remove or download sensitive data. This ensures continued productivity for remote or ad-hoc access while maintaining strong protection for the organization’s information.

The second configuration concerns guest access, which determines whether external users can participate in team collaboration. This setting affects onboarding, permissions, and interaction for guests but cannot restrict file download behavior for internal users on unmanaged devices. Guest access also does not differentiate between compliant and noncompliant devices for conditional security purposes. Therefore, it cannot fulfill the requirement of blocking file downloads for internal users while still allowing meeting access.

The third configuration controls the layout, visibility, and pinning of applications in the Teams client experience. App setup policies influence user interface convenience rather than security, access control, or device-based restrictions. Even if certain apps are hidden or rearranged, users on unmanaged devices would still be able to download files unless a proper identity-driven control like Conditional Access is applied.

The fourth configuration, Teams calling policies, manages telephony features such as call forwarding, call groups, voicemail, and PSTN capabilities. These policies address calling functionality and do not extend into content protection, file handling rules, or device-condition evaluation. Calling behavior is separate from file governance requirements.

To meet the requirement—permitting access to meetings but preventing file downloads—the organization must enforce identity-based security through Conditional Access with session controls. This is the only approach capable of restricting download activity based on device compliance state while maintaining meeting participation.