A public library system needs a new SharePoint site to hold capital-projects document sets. Which admin center should be used to provision and govern that site object at the service level?

A public library system creating a SharePoint site for capital-projects document sets provisions and governs that site object at the service level in the SharePoint admin center. SharePoint admin center is where tenant administrators create sites, view site collections, manage sharing defaults, and apply service-level governance that affects municipal document workspaces. Capital-project files belong in SharePoint sites designed for document collaboration and retention.

Exchange admin center fails by concept: Exchange manages mailboxes, distribution groups, and mail flow—not SharePoint site objects. Teams admin center fails by concept: it manages Teams-specific workloads like chat, meetings, and teams; it does not provision or govern SharePoint site objects at the service level. Microsoft 365 admin center fails because it manages tenant-wide settings, user licenses, and subscriptions rather than provisioning and governing individual SharePoint site objects.

Exam caveat: Map ‘site object’ language to SharePoint admin center. Teams may create an associated site when you create a Team, but the stem asks which admin center provisions and governs the SharePoint site at the service level—SharePoint admin center remains the correct association for site governance.

Operational check: in SharePoint admin center, create the capital-projects site (or approve a site request), set sharing and external access appropriately for library staff and contractors, assign Owners/Members/Visitors, create libraries for document sets, and verify librarians can upload and navigate project files before migrating legacy capital-project content.