Describe Microsoft 365 apps and services practice questions

Microsoft Teams

Why wrong: Microsoft Teams is a collaboration hub that brings together chat, meetings, and file access, but its document storage and co-authoring capabilities rely entirely on the underlying SharePoint and OneDrive services. When users edit a file from a Teams channel, it is actually stored in a SharePoint document library, with Teams acting only as an interface. Therefore, while Teams supports collaboration, it is not the primary document management service for co-creating content.

OneDrive for Business

Why wrong: OneDrive for Business is intended for personal cloud storage and sharing individual files, not for team-wide content management. While you can share a document with multiple people and co-author in real-time, it lacks the structured team site features like shared document libraries, metadata columns, and site-level permissions that a marketing team requires for collaborative projects. For ongoing, organized team collaboration, SharePoint Online is the dedicated solution.

Microsoft Viva Engage

Why wrong: Microsoft Viva Engage, formerly Yammer, is an enterprise social network focused on communities, announcements, and threaded discussions rather than document collaboration. It does not offer native co-authoring or document libraries, and while you can share links to files, the actual editing happens elsewhere. Its purpose is to foster communication and engagement, not to support the collaborative creation and editing of content.

Power Apps

Why wrong: Power Apps is a low-code application development platform used to build custom canvas apps or model-driven apps for specific business needs, such as a mobile client for tracking deals. While it can be embedded in Microsoft Teams and can call Power Automate flows, its primary purpose is creating user interfaces and business logic, not orchestrating automated workflows or approvals. Therefore, it is not the correct tool for automating approval processes within Teams and Dynamics 365.

Power BI

Why wrong: Power BI is a business analytics and data visualization tool that allows you to create interactive dashboards and reports from various data sources, such as Dynamics 365 sales records. Although Power BI reports can be embedded in Teams for visibility, Power BI does not execute actions, send messages, or manage approval workflows. It is designed for analysis and insight, not for automating business processes, so it cannot fulfill the requirement of creating automated workflow for the sales team.

Power Virtual Agents

Why wrong: Power Virtual Agents is a tool for building intelligent chatbots that can converse with users in natural language and can be deployed within Microsoft Teams to handle FAQs or simple customer queries. While a bot built with Power Virtual Agents can trigger a Power Automate flow to perform backend actions, the platform itself is not a workflow automation tool. It focuses on creating conversational experiences, not on automating multi-step business processes like approvals, making it incorrect for this scenario.

Microsoft Project Online

Why wrong: Microsoft Project Online is an enterprise project and portfolio management (PPM) tool designed for complex requirements such as task dependencies, resource capacity planning, cost tracking, and project timelines. While it can be integrated with Teams, using it simply to maintain a shared task list would introduce significant administrative overhead, advanced licensing requirements, and a steeper learning curve. Its feature set is far beyond basic shared task tracking, which is why it is not the correct choice for this scenario.

Microsoft To Do

Why wrong: Microsoft To Do is primarily a personal task management app focused on individual productivity, with features like My Day, reminders, and personal to-do lists. Although Planner and other Microsoft 365 tasks can surface in a user's To Do, To Do does not provide a shared, team-wide workspace where all members can view a single collaborative list, see assignees, or track group progress. This makes it unsuitable for a project team that needs a shared and shared-ownership task list.

Microsoft Lists

Why wrong: Microsoft Lists is a flexible data-tracking application that lets users create custom lists with different column types, views, and formatting, and it can be added as a Teams tab. However, it is a general-purpose information tracker rather than a dedicated task management service, so it lacks built-in task assignments, due date reminders, progress charts, and workflow automation that Planner provides natively. While you could manually mimic a task list with an "Assigned To" column, Lists is better suited for tracking assets, issues, or structured data.

Excel

Why wrong: Excel can create static charts and pivot tables, and even connect to external data using Power Query and Power Pivot. However, it is not designed for real-time, multi-source data integration or interactive dashboard experiences that update automatically for multiple simultaneous users. Excel files are typically siloed and require manual refresh, lack centralized governance and row-level security, and do not provide the same mobile-optimized, shared, and live dashboard capabilities as Power BI, making it a limited choice for this requirement.

Power Apps

Why wrong: Power Apps is a low-code application development platform for building custom business applications, such as forms, approvals, and data-entry tools. It uses data sources like Dataverse and can display simple galleries or charts, but it is not optimized for BI-style visualization, complex aggregations, or real-time analytical dashboards. Creating a sales analytics dashboard in Power Apps would require significant custom code and would still lack Power BI's rich visualization library, built-in AI insights, and enterprise-level sharing and governance, so it is incorrect for this task.

SharePoint

Why wrong: SharePoint is primarily a collaboration and document management platform, not a business intelligence tool. While it can display data from lists through web parts or embed Power BI reports, it lacks native capabilities for real-time data ingestion, advanced visual interactions like slicers and drill-through, and complex analytics across multiple data sources. Using SharePoint alone would require extensive custom development and still miss Power BI's out-of-the-box intelligence features, making it unsuitable for this scenario.

Microsoft Forms

Why wrong: 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 wrong: 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 wrong: 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 wrong: 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 wrong: 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 wrong: 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 wrong: 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 wrong: 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 wrong: 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.

Microsoft Excel

Why wrong: Excel can create charts from list data, but it lacks native web-publishing with live sync from Microsoft Lists; sharing requires manual file uploads or static exports, so the automatic, interactive web link requirement is unmet. It is tempting because Excel excels at building detailed pipeline charts and calculating win probabilities locally, and would be correct if the manager only needed a static report or a shared workbook without live web interactivity.

Microsoft Forms

Why wrong: Microsoft Forms is designed solely for creating surveys, quizzes, and polls; it captures responses into an associated data table but provides no dashboarding, charting, or pipeline visualization capabilities. It cannot connect to an existing Microsoft Lists dataset as a source, nor can it publish an interactive, automatically refreshing web view of sales pipeline metrics — so it fails every functional requirement of the scenario.

Microsoft SharePoint

Why wrong: SharePoint can display Microsoft Lists data through standard list views and web parts, and it offers only basic charts such as column or pie charts with minimal interactivity. Those charts are limited to simple aggregations, lack drill-down and cross-filtering, and are not equivalent to the advanced analytical visuals and managed web publishing that Power BI provides; therefore SharePoint alone cannot satisfy the manager's need for an interactive, refreshable web dashboard.

Outlook on the web

Why wrong: 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 wrong: 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 PowerPoint

Why wrong: Microsoft PowerPoint is primarily a presentation program designed for creating slide decks for sequential, often in-person or broadcast slide shows. It does not natively produce a web-based interactive newsletter; although it can export slides as images or PDFs, it lacks the responsive web layout, embedded multimedia integration, and interactive scrolling experience that Sway provides for newsletter distribution.

Microsoft SharePoint

Why wrong: Microsoft SharePoint is a collaboration and document management platform used for building intranet sites, team sites, and content repositories. While SharePoint Pages or News can display news articles internally, it is not a focused authoring tool for creating a polished, interactive newsletter with rich multimedia; its core purpose is to store, manage, and share content within an organization, not to provide the simple card-based storytelling interface that Sway offers.

Microsoft Stream

Why wrong: Microsoft Stream is an enterprise video service designed for uploading, managing, and sharing recorded videos within an organization. It cannot create a newsletter with mixed text and images; its scope is limited to video content hosting and playback, unlike Sway which is an all-in-one authoring tool for interactive, multimedia-rich documents like monthly newsletters.

Microsoft Teams

Why wrong: Microsoft Teams is a chat-centric collaboration hub that integrates with other Microsoft 365 services, but it does not natively provide a document library, shared calendar, or threaded discussions within a single site. While Teams can display SharePoint pages and Planner tasks as tabs, the underlying storage and list structures live in the separate SharePoint site. Therefore, Teams alone lacks the required centralized workspace features described.

Microsoft Viva Engage

Why wrong: Microsoft Viva Engage, formerly Yammer, is an enterprise social network designed for company-wide conversations, communities, and executive updates, not for operational work management. It does not include a native document library with version control, a shared calendar, or structured task lists, so it cannot serve as the centralized workspace for a project team. Its primary function is to encourage discussion and knowledge sharing, not to house files and calendars.

Microsoft Planner

Why wrong: Microsoft Planner is a lightweight task management application that gives each project a board with buckets and tasks, and it allows files to be attached to individual tasks, but it does not provide a document library or a shared calendar for the team. The workspace in Planner is centered entirely on task assignments, progress tracking, and due dates, making it a single-purpose tool rather than a centralized collaboration workspace. Therefore, it lacks the document and calendar components required by the project team.

Word Online

Why wrong: Word Online is a rich text document editor with true co-authoring, but it lacks native ink drawing capabilities and a notebook-style structure of sections and pages. While you can paste images or use basic shapes, there is no free-form drawing canvas or tag-based note organization, so hand-drawn meeting notes are either impossible or require clunky workarounds. Its primary purpose is document creation, not quick, visual idea capture.

SharePoint Wiki

Why wrong: SharePoint Wiki pages are web-based and support collaborative editing, but they do not provide a dedicated client for ink-based drawing or the familiar notebook paradigm of tabs and pages. The wiki engine renders static HTML content, making real-time inking impractical without third-party add-ons, and its structure is better suited for persistent reference documentation rather than transient meeting sketches. This makes it less efficient for the free-form, rapid capture that a project notebook demands.

Microsoft Lists

Why wrong: Microsoft Lists is a structured data-tracking app built around rows, columns, and views, not a free-form note-taking surface. It provides no inking tools, no drawing canvas, and no natural way to record flexible narrative notes or hand-drawn diagrams. Lists are optimized for managing items like action trackers or issue logs, but they are unsuitable as a digital notebook for collaborative meeting capture with visual annotations.

Microsoft Lists

Why wrong: Microsoft Lists provides structured data tracking with customizable column types, but its interface is limited to list and board views with no built-in interactive visualization system. While you can create a task list with deadlines, it cannot produce the dynamic charts, filters, and drill-through visuals required for a real-time project dashboard without exporting or connecting to an external BI tool like Power BI.

SharePoint Online

Why wrong: SharePoint Online is a collaboration and content-management platform; although it can display lists via web parts and even include a simple 'Highlighted Content' web part for content, it lacks an integrated data model and authoring tools for charts and cross-source analytics. To get a true dashboard in SharePoint, you would embed a Power BI report, which underscores that SharePoint itself does not provide the standalone interactive dashboard experience requested.

Microsoft Forms

Why wrong: Microsoft Forms is designed solely for creating surveys, quizzes, and feedback forms; it supports no task tracking, deadline calculations, or visualization elements. Its primary output is a summary of responses in charts, but that is limited to the survey dataset and cannot connect to project tasks or display interdependent deadline metrics, making it completely unsuitable for a project-management dashboard.

Word Online

Why wrong: Word Online is a web-based word processor that focuses on document creation and co-authoring. It lacks the specialized layout templates, interactive elements, and responsive design capabilities needed for a modern newsletter. While you can embed images and links, the output is essentially a static document meant for printing or viewing as a page, not an interactive web experience optimized for mobile devices. Real-time collaboration exists, but the format constrains visual polish and multimedia integration compared to dedicated tools.

Publisher

Why wrong: Publisher is a desktop publishing application intended for print media such as brochures, flyers, and posters. It offers precise layout controls and high-resolution output, but it is not designed for digital distribution or responsive web viewing. Newsletters created in Publisher are typically exported as PDFs or printed, which does not provide the interactive, multi-device experience needed. Additionally, Publisher lacks real-time co-authoring capabilities, hindering collaborative editing across a marketing team unless files are shared and managed carefully.

OneNote

Why wrong: OneNote is a digital notebook application optimized for capturing and organizing notes, ideas, and research from multiple sources. While it supports rich text, images, and even audio/video clips, its purpose is personal knowledge management rather than creating polished, shareable newsletters. Content in OneNote is stored in section/notebook hierarchy, not as a standalone newsletter that can be presented professionally with brand styling or distributed as a single link. It lacks the design templates, presentation modes, and marketing-specific features required for a professional newsletter.

Exchange Online

Why wrong: Exchange Online is a messaging and calendaring platform built around mailboxes, not file storage. Although email can transport attachments, it lacks a shared document library with check-in/check-out, version history, real-time co-authoring, or granular permission management at the file level. Therefore, it cannot serve as a central repository for persistent team collaboration.

Microsoft Stream

Why wrong: Microsoft Stream is a video hosting and management service, specifically for uploading, organizing, and playing video content, not for storing documents or co-authoring files. While it can be embedded in SharePoint pages or Teams, it cannot maintain document versions, track changes, or facilitate simultaneous editing of Office files. Thus, it is not a central repository for document collaboration.

Microsoft Viva Engage

Why wrong: Viva Engage (formerly Yammer) is an enterprise social network for community discussions, announcements, and knowledge exchange across organizational groups. It offers conversation threads and feeds but does not provide document libraries, version history, or co-authoring capabilities for Office files. Using it as a central document repository would lack the structured content management the project team needs.

Microsoft To Do

Why wrong: Microsoft To Do is a lightweight task management application that surfaces personal and shared lists with due dates and reminders. It is built around checkbox-driven task completion, not open-ended visual collaboration. Because it lacks a shared real-time canvas, freehand inking, or sticky-note tools, it cannot support the synchronous drawing and idea capture that remote brainstorming requires.

Microsoft Forms

Why wrong: Microsoft Forms is a structured data-collection tool for creating surveys, quizzes, and polls, capturing respondent input in a backend Excel table. It does not offer an editable canvas or real-time drawing surface, and only one at a time interacts with a form, not collaboratively. Since it is designed to gather fixed responses rather than foster freeform visual exploration, it is unsuitable for brainstorming.

Microsoft Planner

Why wrong: Microsoft Planner is a project management application that organizes work into kanban boards, buckets, and tasks, with assignments and progress tracking. Its model is built on status updates and checklists, not on freehand drawing, spatial mapping, or simultaneous editing of an unbounded canvas. While it helps manage action items after a brainstorm, it cannot host the live, collaborative drawing that remote ideation requires.

Microsoft Excel

Why wrong: Microsoft Excel is a spreadsheet application optimized for data manipulation, calculation, and visualization, not for collecting user input. While you could manually design a survey layout in a worksheet and share the file, this approach lacks formal response collection, prevents anonymous or controlled distribution, and does not automatically aggregate results into charts. It is far more efficient to use Forms to gather responses and then export the data to Excel for analysis.

Microsoft Word

Why wrong: Microsoft Word is a word processing application focused on authoring and formatting written content, and it has no built-in capability to collect, track, or analyze survey responses. Sending a Word document to employees would require them to diligently fill in a table and send it back, leading to version-control issues and manual data entry. Since there is no central response repository or automatic visualization, Word is unsuitable for structured feedback collection.

Microsoft Teams

Why wrong: Microsoft Teams is a collaboration platform for chat, meetings, and file sharing, not a survey authoring tool. The built-in polling feature in Teams meetings is limited to simple multiple-choice questions and cannot support the rich question types, branching, or anonymous response options that a full employee feedback survey requires. For this scenario, the HR manager should use Microsoft Forms and can optionally attach it as a tab in a Teams channel for convenient employee access.

Microsoft Forms and Microsoft Power Automate

Why wrong: 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 wrong: 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 wrong: 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 wrong: 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 wrong: 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 wrong: 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 Word

Why wrong: Microsoft Word is a word-processing application designed for creating and editing text-based documents, not for managing structured numerical data. It lacks a native formula engine for financial calculations like budget modeling, and while it can insert tables, those tables cannot perform live computations or generate dynamic charts. Co-authoring in Word edits text and layout, not interdependent financial cells, so it would be inefficient and error-prone for a team of analysts building a budget collaboratively.

Microsoft PowerPoint

Why wrong: Microsoft PowerPoint is a presentation program intended for creating slideshows and visual narratives, not for performing calculations or co-authoring data models. Although users can embed Excel charts or paste static tables, PowerPoint does not have a formula engine, and any embedded data is typically linked back to an external Excel file. Collaborative editing in PowerPoint focuses on slide content and design, not on iterating live financial figures, making it unsuitable as the primary tool for budget modeling.

Microsoft OneNote

Why wrong: Microsoft OneNote is a digital notebook designed for free-form note-taking, brainstorming, and information capture across text, images, and audio. It lacks a spreadsheet engine, so it cannot compute formulas, cross-reference cells, generate charts, or enforce data validation for financial calculations. While OneNote supports co-authoring and can store snippets from Excel, it treats them as static copies rather than live data objects, giving analysts no way to collaboratively build and interact with a budget model.