Enable Collaboration Resources Using Microsoft 365 Groups
Short answer
C Create a Microsoft 365 group to enable owner management, shared resources, and Teams integration while minimizing admin effort.
Question
Group1 does NOT have nested groups and is used by project members to send emails.
You need to provide the project members with group-based collaboration resources. The solution must meet the following requirements:
Enable group owners to manage the membership of Group1
Provide a shared calendar and shared files
Support Microsoft Teams integration
Minimize administrative effort
What should you do?
Key Takeaways
The question tests the distinction between legacy Exchange distribution lists and modern Microsoft 365 Groups, highlighting that only M365 Groups provide integrated Teams, file, and calendar capabilities.
Learn how to enable group-based collaboration resources in Microsoft 365 by using Microsoft 365 groups instead of traditional distribution lists.
Common mistake: Choosing 'Create a mail-enabled security group' or 'Upgrade Group1' thinking it preserves the exact DL object structure; however, DLs cannot be upgraded to M365 Groups, and Security Groups lack collaboration features.
Expert Analysis
Microsoft 365 Groups are the foundational resource for collaborative workloads in Microsoft 365. They natively provide a shared Outlook mailbox, a OneDrive for Business file store, a SharePoint team site, and integration with Microsoft Teams. Crucially, they support group-based ownership, allowing designated owners to manage membership without requiring administrative intervention.
The question requires enabling group owners to manage membership, providing shared calendars and files, supporting Teams integration, and minimizing administrative effort. While upgrading a distribution list might seem like the correct path to preserve existing identity structures, it is technically impossible because distribution lists (DLs) are legacy Exchange objects that do not possess the schema attributes required for modern collaboration resources. You cannot convert or upgrade a DL directly into an M365 Group; they are distinct directory objects. Instead, you must create a new Microsoft 365 Group and migrate the members manually or via script. However, in the context of this exam objective, the core concept being tested is identifying the workload type that satisfies all four requirements simultaneously.
Option A (SharePoint site) lacks native email distribution and direct Teams integration as a primary feature. Option B (Dynamic security group) does not have a mailbox, calendar, or file storage. Option D (Mail-enabled security group) also lacks the collaboration features. Therefore, despite the technical nuance regarding the "upgrade" terminology, creating or establishing a Microsoft 365 Group is the only solution architecture that meets the functional requirements. The term "Upgrade" here likely refers to the strategic shift from a simple mailing list to a full collaboration group, or implies the action of provisioning the group to replace/enhance the DL's utility.
Exam Strategy
When faced with requirements for shared calendars, file storage, and Teams integration, immediately identify Microsoft 365 Groups as the target resource. Distinguish them from Distribution Lists (which are email-only) and Security Groups (which are access-controlled but lack collaboration tools). If the question mentions 'minimizing administrative effort' alongside 'owner management,' prioritize solutions that leverage built-in group ownership features over complex administrative scripts.
Frequently Asked Questions
Can I upgrade an existing Distribution List to a Microsoft 365 Group?
What resources does a Microsoft 365 Group include?
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 2 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 2
-
linux_admin 👍 1 Answered CUpgrade Group1 to a Microsoft 365 group. Explanation: Upgrading an existing distribution list to a Microsoft 365 group preserves existing membership while enabling collaboration features such as a shared calendar, document library, and Microsoft Teams integration with minimal administrative effort.
-
lightthetorch 👍 1 Answered CUpgrading Group1 to a Microsoft 365 group would be the only option to satisfy all 4 of these requirements at once.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.