Describe Microsoft 365 apps and services practice questions

Microsoft Forms

Why it fails: Microsoft Forms is a lightweight data-collection tool for building surveys, quizzes, and polls, not for visual content composition. Its interface only supports form fields like multiple-choice and text inputs, with no freeform layout, theming, or embedding of rich media. As a result, it cannot produce a visually rich newsletter with narratives and imagery.

Microsoft Stream

Why it fails: Microsoft Stream is a video hosting and streaming platform where organizations upload, manage, and play back video content. It does not provide any document authoring, text layout, or design capabilities, so it is unsuitable for creating a newsletter. While you could embed a newsletter link in a Stream video or link a video in Sway, the service itself cannot generate the visual asset.

Microsoft Microsoft Viva Engage

Why it fails: Microsoft Viva Engage (formerly Yammer) is an enterprise social network focused on community conversations, announcements, and employee engagement. Its primary artifacts are posts, polls, and threads that live in feeds, not designed documents or newsletters. Although it amplifies communication, it lacks the authoring and layout engine needed to compose a visually rich newsletter.

Microsoft Teams

Why it fails: Microsoft Teams does provide meeting scheduling, but that capability is built on Exchange/Outlook calendar services rather than a separate scheduling engine. When you use 'Schedule a meeting' in Teams, it opens Outlook's scheduling assistant data for free/busy lookup, meaning Teams cannot function as the primary calendar source of truth. For a direct team-project sync, Outlook is the authoritative scheduler, so Teams is not the best answer.

Microsoft Bookings

Why it fails: Microsoft Bookings is an external-facing appointment service where clients select from staff-defined service offerings via a public booking page. It does not reconcile the free/busy calendars of multiple internal team members for an ad-hoc meeting; instead, it enforces per-person availability rules and buffer times for customer appointments. Since the scenario is an internal team meeting, Bookings' external scheduling model makes it an incorrect choice.

Microsoft Shifts

Why it fails: Microsoft Shifts, included in Teams for the Frontline Worker, is designed to assign and manage recurring shift schedules for hourly or location-based staff, not to create calendar meeting invitations. It tracks clock-in/out, shift requests, and open shift offers, but it never accesses attendees' free/busy availability or sends a standard Outlook meeting invite. Therefore, Shifts cannot be used to schedule an impromptu project status discussion among team members.

Microsoft Planner

Why it fails: Microsoft Planner is a lightweight project tracking service in Microsoft 365 that uses kanban-style boards to organize tasks and assignments, but it does not include a document library or native file storage of its own. While you can attach links to files stored elsewhere (e.g., SharePoint), there is no built-in co-authoring, version history, or centralized document repository within Planner itself. Because the project manager needs a single location to store documents and enable real-time collaboration, Planner alone fails to satisfy that core requirement.

Microsoft Project Online

Why it fails: Project Online lacks the real-time co-authoring capability required by the stem; its documents are stored in SharePoint but editing is primarily offline or check-in/check-out, not simultaneous co-editing. It is tempting because it offers centralised task assignment and milestone tracking, and would be the correct choice if the scenario required detailed schedule management, resource levelling, or Gantt chart dependencies rather than real-time co-authoring.

Microsoft To Do

Why it fails: Microsoft To Do is a personal productivity application designed for individual task lists, reminders, and cross-device sync, not for team collaboration or content management. It does not provide a shared workspace, document storage, versioning, or permission-based access, and files cannot be co-authored directly within the app. To Do also has no integration with SharePoint or Microsoft Teams for centralized team content, so it cannot serve as the project manager's repository for project documents or enable the real-time collaboration described in the scenario.

Outlook on the web

Why it fails: Outlook on the web is incorrect because it is an email and calendaring client, not a co-authoring platform; it has no native document editor and cannot merge simultaneous edits from multiple people. You might attach a proposal file, but each recipient would need to download, edit, and re-upload, creating conflicting copies and losing version control. The service does support shared mailboxes and calendar sharing, but that doesn't enable concurrent input into a single document.

OneNote for Windows 10

Why it fails: While OneNote does support real-time collaboration, the 'OneNote for Windows 10' version is legacy and lacks full version history compared to the modern OneNote app. More importantly, the scenario focuses on document co-authoring, and Word and Excel web are the clearest choices.

Microsoft Forms and Microsoft Power Automate

Why it fails: Microsoft Forms provides the survey interface where team members can submit weekly status reports, and each submission is automatically recorded in an associated Excel workbook. Microsoft Power Automate can then use the 'When a new response is submitted' trigger for Forms to send an immediate email notification to the manager, fulfilling both the collection and alerting requirements. The combination is correct because Forms handles the structured input and Power Automate delivers the real-time notification that Forms alone cannot natively generate.

Microsoft Lists and Power Automate

Why it fails: Microsoft Lists is designed for managing structured, shared data such as tasks or inventory, but it does not provide a free-form, front-end submission form that team members would naturally use for weekly narrative reports. Although Power Automate can send notifications based on list item creation, the collection mechanism is not a user-friendly form and would require team members to edit the list directly, which is error-prone and not designed for status updates. Therefore, this option is incorrect because the primary data-capture component is not a form, making it unsuitable for the stated workflow.

Microsoft Excel only

Why it fails: A standalone Excel workbook does not provide a form-based interface for data entry, so team members would need to edit the spreadsheet directly, increasing the risk of accidental data corruption or formatting errors. Excel also has no native event-driven automation to detect when a new row is added and trigger an automatic email notification without external scripting or add-ins. Without Power Automate to connect Excel's 'When a new row is created' trigger to an email action, Excel alone cannot satisfy the notification requirement of this scenario.

Microsoft Lists

Why it fails: Microsoft Lists is a lightweight data-tracking app in Microsoft 365 that allows teams to create customizable lists for simple records such as inventory, issues, or event registrations. While it can mimic a basic sales pipeline using views and conditional formatting, it lacks core CRM functionality like lead qualification, opportunity stage management, quote-to-order workflows, and integrated customer communication history. Lists does not provide relationship intelligence or automation, so it is insufficient for managing a sales team's pipeline and customer interactions.

Microsoft Viva Sales

Why it fails: Microsoft Viva Sales is a seller-experience add-on that surfaces customer data and context in Outlook and Teams, but it is not a standalone CRM. Viva Sales relies on an underlying CRM—either Dynamics 365 or Salesforce—to store and manage pipeline and customer information; it only enhances the seller's day-to-day productivity by automating activity capture and providing contextual reminders. Because it has no native pipeline database of its own, it cannot serve as the primary tracking system for a sales team, and deploying it would require purchasing a full CRM first.

Microsoft To Do

Why it fails: Microsoft To Do is a personal task management application designed for individual productivity, allowing users to create simple to-do lists, set reminders, and prioritize daily tasks with My Day. It has no concept of customers, leads, or opportunities, nor does it support shared pipelines, team-level activity tracking, or communication history. While a salesperson might use it for personal follow-up reminders, it cannot provide the structured CRM functionality needed to track a team's pipeline and customer communications.

Microsoft Purview Audit

Why it fails: Microsoft Purview Audit is a compliance and forensic tool that records user and admin activities across Microsoft 365, such as file access, permission changes, and sign-in events. It does not provide a location to store personal work files — it generates logs for security investigations, not a collaboration workspace. Therefore, it cannot meet the requirement of storing personal work.

Microsoft Planner

Why it fails: Microsoft Planner is a lightweight task management application based on the Microsoft 365 Groups model, offering Kanban-style boards with tasks, assignments, and due dates. It does not include a file storage repository for personal work; any attached files are links to other locations like SharePoint or OneDrive. Hence, it is unsuitable for the stated storage need.

Microsoft Forms

Why it fails: Microsoft Forms is an online tool for creating surveys, quizzes, and polls, with responses collected in a simple grid or Excel online. It does not offer a file storage area for personal work documents or any general-purpose collaboration file management. Thus, it is unrelated to the stated requirement of storing personal work.

Microsoft Planner

Why it fails: Planner is mainly for task management, not this requirement.

Microsoft Forms

Why it fails: Forms is mainly for surveys and quizzes, not this requirement.

Microsoft Purview Audit

Why it fails: Audit records activities and does not provide the requested collaboration function.

Microsoft Purview Audit

Why it fails: Microsoft Purview Audit records and retains a unified audit log of security and compliance events such as sign-ins, file accesses, and admin actions across M365 workloads. It is a backend monitoring tool, not a user-facing data collection service, so it cannot present a survey or aggregate employee feedback. While the audit log might later help confirm which licenses or features are used during the adoption, it does not fulfill the consultant's need to collect collaboration-focused input.

Microsoft Planner

Why it fails: Planner is a collaboration and task-management service organized around buckets, cards, checklists, and assignments, so it is ideal for tracking the execution steps of an adoption plan. It has no survey designer, no quiz logic, and no response repository, meaning it cannot solicit or consolidate open-ended answers from many employees. Asking employees to submit feedback as Planner comments would mix opinions with task updates and leave no structured way to report on the results.

Microsoft Purview Audit

Why it fails: Microsoft Purview Audit is a security and compliance solution that records user and admin activities across Microsoft 365 services, such as sign-in events, file access, and mailbox operations. It does not offer any planning, task, or collaboration workflow—it only logs what has happened after the fact. Therefore, it cannot satisfy a request for coordinating work among team members, making it an incorrect option for this requirement.

Microsoft Forms

Why it fails: Microsoft Forms is designed for creating surveys, quizzes, and polls, with responses collected in an Excel workbook and real-time charts available to the form owner. While a form might ask who will do a task or when it should be done, it cannot serve as a persistent shared workspace to manage assignments, update statuses, or track due dates across multiple users. Thus, it falls short of the collaboration and task management capability described in the question, so it is not the correct choice.

Microsoft Teams

Why it fails: Microsoft Teams is optimized for collaboration within defined teams and channels, with membership restrictions and chat-centric interactions. Posting to a team only reaches that team's members, not automatically the entire organization, and there are no built-in upvoting or Q&A features. While you could create a huge team, it is not designed for organic, discovery-based company-wide announcements and community engagement.

SharePoint

Why it fails: SharePoint offers sites, lists, and news posts that can display announcements, but these are essentially static, publisher-controlled pages. It lacks native social mechanics such as upvoting, threaded community Q&A, and user-generated answers without considerable customization or third-party integrations. Therefore, SharePoint is not the ready-made, interactive solution for company-wide announcement posts.

Outlook

Why it fails: Outlook is fundamentally a mail client and personal information manager, not a social-communication platform. While you could send a company-wide email blast, the message is one-way, ephemeral, and buried in inboxes, with no persistent, searchable feed or structured Q&A. It also lacks native upvoting or community features, so it fails to support interactive, engaging company-wide announcements.

Microsoft Power Apps

Why it fails: Power Apps is for building custom apps; it does not natively provide event-driven email workflows.

Microsoft Outlook

Why it fails: Outlook is an email client; the automation logic is handled by Power Automate, not Outlook itself.

Microsoft Entra Privileged Identity Management

Why it fails: Microsoft Entra Privileged Identity Management is an identity governance control that enables just-in-time, time-bound, and approval-based role activation for privileged administrators. It does not offer document storage, sync, or file sharing capabilities, so it cannot satisfy a department's need for a service to store and collaborate on files among 10 users.

Microsoft Defender for Endpoint

Why it fails: Microsoft Defender for Endpoint is a cloud-based endpoint protection platform that continuously monitors devices for suspicious behavior, automates threat response, and provides security investigations. It is designed to safeguard endpoints from malware and attacks, not to enable file sharing or day-to-day collaboration tasks, so it is not relevant to this department's requirement.

Microsoft Purview Compliance Manager

Why it fails: Microsoft Purview Compliance Manager is a risk-based compliance solution that assesses an organization's compliance posture, manages controls, and tracks progress against data protection and regulatory standards. It does not provide a workspace for storing, syncing, or sharing files, and it would not help a department of 10 complete collaborative work.

Microsoft Purview eDiscovery case

Why it fails: eDiscovery is for legal investigation, not daily team collaboration.

Exchange anti-malware policy

Why it fails: Anti-malware policies protect mail flow but are not the primary collaboration workspace.

Microsoft Purview eDiscovery case

Why it fails: Microsoft Purview eDiscovery is a legal and regulatory compliance solution, not a collaboration or automation service. It is used to identify, preserve, collect, and export content from Exchange, SharePoint, and Teams for litigation or investigation purposes. eDiscovery cases support legal holds, searches, and review sets, but they have no ability to execute business workflow approvals or automate approval decisions. This makes it completely misaligned with the team's objective.

Exchange anti-malware policy

Why it fails: Exchange anti-malware policies are part of Exchange Online Protection and are designed to filter malicious content from email messages as they traverse the mail flow. These policies scan inbound and outbound messages, quarantine threats, and generate threat reports, but they do not provide any collaboration workspace or workflow approval logic. Their function is strictly security-based and unrelated to building or executing approval workflows.

The user registers their verification methods first, then the admin enables MFA for the user.

Why it fails: This ordering cannot work in practice because the user will only see the registration prompt after an admin has enabled MFA on their account. The Microsoft 365 platform does not offer a pre-registration workflow for the user to add verification methods independently before MFA is activated. Without the admin enabling MFA, the user's sign-in experience remains unchanged and the registration step never triggers.

Enable MFA for the user, then configure the default authentication method, then the user registers verification methods.

Why it fails: The default authentication method is not something an admin pre-configures per user in the legacy MFA setup; rather, the user selects and confirms their default sign-in method during the registration flow. Admin configurable policy, such as the Authentication methods policy, controls which methods are available, but it does not designate a user's default ahead of registration. Inserting a 'configure default method' step between enabling MFA and user registration misrepresents both the ordering and the administrative role in that process.

Configure the MFA service settings (e.g., number of methods required), then enable MFA for the user, then the user registers.

Why it fails: This is incorrect because while service settings can be configured before enabling MFA for individual users, the core required order is enabling MFA first, then registration. Adding the service settings step is unnecessary and may mislead about the essential sequence.

Microsoft 365 Copilot for Microsoft 365 with no additional license

Why it fails: The correct name is 'Microsoft 365 Copilot' and it requires a qualifying Microsoft 365 license.

Microsoft 365 Copilot standalone license without any other subscription

Why it fails: Copilot requires a qualifying Microsoft 365 license (E3/E5 or Business Premium) as a prerequisite.

Microsoft 365 Business Basic

Why it fails: Business Basic does not include Copilot; it requires E3/E5 or Business Premium.

blockAccess

Why it fails: The `blockAccess` element is a boolean flag that, when set to `true`, actively prevents unauthorized users from opening or using the content. In the JSON snippet, this is the only property that directly enforces an access-control action on the item, making it the correct answer. It controls whether access is allowed or denied at the authorization layer, rather than merely encrypting or marking the content.

applyWatermark

Why it fails: The `applyWatermark` element is a content-marking action that adds a visible text overlay (for example, 'Confidential' or 'Draft') to a document or email to deter leakage and remind users of the sensitivity level. This visual indicator helps with data loss prevention but is non-blocking: the content remains accessible to anyone who has already obtained it, so it cannot be the element responsible for stopping unauthorized access.

labels

Why it fails: The `labels` element refers to sensitivity label metadata—such as the label ID or name assigned to the item—rather than an action that can be executed. Labels classify content and trigger policies, but they do not themselves perform access control operations; a label reference alone never prevents a user from opening a file. This is why `labels` is not the action that blocks access in the JSON snippet.

Microsoft Teams

Why it fails: Microsoft Teams is a collaboration hub that relies on SharePoint Online for file storage and Exchange Online for messaging, but it is not itself an Azure-deployable resource. An ARM template provisions infrastructure such as storage accounts, databases, or virtual networks, whereas Teams is a SaaS application layer. Even if the exhibit shows a Teams-related deployment, the actual Azure resources being deployed would be the underlying SharePoint or Exchange backends, not Teams itself.

Exchange Online

Why it fails: Exchange Online is a dedicated SaaS workload that stores mailbox data in its own Exchange databases, not in Azure Storage blobs or other ARM-provisioned resources. While Exchange Online runs on Microsoft's global infrastructure, its content databases are managed by the Exchange service and are not directly configurable via ARM templates. Therefore, an ARM template would not target Exchange Online as the deployed resource, because it lacks the Azure resource provider for mailbox stores.

OneDrive for Business

Why it fails: OneDrive for Business is built on top of SharePoint Online; each user's OneDrive library is stored in a personal site collection within SharePoint's managed databases. Although OneDrive files ultimately reside in Azure Storage, OneDrive itself is not a distinct Azure resource and cannot be provisioned independently via an ARM template. The ARM template would target the underlying SharePoint infrastructure, making OneDrive for Business a derivative service rather than the primary deployment target.

The user's Exchange Online mailbox is full

Why it fails: A full Exchange Online mailbox is a storage quota issue that primarily affects sending and receiving email. Although Teams meeting messages are delivered through Exchange, the Teams calendar and meeting scheduler are part of the Teams service and do not rely on available mailbox storage to create a meeting invitation. Therefore, this condition would not prevent a user from scheduling a meeting with external participants and is not the root cause.

The Teams client is outdated

Why it fails: An outdated Teams client can cause display glitches or connection errors, but meeting scheduling logic is processed by the Microsoft Teams backend, not by the local client version. External meeting invites are a standard, mature feature present in all supported Teams clients, and a client version problem would typically produce a client-specific message rather than silently preventing external scheduling. Since the user's issue is specific to meetings with external parties, a licensing issue is more plausible than the client's version.

Guest access is disabled

Why it fails: Guest access is an Microsoft Entra B2B feature that controls whether outside users can be added to a team or channel, not whether a licensed user can send a meeting invitation. Scheduling a Teams meeting with external recipients uses the organizer's Exchange calendar and the meeting invitation mechanism; external recipients can attend as anonymous participants or after a simple one-time acceptance without ever being added as guests. Consequently, disabling guest access would limit shared team spaces but would not stop the otherwise licensed user from creating a meeting with external email addresses.