Microsoft MS-700 Microsoft 365 Certified: Teams Administrator Associate Exam Dumps and Practice Test Questions Set 7 Q121-140

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

Question 121: 

Which Teams policy determines whether users can send GIFs, stickers, and memes?

A) Messaging policy
B) App setup policy
C) Meeting policy
D) Live events policy

Answer: A)

Explanation: 

A messaging policy governs the wide range of chat-related capabilities available to users within the Teams client, including expressive content such as GIFs, stickers, emojis, memes, and similar communication elements. When administrators need to regulate how users interact in chats, especially in organizations where visual or playful content needs to be controlled for professionalism, compliance, or bandwidth optimization, this policy becomes the primary configuration point. It directly determines whether such expressive content is allowed or restricted, making it the accurate solution for managing GIF availability.

An app setup policy focuses on which applications appear in the Teams interface, particularly those pinned or allowed for specific groups. This setting is unrelated to controlling the features within chats. While it influences app visibility, it has no effect on whether users can send expressive content. Administrators use such policies mainly for app deployment rather than chat governance.

A meeting policy shapes user experiences during meetings, including aspects such as screen sharing, recording permissions, participant roles, lobby behavior, and meeting chat availability. However, these configurations do not regulate GIFs or stickers in normal chats. Meeting policies apply specifically to meeting environments rather than general chat behavior.

A live events policy manages configurations for broadcast-scale events, including attendee engagement, scheduling allowances, recording availability, and producer permissions. These settings apply only to live events and have no control over messaging-level expressive content. Because live events are structured broadcasts, they do not intersect with everyday chat tools like GIFs or stickers.

Since the goal is to control expressive content within standard chat interactions, the messaging policy is the only policy category designed to influence that capability. Therefore, the messaging policy correctly manages GIF, sticker, and meme permissions.

Question 122: 

A manager wants to pin a specific app for a subset of users. What should be configured?

A) App setup policy
B) Teams update policy
C) Compliance policy
D) Network planner

Answer: A)

Explanation: 

An app setup policy provides administrators with direct control over which applications appear pinned in the Teams client for selected groups or individuals. When an organization wants to ensure consistent app visibility—such as automatically pinning a project management app, workflow tool, productivity extension, or industry-specific solution—this policy determines the order, presence, and availability of those apps. Because pinning affects user interfaces and productivity workflows, app setup policies are the correct choice when a subset of users needs a tailored app arrangement.

A Teams update policy controls how quickly Teams client updates become available to different user groups. It allows administrators to place users in the targeted, production, or preview update rings. While important for feature rollout, this type of policy does not influence which apps appear pinned in the Teams app bar. It deals with client updates rather than application availability or placement.

A compliance policy governs retention, data loss prevention, auditing, governance, and other compliance-related requirements. These policies ensure that organizational data is protected and stored according to legal or regulatory standards. They do not manage visual arrangement or app placement in the interface. Compliance policies operate at a data-governance level, not at a user interface configuration level.

A network planner is a technical tool used to evaluate bandwidth requirements for Teams workloads such as voice, video, and meetings. It helps organizations design network readiness for deployment but has no impact on the Teams client interface or app pinning.

Because the requirement is specifically to pin an app for selected users, the app setup policy directly meets this need by allowing administrators to configure how apps appear.

Question 123: 

Which feature controls whether anonymous users can join Teams meetings?

A) Meeting policy
B) App permission policy
C) Messaging policy
D) Teams Rooms policy

Answer: A)

Explanation: 

A meeting policy manages a wide range of meeting-related behaviors and permissions, including whether anonymous users may join meetings. This control is significant because organizations often need to decide whether external participants without authentication should be granted access to meetings for training sessions, public events, support interactions, or open forums. By adjusting this policy, administrators can explicitly allow or block anonymous join, ensuring security and compliance with internal meeting access standards. This makes a meeting policy the correct configuration for the requirement.

An app permission policy regulates whether users can access Microsoft-provided, third-party, or custom applications within Teams. It allows administrators to block or allow categories of apps, restrict particular publisher apps, or control app availability based on security considerations. This policy does not manage meeting access rights and has no ability to control anonymous participation. It addresses app governance rather than meeting attendance.

A messaging policy determines permissions related to chats, such as deleting messages, sending GIFs, using memes, or editing sent content. Although messaging is frequently related to collaboration, it is unrelated to the admission of anonymous participants in meetings. Messaging governance affects chat interactions rather than meeting access pathways.

A Teams Rooms policy applies to certified Teams meeting room devices, governing their sign-in behavior, meeting experiences, and device-specific configurations. These policies influence how room systems participate in and manage meetings but do not control whether anonymous participants may join.

The ability to allow or block anonymous join is exclusively managed by the meeting policy, making it the correct answer.

Question 124: 

A department needs a shared voicemail for incoming calls. Which feature should be used?

A) Call queue
B) Auto attendant
C) Caller ID policy
D) External access

Answer: A)

Explanation: 

A call queue enables organizations to route incoming calls to a group of agents, provide an organized distribution method, and offer shared voicemail functionality for departments or functional teams. When incoming calls need to reach multiple people who may not always be available, call queues supply mechanisms such as round robin routing, serial distribution, and simultaneous ringing. When no agents are available to answer, shared voicemail ensures that recorded messages are stored in a central location accessible to the group, fulfilling the need for departmental coverage and message management.

An auto attendant provides menu navigation, allowing callers to interact with a structured voice menu using either keypad inputs or speech recognition. Although auto attendants facilitate routing, their primary function is not to serve as shared voicemail endpoints. They can send callers to voicemail boxes, but the shared voicemail capability, designed for groups of agents, is implemented through call queues rather than auto attendants. Auto attendants focus on interactive call flow rather than voicemail distribution.

A caller ID policy manages how outbound caller identity is presented, such as masking a user’s number or substituting a service number. While useful for branding, privacy, or call routing purposes, it has no role in creating shared voicemail or handling group call behavior. Caller ID configurations strictly influence outbound caller identity.

External access allows federated communications with outside domains, enabling chat and calling between organizations. This feature is unrelated to call routing, voicemail availability, or internal call distribution. It governs communication boundaries rather than voicemail functionality.

Because the requirement centers on enabling multiple users to access shared voicemail for department-level inbound calls, call queues are the only feature specifically designed to support this capability.

Question 125: 

Which Teams admin control restricts who can create private channels?

A) Teams policy
B) Messaging policy
C) Meeting policy
D) Device policy

Answer: A)

Explanation: 

A Teams policy manages permissions related to Teams and channel-level capabilities, including the ability to create private channels. Organizations often need to limit private channel creation to ensure governance, proper data segregation, compliance, and security. This policy allows administrators to specify which users can create such channels, helping maintain control over information access and ensuring private channels are used only when appropriate. Because the question requires controlling channel creation capabilities, a Teams policy is the correct configuration.

A messaging policy regulates chat behaviors such as editing messages, deleting content, sending rich media, or enabling chat transcripts. Although chat and channels both involve communication, messaging policies do not control channel creation or structural governance. Their scope is chat-centric rather than team or channel-centric.

A meeting policy defines settings related to meeting participation, recording, screen sharing, and other meeting features. It does not manage channel structure or authorization to create channels. These policies influence meeting environments rather than workspace architecture.

A device policy governs Teams-certified devices, configuring aspects such as sign-in behavior, device settings, and meeting profile preferences. Device policies are unrelated to channel permissions and are exclusively focused on hardware functionality.

The ability to create private channels is specifically governed by Teams policies, making them the correct solution.

Question 126: 

An organization wants external users to chat with employees but not join meetings. What should be configured?

A) Allow external access but disable guest access
B) Disable external access and enable guest access
C) Disable federation
D) Disable chat in messaging policies

Answer: A)

Explanation:

Allowing external access while disabling guest access provides a very specific balance between communication openness and meeting security. External access enables federated chat, meaning users in other domains can send and receive messages with internal employees without being added as guests. This satisfies the need for cross-organization communication while still maintaining a lightweight interaction model. Because external access does not inherently grant meeting participation privileges unless the meeting organizer permits it, allowing it while simultaneously blocking guest access ensures that external individuals can chat but cannot join internal meetings as authenticated participants. Guest access, on the other hand, provides deeper collaboration capabilities—including access to channels, files, and meeting participation—so disabling it ensures external users cannot join meetings.

Disabling external access while enabling guest access would restrict the ability for outside users to initiate chat through federation. Guest access is intended for more formal collaboration scenarios where the external user must be added into a team, given extended resource permissions, and actively participate in activities including meetings. This goes against the requirement, because enabling guest access would allow meeting participation rather than prevent it.

Disabling federation blocks all external chat interactions entirely. While this setting enhances security for organizations that must isolate communication boundaries, it eliminates the capability that the scenario requires—external users must be able to chat. Therefore, such a restriction is incompatible with the desired outcome.

Disabling chat via messaging policies is an internal restriction that affects both internal and external communication. Applying such a policy would remove chat capabilities altogether, making it impossible for employees to exchange messages with external participants. This is far beyond the required limitation and negatively impacts productivity.

Combining external access with guest access disabled ensures chat remains available while preventing meeting participation.

Question 127: 

Which setting allows meeting organizers to control who can bypass the lobby?

A) Meeting policy
B) Messaging policy
C) Update policy
D) App setup policy

Answer: A)

Explanation: 

A meeting policy controls an array of settings that determine how meetings behave, including the configuration that dictates who may bypass the lobby. The lobby serves as a virtual waiting area, and many organizations rely on this feature for security, privacy, or workflow needs. Meeting policies allow administrators to specify whether internal users, external authenticated users, or specific groups can enter meetings directly without waiting for approval. These settings help ensure meetings remain secure while still providing flexibility in how organizers admit participants. Since the requirement involves controlling lobby bypass behavior, meeting policies are the correct tool.

A messaging policy manages chat-related functionalities such as message editing, deletion, rich content usage, and other similar features. Messaging policies do not influence meeting access, waiting room conditions, or participant admission. While essential for organizing communication standards, they do not impact lobby behavior in any way and therefore cannot meet the requirement.

An update policy regulates how Teams client updates and preview features are rolled out to users. These policies help organizations manage version control and ensure stability or early access to new features but do not alter meeting configurations. Update policies are strictly related to update cadence, not meeting access rules.

An app setup policy manages which apps are pinned or visible in the Teams interface. While helpful for customizing user experiences and ensuring important apps appear prominently, these policies have no impact on meeting structure or participant security controls. App setup relates purely to interface customization, not meeting governance.

Meeting policies alone contain the necessary settings for lobby bypass behavior.

Question 128: 

To ensure Teams devices stay current with firmware, what should be configured?

A) Teams device update policy
B) Meeting policy
C) Caller ID policy
D) External access

Answer: A)

Explanation: 

A Teams device update policy governs the firmware update process for Teams-certified devices such as Teams phones, Teams displays, and Teams panels. These policies ensure that devices stay aligned with the latest security updates, stability improvements, and feature enhancements. Administrators can configure automatic updates, defer updates, or set update schedules to maintain consistency across their device fleet. This type of policy is designed specifically to manage firmware versions and ensure devices operate reliably. With device stability being critical for communication environments, managing firmware through device update policies is the correct approach.

A meeting policy covers features such as recording availability, screen sharing, breakout rooms, participant controls, and lobby bypass options. These settings affect meeting behavior rather than physical device firmware. While meeting policies significantly shape user experiences during meetings, they offer no mechanism for managing firmware updates or device maintenance.

A caller ID policy is focused on managing how outbound caller identity is displayed. It can apply service numbers, mask personal numbers, or reflect team-based identities. This policy impacts outbound calling appearance but cannot modify device firmware or update schedules. Caller identity presentation and device firmware management are unrelated domains.

External access governs communication with users in other organizations. It controls whether federation is allowed, whether communication can occur across domains, and how external chat or calling behaves. This setting is unrelated to device management and does not provide any tools for controlling firmware or updates.

Because firmware management pertains specifically to device update processes, Teams device update policies are the correct configuration choice.

Question 129: 

Which tool helps estimate bandwidth requirements for a location with 500 Teams users?

A) Network planner
B) Call queue
C) Auto attendant
D) Live events policy

Answer: A)

Explanation: 

The network planner tool provides organizations with the ability to model bandwidth requirements based on usage scenarios, user counts, workload types, and building layouts. This tool is particularly useful during planning or deployment phases where administrators need to predict how Teams workloads—including voice, video, meetings, and signaling traffic—will perform within the existing network infrastructure. For a location with 500 users, the network planner calculates estimated capacity needs and helps ensure sufficient resources are available to maintain performance. It also highlights areas where adjustments may be necessary, such as upgrading routers, increasing available bandwidth, or optimizing Wi-Fi coverage.

Call queues are designed for distributing inbound calls to groups of agents. They manage routing patterns, shared voicemail, and caller wait experiences. While useful for communication management, call queues have no capability to estimate bandwidth consumption or analyze infrastructure capacity. Their function is operational rather than analytical.

Auto attendants provide interactive menus for callers, supporting features such as speech recognition, routing based on caller input, and call redirection. These are voice workflow tools—not network analysis tools—and therefore do not contribute to bandwidth planning or network assessment.

A live events policy manages configurations for large broadcast-style meetings, determining whether users can schedule events, the types of recording allowed, and participant settings. Although live events may generate notable traffic during usage, the policy itself does not calculate bandwidth needs or evaluate network readiness.

Only the network planner provides explicit bandwidth estimation functionality, making it the correct answer.

Question 130: 

Which Microsoft Teams feature allows callers to route to departments based on voice commands?

A) Auto attendant
B) Call queue
C) Voice routing policy
D) Caller ID policy

Answer: A)

Explanation: 

An auto attendant supports intelligent call routing using speech recognition, allowing callers to speak department names, phrases, or keywords in order to reach the appropriate destination. This feature enables organizations to streamline inbound call flows by removing the need for menu navigation through keypad inputs. Callers can simply say “sales,” “technical support,” or another department name, and the auto attendant’s voice recognition engine interprets the request and routes the call accordingly. Auto attendants offer flexible configurations, including multi-level menus, time-based routing, business hours settings, and integration with call queues when agent-based routing is necessary. Because the requirement centers on routing triggered by spoken commands, the auto attendant is the correct solution.

A call queue manages distribution of calls to available agents but does not interpret voice commands. Call queues are designed for structured inbound call handling once a caller has already been routed, typically by an auto attendant. They provide shared voicemail, agent routing, and queue management, but not speech-based routing.

A voice routing policy governs outbound PSTN call routing patterns, determining which trunk or path a call should follow. These policies support direct routing scenarios and ensure outbound calls follow defined routes. They do not provide interactive voice capabilities or caller-driven routing experiences.

A caller ID policy manages how users’ outbound identity is presented, controlling whether a personal or service number appears to recipients. This functionality is unrelated to routing workflows or voice command recognition.

Because auto attendants are the only feature with built-in speech recognition for routing, they correctly meet the requirement.

Question 131: 

A Teams administrator needs to prevent users from installing third-party apps in Teams. What should be configured?

A) App permission policy
B) App setup policy
C) Teams update policy
D) Teams meeting policy

Answer: A)

Explanation: 

An app permission policy is the correct configuration when an administrator needs to prevent users from installing third-party applications in Microsoft Teams. These policies determine which categories of apps—Microsoft apps, third-party apps, tenant apps, or custom line-of-business apps—users are allowed to install. By modifying the policy to block third-party apps, administrators can maintain compliance, reduce security risks, and ensure the environment is restricted to approved tools only. App permission policies also allow administrators to grant or deny access at a granular level based on user groups, enabling selective restrictions depending on the organization’s structure. This aligns directly with the requirement of preventing installation of third-party apps while still allowing internal or Microsoft-provided apps where appropriate.

An app setup policy, on the other hand, affects which apps appear pinned or the order in which they display in the Teams interface. Although it influences user interface layouts, it does not block or allow app installation. This policy only affects visibility and pinning, not permissions. Changing this policy does not meet the requirement of preventing third-party app installation.

A Teams update policy determines how quickly new Teams features and preview functionalities are delivered to users. These policies allow administrators to assign update channels but do not grant or deny app installation rights. Adjusting update policies has no effect on third-party app access and would not help achieve the stated restriction.

A Teams meeting policy governs meeting behavior, covering capabilities such as recording, screen sharing, transcription availability, meeting chat, and participant roles. While essential for meeting governance, such a policy has no control over app installation permissions. It focuses solely on meeting environments, not the broader Teams app ecosystem.

Because only app permission policies directly regulate whether third-party applications can be installed or used, modifying these policies is the correct and effective approach.

Question 132: 

You need to restrict who can create new Teams in the organization. Which feature should be configured?

A) Azure AD group creation permissions
B) App setup policy
C) Teams device policy
D) Live events policy

Answer: A)

Explanation: 

Azure AD group creation permissions are the correct method for controlling who can create new Teams. Every Microsoft Team is backed by a Microsoft 365 Group, meaning that the ability to create Teams is directly tied to the permissions that govern group creation. By restricting group creation to specific security groups, administrators ensure that only designated users can create Teams, reducing sprawl, improving governance, and ensuring that only properly managed Teams are introduced into the environment. This approach is often used in large organizations to maintain order and prevent unnecessary resource creation.

An app setup policy configures how apps appear in Teams, such as which applications are pinned or the sequence in which they appear. It does not manage permissions for creating Teams or Microsoft 365 Groups. Adjusting app setup policies will not enforce restrictions on team creation.

A Teams device policy applies to Teams-certified hardware such as phones and displays. These policies dictate device-level behavior, including configuration settings and sign-in properties. They do not influence which users can create Teams or manage group creation rights. Therefore, device policies are unrelated to the requirement.

A live events policy governs permissions around scheduling and producing Teams live events. While necessary for managing broadcast capabilities, this policy only affects event production workflows. It does not impact the structural governance of team creation.

Because restricting who creates Teams requires controlling Microsoft 365 Group creation, Azure AD group creation permissions are the correct and only effective solution.

Question 133: 

A company wants specific users to have early access to Teams preview features. What should be adjusted?

A) Teams update policy
B) Messaging policy
C) Meeting policy
D) Compliance policy

Answer: A)

Explanation: 

A Teams update policy is the correct configuration when an organization wants certain users to receive preview features before standard release. These policies allow administrators to place users in different update channels, including “Preview,” “Targeted,” and “Standard.” Assigning users to the preview channel grants early access to experimental or upcoming features, enabling pilot testing, feedback collection, and compatibility assessment. This targeted rollout is essential for organizations that want to evaluate changes before widespread adoption. Because preview features are controlled exclusively through the update policy, this is the precise configuration that satisfies the requirement.

A messaging policy manages chat-related behaviors such as deleting messages, editing messages, sending GIFs, or allowing memes. These settings do not influence when features are rolled out or who receives early updates. Messaging policies govern communication behaviors, not update channels.

A meeting policy affects meeting-related capabilities including recording, screen sharing, breakout rooms, lobby settings, and participant permissions. Although critical for shaping meeting experiences, such a policy does not control feature rollout timing or preview enrollment. No meeting policy setting grants early access to Teams preview features.

A compliance policy governs retention, data protection, eDiscovery, and DLP capabilities. These are essential for governance and regulatory adherence, but they do not manage software feature updates or preview channel assignments. Compliance tools relate to data management, not client update workflows.

Because only the Teams update policy directly controls preview access, it is the correct solution.

Question 134:

A school wants to ensure students cannot start meetings in class Teams channels. What should be changed?

A) Teams channel meeting policy
B) Teams app permission policy
C) Live events policy
D) Teams device policy

Answer: A)

Explanation: 

A Teams channel meeting policy is the correct configuration to prevent students from starting meetings in class channels. This policy allows administrators to specify who can schedule or initiate channel-based meetings. In educational environments, controlling meeting creation is essential for classroom management, preventing unsupervised sessions, and maintaining structured learning experiences. By adjusting channel meeting permissions, administrators can ensure that only teachers or authorized staff members can launch meetings, while students are restricted to joining scheduled sessions. This aligns directly with the requirement and ensures consistent control in academic settings.

A Teams app permission policy governs which applications users can access within Teams. While it regulates app categories such as third-party or custom apps, it does not provide controls for starting or scheduling channel meetings. Adjusting this policy does nothing to restrict students from initiating meetings.

A live events policy applies to broadcast-style events rather than everyday class meetings. These policies configure who can schedule live events, their recording settings, and attendee permissions. Since the school’s requirement concerns regular channel meetings rather than live broadcast events, this policy is unrelated.

A Teams device policy governs Teams-certified hardware and manages device settings such as meeting join behaviors and display configurations. These policies do not govern whether users can start meetings in a channel. Device configuration and channel meeting permissions serve completely different purposes.

Because preventing students from starting meetings requires controlling channel meeting creation rights, a Teams channel meeting policy is the correct tool.

Question 135: 

Your organization wants to prevent anonymous users from joining Teams meetings. What should you modify?

A) Meeting policy
B) Messaging policy
C) Update policy
D) App setup policy

Answer: A)

Explanation: 

A meeting policy is the correct configuration to prevent anonymous users from joining Teams meetings. These policies contain the specific setting that allows or blocks anonymous join. Organizations commonly restrict anonymous access to ensure only authenticated participants enter meetings, improving security, compliance, and accountability. By adjusting the policy to disable anonymous join, meeting organizers are assured that external participants must authenticate before entering. This prevents unauthorized or unverified users from accessing sensitive discussions or disrupting sessions.

A messaging policy governs behaviors within chat such as message editing, deletion, link previews, GIF usage, and other communication features. Messaging settings do not determine meeting entry permissions and therefore cannot control access for anonymous participants.

An update policy determines how Teams client updates are delivered, including whether users receive preview features. Although important for controlled feature rollouts, update policies do not affect meeting access or authentication requirements.

An app setup policy dictates which applications display in Teams and in what order. It influences layout and app pinning, but not meeting entrance criteria. Changing this policy has no effect on anonymous join settings.

Because only meeting policies govern anonymous meeting access, modifying them is the correct and necessary action.

Question 136: 

You want to ensure specific users can create Teams live events while others cannot. What should you use?

A) Live events policy
B) App setup policy
C) Compliance policy
D) Calling policy

Answer: A)

Explanation: 

Managing which individuals in an organization can create and conduct Teams live events requires a configuration that directly governs access to broadcast-level features. Live events are a specialized capability within Microsoft Teams that allow selected presenters and producers to stream structured, large-scale sessions to broad audiences. Because not every user needs or should have this functionality, the platform provides a dedicated control mechanism to restrict or enable this feature precisely where it is required. The setting that fulfills this requirement is the live events policy, which has controls explicitly designed to determine who is allowed to schedule or produce these broadcast sessions. It lets administrators selectively grant permissions to certain departments, roles, or individuals while ensuring that the general workforce cannot initiate these high-visibility event types. This approach enables organizations to maintain governance over large broadcasts, control technical resource usage, and prevent unintended or unauthorized event scheduling.

App setup policy, by contrast, deals with the placement of apps within the Teams client interface. It determines which applications are automatically pinned to the client and which are made available for easy access. While this can affect user experience and streamline workflows by exposing relevant tools, it does not grant or restrict the ability to create live events. The policy’s scope is limited to app arrangement and availability, meaning it cannot influence a capability as specialized as event production.

Compliance policy focuses on regulatory requirements, retention, content lifecycle, legal hold, and information protection settings. Although such policies play a major role in ensuring proper governance and data management for content generated within Teams, they do not determine who is allowed to produce live events. These controls work behind the scenes to enforce compliance behaviors rather than adjusting user feature privileges.

Calling policy governs calling and voice functionalities, such as forwarding rules, call handling, voicemail, call recording configurations, and outbound or inbound calling restrictions. While these settings are essential for telephony governance, they have no relationship to broadcast events. They focus exclusively on voice features and cannot limit or enable event production capabilities.

Because only the live events policy contains explicit settings that directly define who may schedule, produce, or present large broadcast sessions, it is the correct configuration to use when restricting live event creation to specific users.

Question 137: 

A company wants to restrict external domain communication but still allow it for one department. What should be configured?

A) External access settings
B) Messaging policy
C) Meeting policy
D) App permission policy

Answer: A)

Explanation: 

Controlling which users or departments can communicate with external domains requires a setting that governs federation behavior at the organizational or scoped level. External access settings are designed precisely for this purpose because they regulate whether users can communicate with people in allowed external domains while blocking all others. These controls can be configured to allow only specific trusted domains or to disable external communication except for those that must remain open for business needs. When a company needs to restrict this capability for the general workforce while continuing to permit communication for a single department, the configuration must allow selective application of these controls. External access settings support this by enabling administrators to apply conditional access or routing rules that ensure only approved groups retain access to external domains. This method maintains operational flexibility while enforcing security.

Messaging policy, on the other hand, governs chat-related behaviors inside the tenant. It defines features such as deleting messages, using GIFs or stickers, or initiating private chats. These policies cannot manage communication boundaries across external domains and do not provide any mechanism to selectively permit or block cross-tenant communication.

Meeting policy controls meeting-related capabilities, such as screen sharing, meeting creation restrictions, lobby settings, and recording permissions. While essential for secure meeting governance, these settings do not regulate domain-level communication, nor do they influence external federation behavior.

App permission policy manages which applications users can install or access within Teams. This includes third-party apps, custom line-of-business apps, and Microsoft apps. While critical for reducing app-based risk exposure, it has no relation to controlling communication with external domains and cannot enforce domain restrictions.

Because external access settings directly control cross-tenant federation and domain communication, and provide the selective flexibility needed to support only one department, they are the correct choice.

Question 138: 

You need to give a helpdesk group the ability to view Teams call analytics. What should be assigned?

A) Teams communications support specialist role
B) Teams administrator role
C) Global admin role
D) Security reader role

Answer: A)

Explanation: 

Providing a helpdesk group with the ability to view call analytics and call-quality information requires a role tailored for support teams that need visibility into user call experience without gaining broad administrative privileges. The Teams communications support specialist role is designed precisely for this scenario because it grants access to the Call Analytics dashboard, enabling helpdesk staff to investigate call issues, troubleshoot user-reported problems, and view device, network, and session-level data. This role offers the necessary visibility without permitting high-risk configuration changes, making it ideal for Tier 1 or Tier 2 support teams.

The Teams administrator role grants full administrative control over Microsoft Teams, including the ability to manage policies, configure organization-wide settings, adjust meeting and messaging controls, manage Teams apps, and perform deep management tasks. Assigning this level of access to helpdesk staff would be excessive and increase the risk of unintentional or unauthorized configuration changes. While this role also has access to analytics, it goes far beyond what is needed.

The global admin role provides the highest level of authority in Microsoft 365, granting full control across all services. Giving this to helpdesk personnel would constitute a major security risk, far exceeding the requirements of viewing call analytics. This role should be restricted to only a very small set of trusted personnel due to its comprehensive access.

The security reader role provides access to security-related dashboards, threat intelligence, and compliance insights. It does not grant access to Teams-specific call analytics or workload-specific troubleshooting tools. This role focuses on threat detection and compliance monitoring rather than communication quality analysis.

Because the Teams communications support specialist role provides exactly the needed level of visibility with minimal risk, it is the correct assignment.

Question 139: 

You want all guest users to have restricted chat abilities. What should be configured?

A) Guest messaging policy
B) Teams device policy
C) Live events policy
D) App setup policy

Answer: A)

Explanation: 

Restricting chat abilities for guests requires a control mechanism dedicated to governing how guest accounts behave within Teams environments. A guest messaging policy contains the settings needed to control whether guests can send messages, edit messages, use rich content such as images or memes, or initiate private conversations. Because guest access must remain limited to preserve security and prevent misuse of collaboration spaces, organizations frequently reduce these capabilities for external participants. A guest messaging policy provides precisely targeted configuration to ensure that all guests automatically inherit restricted behavior without impacting internal users. This allows administrators to enforce consistent restrictions across all external participants regardless of department, team, or channel.

Teams device policy controls how Teams behaves on specific certified hardware devices, such as Teams Rooms systems, desk phones, and collaboration panels. While these controls are important for managing device functionality and security, they have no effect on how users—guest or internal—can use chat features. Device policies focus on hardware capabilities, not communication privileges.

Live events policy governs the ability to schedule and produce live broadcast events. These policies decide who can create such events and what tools they can use. They have no connection to chat restrictions for guest users, because live events are a distinct feature set unrelated to guest messaging capabilities.

App setup policy controls the arrangement and availability of apps in the Teams client. It determines what apps appear by default or are pinned for convenience. While it influences the interface experience, it does not enforce communication restrictions and cannot limit chat abilities for guests.

Since only the guest messaging policy allows fine-grained control over guest chat behaviors, it is the correct configuration.

Question 140: 

You need to ensure recordings expire after 60 days for all users. What should be set?

A) Teams meeting recording expiration settings
B) Retention labels
C) App permission policy
D) Teams calling policy

Answer: A)

Explanation: 

When an organization needs to enforce a specific expiration period for Teams meeting recordings, the configuration must directly control the lifecycle of recordings stored in OneDrive and SharePoint. Teams meeting recording expiration settings provide an administrative mechanism that automatically deletes recordings after a set number of days, such as 60, unless extended or overridden by the user within permitted governance limits. This ensures storage is managed efficiently, reduces long-term retention of unnecessary meeting data, and aligns with internal policies that limit how long such recordings should remain accessible. Because the setting applies globally or per-policy, it ensures consistent enforcement across all users.

Retention labels are designed for long-term governance of files, emails, and messages. They support assigning content retention periods, managing deletion timelines, and enforcing compliance regulations. While powerful, retention labels do not control the automatic expiration of Teams recordings based on recording-specific lifecycle settings. They operate at a different level focused on regulatory data governance, not streamlined recording expiration.

App permission policy controls which applications can be installed or used within Teams. These policies are completely unrelated to meeting recording retention and cannot enforce any type of expiration behavior. Their scope is limited to app access and availability.

Teams calling policy manages features related to calling behavior, such as voicemail, call transfer, call forwarding, and outbound calling restrictions. It has no capability to influence meeting recordings, their storage, or their deletion timelines.

Because Teams meeting recording expiration settings are the only tool specifically designed to define recording deletion timeframes, they are the correct choice.