MS-102 Deploy and manage a Microsoft 365 tenant 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.

• ✓

  The destination site collection or OneDrive must already exist in the target tenant.

  Why this is correct

  The destination site collection or OneDrive container must be provisioned and exist in the target tenant before the migration runs. Content is copied into an existing container; neither SharePoint nor OneDrive migration creates the target site automatically. For OneDrive, the destination user must have a licensed OneDrive site, and for SharePoint the target site collection must already be created in the appropriate location.

• ✓

  Cross-tenant trust must be established or a third-party migration tool must be used.

  Why this is correct

  Native tenant-to-tenant migration requires a cross-tenant trust relationship configured in Entra ID so the source and target tenants can authenticate each other for content transfer. If no trust is established, the alternative is to use a third-party migration product that operates with its own connectors and agents, bypassing the built-in federation. Without either mechanism, the destination tenant cannot securely accept the migrated content.

• ✗

  The source user performing the migration must be a global admin in the target tenant.

  Why it's wrong here

  The user who initiates the migration does not need the Global Administrator role in the target tenant. That user primarily needs administrative permission in the source tenant to read and transfer content, while the destination-side authorization comes from the cross-tenant trust or the migration tool's credentials. Requiring the source user to be a global admin in the target would violate least-privilege administration and is not a stated prerequisite.

• ✓

  The target tenant must have an active Microsoft 365 subscription.

  Why this is correct

  The target tenant must have an active Microsoft 365 subscription with the necessary SharePoint and OneDrive service plans and licenses assigned to destination users. Without licensed capacity, the destination container may not be provisioned or writable, and the migration job will fail. The source tenant's subscription is irrelevant once content moves, so the target billing entity is the one that must be valid.

• ✗

  Both tenants must have at least one user with PowerShell access.

  Why it's wrong here

  PowerShell access is not a required condition for tenant-to-tenant migration. Microsoft's native experience is administered through the Microsoft 365 admin center or Graph-based tools, and many third-party tools are web-based with their own consoles. What matters is the ability to authenticate with the necessary admin permissions and credentials, not whether either tenant has a user with a PowerShell console. The premise incorrectly turns an administrative convenience into a hard prerequisite.

Go deeper

Related to this question