Microsoft MS-700 Microsoft 365 Certified: Teams Administrator Associate Exam Dumps and Practice Test Questions Set 4 Q61-80

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

Question 61: 

Your organization wants to prevent external users from uploading files during Teams meetings. Which configuration should you change?

A) Disable external file sharing in SharePoint admin center
B) Modify guest access settings in Microsoft 365 admin center
C) Configure external access meeting policies
D) Update Teams meeting policies to disable external participant content sharing

Answer: D)

Explanation:

When external individuals join a Teams meeting, file uploading or sharing occurs only if meeting policies allow content contributions from non-organizational attendees. One configuration relates to removing the ability for external participants to share content at all. Disabling this ensures they can still join and interact verbally but cannot upload or present files. Modifying this parameter is the correct path for restricting the behavior described because it controls content permissions directly inside Teams meetings rather than tenant-wide sharing rules. 

Another configuration involves SharePoint administrative settings. This relates to how external individuals interact with files within SharePoint or OneDrive environments. Although file-sharing restrictions here prevent access to content stored in SharePoint libraries, they do not control the uploading behavior inside a live Teams meeting. Because the scenario describes meeting-specific file uploading, modifying SharePoint rules would not address the behavior that occurs within the Teams meeting interface. 

A different configuration involves guest access settings in the Microsoft 365 admin center. This controls long-term guests in the organization and governs whether they can participate in Teams channels, chat, and applications within your tenant. However, meeting participants joining anonymously or as external attendees do not rely on guest access settings for content upload abilities. Therefore, modifying guest access settings has no direct impact on file uploads within meetings. 

Another configuration concerns external access meeting settings, which regulate how external domains communicate with the tenant’s users through chat and calls. This mechanism enables or blocks cross-organization communication. While important, external access controls do not manage in-meeting content capabilities. They ensure whether a domain can interact at the communication layer but have no control over whether a participant can upload a file during the meeting itself.
Reviewing each configuration clarifies the correct action: the meeting policy that disables content sharing by external participants directly addresses file upload behavior during Teams meetings. When this policy setting is disabled, external attendees cannot upload content, share screens, or present files. Because this aligns perfectly with the organization’s objective, adjusting meeting policies is the proper solution.

Question 62: 

You need to ensure that users cannot schedule Teams webinars but can still schedule standard meetings. What should you configure?

A) Disable the “Allow Webinars” toggle in Teams meeting policies
B) Remove users’ ability to create Teams live events
C) Disable the Teams calendar app in app permission policies
D) Set all users to attendee roles for webinars

Answer: A)

Explanation: 

Controlling webinar creation is handled by a specific setting within Teams meeting policies that enables or disables webinar scheduling capabilities. Adjusting this setting allows Teams administrators to permit standard meeting creation while preventing webinar creation specifically. Users can still invite participants, manage meeting details, and conduct regular calls, but will not see the webinar creation interface. This is the precise mechanism for achieving the requirement. 

One administrative action involves removing individuals’ capability to create live events. Live events are distinct from webinars and serve a different purpose. They use separate scheduling flows and often involve one-to-many broadcasting. Because they are unrelated to webinar creation, turning this setting off will not prevent webinar scheduling. Users will continue to see webinar options in the Teams calendar unless meeting policy configurations are changed. 

Another possibility concerns disabling the Teams calendar app. Turning off this app removes the user’s ability to schedule any meetings through the Teams client interface. This approach would prevent webinars but would also prevent ordinary meeting scheduling. Because the goal is to allow standard meetings while blocking webinars, disabling the calendar app removes essential functionality for all meeting types and would not meet the requirement. 

There is also the configuration to assign users attendee status for webinars. This determines the user’s in-webinar role after a webinar has been created, but role assignment does not influence whether the user can create new webinars. Individuals configured as attendees may still schedule webinars if the governing policy permits. Therefore, this action affects participant roles but does not regulate scheduling rights. 

Evaluating each action reveals that only meeting policies contain the precise configuration needed to restrict webinar scheduling while leaving standard meeting scheduling intact. Turning off the webinar toggle within the meeting policy gives administrators direct control over this capability. This preserves normal organizational workflows and targets only the functionality the administrator intends to restrict.

Question 63: 

A department wants to use breakout rooms in Teams meetings but reports that some organizers cannot create them. What should the administrator verify?

A) Users are assigned the correct Teams meeting policy
B) The Teams Rooms devices are updated
C) The network supports QoS for real-time traffic
D) The corresponding Teams channels have shared files enabled

Answer: A)

Explanation: 

Breakout room creation capabilities depend on whether the meeting organizer is assigned a policy enabling meeting features that support breakout management. If individuals lack the correct meeting policy, the breakout room feature will not appear for them even if others in the organization can use it. Verifying policy assignment ensures that affected individuals receive the necessary configuration for creating, managing, and distributing participants into separate rooms. This is the direct and most relevant check for the reported issue. 

There is also the possibility of outdated Teams Rooms devices. Updating devices is essential for overall compatibility and performance, but Teams Rooms equipment relates to meeting-room hardware rather than the permissions or capabilities of meeting organizers. Device updates do not influence whether a person can create breakout rooms from their Teams desktop or web client. Therefore, while important, this action would not resolve the problem described. 

Another consideration is whether the network provides sufficient QoS. While quality-of-service helps ensure smooth audio and video interactions, it does not determine the availability of breakout room features. Bandwidth and prioritization settings influence performance rather than feature visibility. Users may experience call quality degradation without QoS, but they would not lose access to the breakout room functionality due to it. 

Some administrators might check channel file settings. File-sharing permissions within Teams channels determine whether users can collaborate on documents inside standard Teams channels, but they have no relevance to breakout rooms in meetings. Breakout rooms are purely meeting-level features, not channel-level resources. Adjusting channel settings would not impact whether users see the breakout room creation controls.
 

Examining all these factors reveals that feature availability for breakout rooms is controlled primarily by the meeting policy assigned to the organizer. Ensuring proper policy application is the only action aligned with resolving the issue of missing breakout room controls.

Question 64: 

You want to restrict students from starting private chats during remote classes in Microsoft Teams. What should you configure?

A) Set a messaging policy blocking private chat
B) Disable the chat app in Teams app permission policies
C) Block external access for the student domain
D) Set meeting policies to prevent chat during meetings

Answer: A)

Explanation:

A messaging policy allows administrators to regulate communication behaviors across Teams, including private chat. By disabling private chat in this policy, administrators can prevent students from initiating or engaging in one-to-one chats during remote sessions. This maintains classroom discipline while still allowing the essential meeting communication that takes place within the class environment. This is the most accurate configuration for controlling private chat behavior outside of meetings. 

Another configuration involves disabling the chat app entirely. This removes the chat feature globally for the affected users, including group chats, meeting chats, and all chat history access. However, the requirement specifies blocking private chats specifically while remote classes continue to operate normally. Disabling the entire chat application is a far more severe action and affects broader functionality than intended. 

There is also the consideration of blocking external access. This regulates communication between users in the student domain and other external domains. External access controls do not prevent internal users within the same organization from chatting with one another. Therefore, restricting external communication will not stop private chat between students enrolled in the same school environment. 

Another potential adjustment is meeting policies controlling chat inside meetings. While this does prevent chatting during a specific meeting session, it does not affect private chats that occur outside those sessions. Since the objective is to prevent private chats entirely, meeting chat restrictions address only part of the problem and do not produce the desired comprehensive restriction. 

Only the messaging policy directly addresses the behavior described. It provides fine-grained control over different types of communication and is designed precisely for situations where administrators must block or allow specific chat features independently of meeting-specific settings.

Question 65: 

Your organization needs to ensure that PSTN callers bypass the lobby when dialing into Teams meetings. What should you configure?

A) Meeting policy for “Automatically admit people”
B) Voice routing policy
C) External access policy
D) Teams app setup policy

Answer: A)

Explanation:

Lobby bypass for PSTN callers is controlled through meeting policy settings that determine which participants are admitted automatically. Changing the setting that automatically admits certain participant groups ensures PSTN callers enter meetings without requiring manual approval. This behavior supports organizations that want seamless calling experiences for telephone-based attendees and aligns directly with the described requirement. 

Voice routing policies influence how outbound PSTN calls are directed within the telephony configuration. These settings govern how Teams routes calls through SBCs or trunks but do not control meeting lobby behaviors. Adjusting routing policies affects call flows rather than admission controls for meeting attendees, so it is not relevant to lobby bypass functionality. 

Another configuration involves external access policies, which determine whether communication with external domains is permitted. These settings impact chat and calling between organizations but do not regulate meeting participant admission or lobby interactions. PSTN callers are not controlled through external domain access rules, so modifying this would not address the requirement. 

One might consider app setup policies, which control which applications appear in the Teams interface for users. Although important for user experience and app placement, these policies do not influence how PSTN callers enter meetings or whether they encounter a lobby. Adjusting app visibility provides no mechanism for affecting lobby behavior. 

Of all the configurations, the meeting policy is the only one that directly manages lobby bypass for PSTN attendees. Adjusting the setting to automatically admit PSTN callers ensures that telephone-based participants join the meeting immediately without waiting for organizer approval. This resolves the requirement effectively and is the correct configuration to implement.

Question 66: 

A global company wants to ensure that users in different regions are routed to the nearest Microsoft Teams media processor for optimal meeting quality. What should you enable?

A) Media Optimization for Teams
B) Location-Based Routing
C) QoS for Teams traffic
D) Regionally hosted meetings

Answer: A)

Explanation: 

Media optimization ensures that users are connected to a geographically appropriate media processor, reducing latency and improving real-time meeting performance. This setting is built specifically to optimize global media experiences across remote regions, ensuring media traffic automatically flows to the closest available processing resource. By enabling this capability, organizations enhance reliability and minimize unnecessary delays in audio and video transmissions for users located across diverse geographic zones.

Location-based routing controls PSTN call routing in compliance-driven environments. Its purpose is to ensure voice calls adhere to local telephony regulations by routing calls through specific gateways depending on user location. While useful for telephony governance, it does not influence how meeting media is processed or which Microsoft region handles call or meeting packets. Because the goal is to optimize media routing during meetings rather than PSTN call routing, this configuration does not satisfy the requirement.

QoS provides prioritization for audio, video, and screen-sharing packets within a network. While QoS is essential for delivering consistent call quality by reducing jitter and packet loss, it does not determine geographic routing. QoS ensures higher priority for Teams traffic but does not influence which cloud media processor Microsoft assigns to a meeting. Therefore, it improves performance but does not achieve regional optimization.

Regionally hosted meetings relate primarily to data residency and compliance. This involves storing meeting artifacts such as recordings, transcripts, and compliance objects in specific regions. Although it plays an important role in regulatory adherence, it does not control the routing of real-time media streams. Meeting media routing depends on intelligent cloud routing mechanisms rather than storage residency.

Considering all of these factors together, only media optimization provides the geographic routing control necessary to connect users to the nearest Microsoft media processor. It directly meets the requirement by enhancing meeting performance through region-aware routing, ensuring globally dispersed users receive the best possible meeting experience.

Question 67:

Your organization wants callers using Microsoft Teams Phone to hear menu prompts and be routed to departments automatically. What should you configure?

A) Call queue
B) Auto attendant
C) Direct Routing trunk
D) Caller ID policies

Answer: B)

Explanation: 

Auto attendants provide a structured, automated call-navigation system that greets callers and presents menu selections directing them to departments or services. They enable prerecorded greetings, dial-by-name directories, business-hour logic, multilingual menus, and routing actions. Because the requirement involves automated menus and guided call routing, the auto-attendant feature is the most aligned configuration to meet this need effectively.

Call queues distribute calls among agents in a group, presenting features such as waiting music, presence-based assignment, and overflow behaviors. While essential for managing call volume, they do not deliver automated menus or spoken navigational prompts. Call queues are typically connected after the auto attendant completes its routing actions, not used for the initial menu experience. Thus, they cannot fulfill the full requirement on their own.

Direct Routing trunks connect Teams to external PSTN providers. They define the telephony path rather than the interactive experience for callers. A trunk does not dictate how callers interact with menus or department flows; instead, it provides the PSTN connectivity foundation. Although vital for telephony connectivity, it cannot address automated routing needs.

Caller ID policies determine how outbound calls appear to recipients, controlling displayed numbers and privacy behavior. These policies have no role in guiding incoming callers or allowing them to navigate a structured menu system. They address identification rather than interaction.

Through comparison, the auto attendant is the only feature deliberately designed to deliver prompts and route callers intelligently. It fulfills the requested functionality precisely and provides the structure required for customizable and automated department routing.

Question 68: 

A company wants to restrict a specific group of users from recording too many Teams meetings to control storage usage. What should the administrator adjust?

A) OneDrive storage quotas
B) Teams meeting policy recording settings
C) Retention policies
D) Teams app permissions

Answer: B)

Explanation: 

Meeting policy recording settings directly determine who can initiate recordings and under what context recording capabilities are available. By adjusting these settings for specific groups, an administrator ensures that only those who require recording can perform it. This reduces unnecessary file generation and aligns perfectly with controlling the frequency of recordings. Because the behavior in question is the ability to start recordings, the meeting policy allows administrators to effectively regulate this capability.

OneDrive quotas control storage allocation but do not prevent meeting recordings from being generated. Users may still record meetings until their storage becomes full, which might disrupt work but does not enforce the proactive prevention required. The goal is not merely to restrict storage capacity but to prevent recording behavior altogether, making storage quotas insufficient to meet the requirement.

Retention policies govern how long recordings remain accessible before expiration or deletion. They apply after the recordings are created rather than before. While helpful for managing long-term data retention, they do not address excessive recording creation, as the recordings must exist first before retention logic applies. Consequently, they are not suitable for limiting recording activity.

Teams app permissions control the availability of applications within the Teams environment. They influence whether users can install or use apps but do not impact meeting functionalities like recording. Since the requirement concerns meeting feature control rather than app visibility, app permissions are unrelated to the stated objective.

Reviewing the functions of each configuration, meeting policy recording settings uniquely control the ability to record and align exactly with the task of limiting recording capacity among selected users.

Question 69: 

An organization wants a different default Teams app layout for a specific group. What should be configured?

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

Answer: A)

Explanation: 

App setup policies dictate which apps appear by default in the Teams interface and their order. By assigning such a policy to a specific user group, administrators gain full control over the default layout, including which apps are pinned, available, or hidden. This allows custom experiences tailored to the needs of specialized departments or teams. Because the requirement involves altering layout presentation, app setup policies provide the correct mechanism to accomplish this.

App permission policies regulate whether users are allowed to use certain apps at all. Their purpose is to allow or block apps rather than determine where they appear in navigation or how the interface is organized. Even if certain apps are permitted, the permission policy cannot configure layout or pinning. Thus, this setting does not answer the requirement for layout customization.

Teams update policies influence the delivery and timing of feature updates to client applications. These policies ensure that particular groups receive updates earlier or later based on administrative decisions. Although important for managing feature rollout, they do not modify app layout or pinned apps in the Teams client.

Teams device policies control behavior on Teams-certified physical devices, such as displays, phones, or meeting room equipment. They manage device-specific settings rather than the Teams software interface for desktop or mobile users. Changing such a policy would not affect app layout inside the Teams client.

Comparing these possibilities, only app setup policies provide direct control over layout customization, satisfying the requirement precisely.

Question 70: 

A manager wants transcription to begin automatically for all meetings created by a certain group. What should be configured?

A) Teams meeting policy transcription settings
B) Live captions settings
C) Compliance retention labels
D) Teams recording expiration settings

Answer: A)

Explanation:

Meeting policy transcription settings determine whether transcription is permitted and whether it begins automatically at the start of meetings. Adjusting this setting ensures transcription starts without manual effort. Because the goal is automatic transcript creation for every meeting organizer in the group, the meeting policy contains the exact controls necessary. It governs functionality at the meeting level and enforces consistent transcription behavior across designated users.

Live captions provide real-time captioning during meetings but do not generate stored transcripts. They allow participants to view spoken content in real time, improving accessibility, but once the meeting ends, no transcript remains. Since the requirement focuses on creating retrievable transcripts, live captions cannot meet the need.

Compliance retention labels govern how long data is stored and manage its lifecycle. They apply after content is created, rather than initiating or controlling creation itself. Retention labels ensure compliance and preservation but cannot automate transcription. Their influence spans what happens to transcripts after they exist, not whether transcripts are created.

Recording expiration settings control how long recordings remain accessible. They manage cleanup of stored content and prevent unnecessary accumulation of files. However, expiration settings do not influence transcription behavior at all. They apply after recordings or transcripts are stored rather than controlling creation.

Considering all factors, transcription settings within meeting policies are the only configuration that handles automatic transcript creation at the moment a meeting begins.

Question 71: 

You need to ensure that external users joining Teams meetings cannot share their screens. What should you configure?

A) Teams meeting policy content sharing settings
B) External access domain restrictions
C) Teams app permission policies
D) Meeting invitations customization settings

Answer: A)

Explanation: 

The setting that manages screen sharing for external individuals is located within the meeting policy content sharing configuration. This setting allows administrators to determine whether people outside the organization can present content or initiate screen sharing during meetings. When this feature is disabled for external participants, they can still attend but cannot present, ensuring tighter control of meeting content. This setting aligns exactly with scenarios where organizations need to restrict external presentation while maintaining attendance access.

Domain restrictions focus on whether users in external organizations can communicate with your tenant through chat or calling. Although important for cross-organization collaboration, domain restrictions do not control the ability to present content during meetings. Even when certain domains are disallowed, participants from permitted domains may still be able to join and potentially share screens unless the meeting policy content settings are adjusted. Therefore, this configuration does not meet the requirement.

App permission policies determine which applications users can access within the Teams client. This includes blocking or allowing third-party and custom apps. These permissions relate to app availability but do not influence in-meeting features like screen sharing. Adjusting app permissions will not prevent an external participant from sharing content, so this method cannot accomplish the desired restriction.

Customization settings for meeting invitations alter the appearance of meeting invites, adding elements like disclaimers, logos, or contact details. These settings help organizations standardize invitation formats but do not influence the functionality available within meetings. These configurations cannot disable screen sharing for external attendees because they only affect the invitation template.

After evaluating the distinctions among the four configurations, it is clear that content sharing settings within the meeting policy provide the correct mechanism for controlling external attendee presentation behavior. Adjusting this setting ensures that external users join meetings without the ability to share their screens, fulfilling the organizational requirement.

Question 72: 

You must ensure that Teams meeting recordings expire automatically after 60 days for a specific user group. What should you configure?

A) Teams meeting policy recording expiration
B) SharePoint storage quotas
C) Compliance communication supervision rules
D) OneDrive external sharing settings

Answer: A)

Explanation:

The Teams meeting policy contains a configurable setting that allows administrators to define how long recordings remain available before they automatically expire. Setting this value to sixty days ensures that any meeting recorded by users assigned to that policy will automatically be deleted after the defined period. This directly satisfies scenarios where organizations want to manage storage usage and ensure recordings do not persist unnecessarily.

SharePoint storage quotas apply to site storage management, such as regulating how much a site can hold before blocking uploads. Although meeting recordings are stored in OneDrive or SharePoint depending on the meeting type, storage quotas do not manage the lifespan of the recordings. They only set thresholds for capacity and will not trigger timed deletion after a specific period. Because the requirement centers on automatic expiration rather than storage limits, this configuration is not applicable.

Communication supervision rules in the compliance center monitor message content for regulatory or policy purposes. They track communication for violations but do not interact with meeting recordings or manage their retention. These rules cannot delete or expire recordings based on a defined timeline, so they are not suited for this purpose.

OneDrive external sharing settings govern how files stored in OneDrive can be shared with individuals outside the organization. These settings regulate collaboration behaviors but do not control retention timelines for files. Adjusting these settings will not ensure that recordings disappear at the 60-day mark.

Based on these distinctions, meeting policy expiration controls provide the precise mechanism needed to enforce timed deletion for recordings, making it the correct configuration.

Question 73: 

A department requires that all its Teams channels automatically standardize folder structures for new projects. What should the administrator implement?

A) Teams templates
B) Teams app setup policies
C) Sensitivity labels
D) Azure AD group naming conventions

Answer: A)

Explanation: 

Teams templates allow administrators to predefine structures for new teams, including channels, folders, tabs, and pre-installed apps. When the department creates new project teams, applying a predefined template ensures that every team includes the same folder organization and layout from the start. This enables consistent workflows across different projects and ensures users begin with a uniform structure.

App setup policies control which apps appear for users in the Teams interface. Although helpful for standardizing access to tools, these policies do not enforce folder or channel structures. They modify the appearance of the Teams client but cannot create default content or organizational layouts for new teams. Therefore, this configuration cannot standardize folder structures.

Sensitivity labels offer a way to classify and protect teams by enforcing settings such as privacy level, external sharing controls, and access restrictions. While powerful for security and compliance, sensitivity labels do not affect folder templates or structural layouts. They influence security behavior rather than organizational structure.

Azure AD group naming conventions regulate how groups are named, including prefixes or suffixes. This helps create internal consistency in naming but does not enforce folder designs or channel setups for Teams. These conventions assist with identification and administration but are not capable of applying structural templates.

Considering all these distinctions, team templates uniquely provide the ability to enforce predefined folder and channel structures for new teams, making them the correct solution.

Question 74: 

You need to assign Teams-certified desk phones to frontline staff and control their calling features. What should you configure?

A) Teams device policy
B) Calling plan assignment
C) Voicemail policy
D) App permission policy

Answer: A)

Explanation: 

A device policy allows administrators to manage how Teams-certified phones function, including locked-down modes, sign-in configurations, and permitted functionalities. By assigning specific policies to frontline staff, the organization can regulate how the phones behave, ensuring that calling features are configured to match operational requirements. This includes controlling whether users can sign out, restricting access to certain functions, and defining display preferences.

Assigning calling plans determines the PSTN connectivity available to users, such as domestic or international calling capabilities. Although calling plans provide telephony services, they do not regulate device-specific behavior or limit how desk phones can be used. Calling plans govern telephony capabilities, not hardware function, so they cannot satisfy the requirement involving desk phone functionality control.

Voicemail policies define how voicemail behaves for users, including whether transcription is enabled or whether callers may leave messages. These policies are applied at the user service level and do not influence the operational behavior of Teams desk phones. They do not manage device interfaces or calling feature availability.

App permission policies govern which applications are available to users within Teams but do not affect Teams-certified desk phones. Since the requirement focuses on managing desk phone functionality, app permission policies cannot achieve this.

Device policies uniquely control the behavior of Teams-certified desk phones, making them the right configuration.

Question 75: 

Your organization wants to allow help desk staff to view Teams call analytics but not modify tenant-wide settings. What role should you assign?

A) Teams Communications Support Specialist
B) Teams Administrator
C) Global Reader
D) Compliance Data Administrator

Answer: A)

Explanation: 

The Teams Communications Support Specialist role is designed specifically for individuals who need to access call analytics and call quality dashboards without affecting administrative configurations. This makes it suitable for help desk teams who must troubleshoot user calling issues without obtaining broader administrative power. They can view metrics, examine call reports, and support end users safely.

The Teams Administrator role provides full administrative control over Teams, including messaging policies, meeting policies, and tenant-wide configurations. Assigning this role grants far more authority than needed and introduces unnecessary risk by giving help desk staff the ability to alter major configurations.

The Global Reader role allows viewing all configuration data across Microsoft 365. Although this role does provide broad read-only access, it does not grant targeted visibility into Teams-specific call analytics in a dedicated manner. It also provides visibility to areas unrelated to the help desk’s responsibilities.

The Compliance Data Administrator manages compliance-related data tasks, such as retention and audit configurations. This role is unrelated to Teams call troubleshooting and would not provide access to call quality dashboards.

Based on the intended scope of responsibilities, the Teams Communications Support Specialist role perfectly aligns with the requirement.

Question 76: 

A training department wants every meeting they host to include meeting recording enabled by default. What should you configure?

A) Teams meeting policy automatic recording
B) Microsoft Stream permissions
C) Live event policy
D) Teams app setup policy

Answer: A)

Explanation: 

The automatic recording setting in the meeting policy ensures that every meeting created by users assigned to that policy begins recording as soon as the meeting starts. This is the only configuration that enforces recording behavior at the meeting level. It is ideal for training teams who must document sessions consistently for compliance or later review.

Stream permissions determine who can view recordings after they are saved but do not activate recording automatically. Even with broad viewing access, recordings must still be manually initiated unless meeting policy settings enforce automatic recording.

Live event policies govern large-scale broadcast events rather than standard meetings. These policies are unrelated to standard Teams meeting behavior and cannot automate recording for normal training sessions.

App setup policies specify which apps appear in the Teams client interface. These policies cannot influence meeting recording behavior, making them unsuitable for this requirement.

The meeting policy’s automatic recording setting is the only configuration that directly ensures recordings begin without manual action, fulfilling the requirement.

Question 77: 

Your company needs to restrict who can create new teams while allowing existing teams to function normally. What should you configure?

A) Office 365 group creation restrictions
B) Teams update policies
C) Teams device policies
D) Channel moderation

Answer: A)

Explanation:

 Restricting group creation effectively limits who can create new teams because every team is backed by a Microsoft 365 group. By configuring group creation permissions through Azure AD, administrators can define which users or security groups are allowed to create new groups, thereby restricting team creation. Existing teams remain unaffected, and the organization retains control over growth.

Teams update policies determine how the Teams client receives new features. These policies do not influence team creation rights, so they cannot meet the requirement of restricting new team creation.

Device policies apply to certified Teams hardware. They manage features like kiosk mode or phone behavior but do not affect administrative rights to create teams within the Teams interface.

Channel moderation controls who can post messages in specific channels. This does not relate to the ability to create teams and therefore cannot address the organizational need.

Because group creation restrictions directly control team creation, they are the correct configuration.

Question 78: 

You want all Teams chats involving sensitive departments to be logged and stored for regulatory purposes. What should you configure?

A) Retention policies
B) App setup policies
C) Calling plan features
D) Teams display device settings

Answer: A)

Explanation: 

Retention policies are the primary mechanism used in Microsoft 365 to preserve, store, or delete Teams chat data in accordance with regulatory or auditing requirements. When an organization needs to ensure that all chats involving specific departments are captured and retained for compliance, retention policies provide the exact controls necessary. Administrators can create policies that apply to Teams chats and channel messages, selecting specific users or groups—such as sensitive departments—to ensure their communications are retained for regulatory durations. These policies make it possible to preserve content even if users attempt to delete messages, ensuring the organization meets strict industry or legal requirements. Retention policies also integrate with the Microsoft Purview compliance framework, making the stored data searchable for investigations, legal requests, or internal audits.

B refers to app setup policies, which manage the visibility and arrangement of apps in the Teams interface. Their purpose is to control which apps appear by default and how users interact with them, but they do not manage data preservation, message logging, or storage retention. App setup policies do not interact with Teams chat content at any compliance or archival level, making them unsuitable for fulfilling regulatory storage requirements.

C refers to calling plan features, which regulate PSTN calling capabilities such as outbound and inbound dialing, number assignments, and telephony behavior. Calling plans are entirely unrelated to chat content and therefore cannot preserve chat data or ensure compliance-based logging. They manage voice functionality only and have no role in data storage or retention of messages.

D refers to Teams display device settings, which involve hardware configuration for Teams display units used as dedicated communication devices. These settings are focused on user interface behavior, notifications, screen control, and device-specific features. They do not interact with Teams chat data and certainly cannot enforce retention or compliance requirements.

Because the organization needs to ensure long-term preservation and regulatory compliance for chat content, the only option that provides direct control over data lifecycle, preservation, and storage is retention policies. They deliver granular assignment, consistent enforcement, and alignment with compliance standards, making them the correct configuration.

Question 79: 

You need to ensure that only managers can schedule Teams live events. What should you modify?

A) Live event policies
B) Teams templates
C) Device tagging
D) Teams app permission policy

Answer: A)

Explanation: 

Live event policies define which users are permitted to create and schedule Teams live events. When an organization needs to restrict live event creation so that only individuals in managerial roles can schedule them, administrators can create a custom live event policy that allows scheduling and assign it exclusively to managers. All other users can be assigned a more restrictive policy that disables the ability to create live events. This approach ensures fine-grained, user-level control over who is allowed to schedule large-scale broadcast-style events. Live event policies also enable administrators to configure event permissions, organizer capabilities, and attendee access rules, making them the proper tool for managing who can host live events across the organization.

B refers to Teams templates, which provide standardized team structures including channels, tabs, apps, and recommended configurations. Templates are designed to simplify the process of creating new teams for consistent organizational usage. However, they do not control capabilities related to event creation or scheduling privileges. Templates affect team structure, not live event permissions.

C refers to device tagging, which helps administrators categorize, group, and manage Teams devices for bulk operations or specific management tasks. Device tagging is unrelated to user permissions and does not regulate who can schedule meetings or events. It is useful for device management only, not user access control.

D refers to Teams app permission policies, which manage which applications users are allowed to use or install within the Teams environment. These policies are effective for blocking or allowing third-party or Microsoft apps but do not govern live event scheduling rights. App permission policies cannot restrict access to the creation of live events.

Because the requirement is specifically about who can schedule live events and this capability is controlled exclusively through live event policies, the correct answer is live event policies. They provide the necessary granularity and targeted control to ensure only managers have scheduling privileges.

Question 80: 

An organization wants to ensure that guests cannot access shared files within Teams channels. What should be adjusted?

A) SharePoint site permissions
B) Teams app setup policies
C) Teams live event policy
D) Teams update policy

Answer: A)

Explanation: 

SharePoint site permissions govern access to the files stored in Teams channels because every standard and private channel stores its files in an associated SharePoint site or SharePoint folder. When an organization needs to ensure that guests cannot access channel files, modifying SharePoint permissions is the appropriate approach. Administrators can remove guest permissions entirely, restrict access to the document library, or limit sharing settings so guests cannot view, download, or edit shared content. Since Teams channel file access is directly tied to SharePoint’s permission model, adjusting SharePoint access controls ensures that guests are prevented from interacting with shared files, regardless of their participation in Teams chats or meetings. This method provides a reliable and enforceable restriction for protecting sensitive content.

B refers to Teams app setup policies, which determine which apps are shown or pinned for users. These policies affect interface visibility but cannot block access to files stored in SharePoint. They are not involved in content security and do not regulate guest access to documents.

C refers to Teams live event policies, which manage permissions related to creating and hosting live events. These policies do not influence access to files within Teams channels or SharePoint libraries. Their scope is limited to event production settings.

D refers to Teams update policies, which determine how and when the Teams client receives feature updates. While useful for managing client versions, these policies have nothing to do with file access security or guest restrictions.

Because Teams relies on SharePoint for file storage, and SharePoint controls file access at a granular level, adjusting SharePoint site permissions is the correct and necessary method to block guest access to channel files.