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.

• ✓

  Create a SharePoint Online document library with versioning and enable offline sync.

  Why this is correct

  A SharePoint Online document library is purpose-built for centralized policy management: it stores files in a secure, standards-based library with configurable major/minor versioning that retains a complete history of each change. Enabling offline sync via the OneDrive sync client or SharePoint mobile app ensures staff can access the latest approved versions even without connectivity. Because the library is a single source of truth in the Microsoft 365 Business Basic tenant, it meets both the version-control and offline-access requirements directly.

• ✗

  Store documents in Exchange Online mailboxes as attachments.

  Why it's wrong here

  Storing documents in Exchange Online mailboxes as attachments treats email as a file repository, which it is not. Each email creates a separate copy of the attachment, so there is no central source of truth, no shared version history, and no granular permissions after the message is sent. Compliance and retention become impractical because policy files are scattered across individual mailboxes, message limits (typically 35 MB) constrain modern policy documents, and offline access depends on each recipient's mail client rather than a managed document store.

• ✗

  Create a Microsoft Teams team with a channel for policies and use the Files tab.

  Why it's wrong here

  A Microsoft Teams channel's Files tab is backed by a SharePoint document library, so it does offer versioning and offline sync; however, it is scoped to that specific team and channel, not to the organization as a central repository. Access is controlled by team membership, and deleting or archiving the team removes or hides the associated policy files, making it fragile for long-lived corporate policies. Additionally, policies stored in a channel are often intermingled with conversational files and drafts, so the repository lacks the dedicated retention, approval workflow, and metadata governance a standalone SharePoint library provides.

• ✗

  Use OneDrive for Business shared folders for each policy document.

  Why it's wrong here

  OneDrive for Business shared folders lack offline access synchronisation for all staff across mobile devices unless each user manually syncs individual folders, which fails the centralised, always-available repository requirement. This option is tempting because OneDrive excels at personal file storage and sharing individual documents with specific colleagues, making it a correct choice for ad-hoc collaboration on a single policy draft rather than a permanent, organisation-wide policy library.

Go deeper

Related to this question