MS-900 Describe Microsoft 365 apps and services Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Microsoft Dataverse

  Why this is correct

  Microsoft Dataverse is the correct choice because it serves as the enterprise-grade data platform beneath the Power Platform, providing relational tables, rich metadata, security roles, and built-in business rules that are essential for a custom inventory-tracking app. It supports calculated columns, rollup fields, and relationships between products, warehouses, and stock transactions — capabilities that go beyond simple file storage. Dataverse integrates natively with Power Apps and Power Automate, enabling low-code app logic without requiring a custom database. Because it offers row-level security and auditing, it satisfies compliance and scalability needs for multi-user business applications.

• ✗

  Microsoft SharePoint Online list

  Why it's wrong here

  A SharePoint Online list can store inventory rows and even surface a basic Power Apps form, but it is designed for lightweight collaborative lists rather than relational applications. It lacks native support for foreign keys, data integrity constraints, and complex queries across related entities, making it impossible to model master-detail inventory relationships such as purchase orders and line items. SharePoint's list thresholds (5,000-item view limits) and slower connector performance become bottlenecks as inventory grows. While Dataverse offers built-in business logic and granular security, SharePoint lists require custom workarounds for even moderate application requirements.

• ✗

  Microsoft Excel Online

  Why it's wrong here

  Excel Online is a spreadsheet, not a database, so it provides no relational schema enforcement, no true concurrent transaction management, and no granular row-level security — multiple users can overwrite inventory data simultaneously. Power Apps can consume Excel via connectors, but updates require one row at a time and there is no way to enforce referential integrity or business validation rules. Excel also lacks server-side calculated fields, auditing, and backup/restore with application tiers, making it acceptable for prototyping but unsuitable for a production inventory tracking system. Its use case ends where multi-user, real-time transaction integrity begins.

• ✗

  Microsoft Forms

  Why it's wrong here

  Microsoft Forms is designed for collecting survey responses, quiz answers, and simple feedback, not for emulating a relational data store needed by a custom inventory application. Each response is written to a plain output (often an Excel sheet) with no structured table schema, no relationships, and no business logic layer to validate stock quantities or integrate with inventory workflows. While Forms supports branching and basic validation, it cannot model inventory items, suppliers, or stock movements, nor can it provide the retrieval and update functions a business app requires. It therefore serves as a data-entry front end only if paired with separate, more robust storage like Dataverse.

Go deeper

Related to this question