MS-102 Deploy and manage a Microsoft 365 tenant Practice Question
A company has recently acquired a smaller organization and needs to consolidate both Microsoft 365 tenants. They want to minimize user disruption and retain existing email addresses. Which approach should they use?
⚠ Common exam trap
Watch out — candidates often confuse cross-tenant mailbox migration with federation trust or hybrid deployment, assuming that any inter-tenant connectivity solution can consolidate mailboxes, but only the cross-tenant migration feature directly moves mailbox data while preserving email addresses.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Perform a cross-tenant mailbox migration
Cross-tenant mailbox migration allows you to move mailboxes between two Microsoft 365 tenants while preserving the users' existing email addresses and minimizing disruption. This approach uses the Microsoft 365 native migration capabilities, specifically the cross-tenant mailbox migration feature, which supports moving mailboxes with their primary SMTP addresses and associated data without requiring on-premises Exchange Server.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Configure a hybrid deployment with Exchange Server
Why it's wrong here
A hybrid deployment with Exchange Server is designed to connect an on-premises Exchange organization to Microsoft 365, not to connect two separate Microsoft 365 tenants. It is fundamentally a migration path for on-premises mailboxes into the cloud, and it does not provide any mechanism to move mailbox data between cloud tenants. Implementing hybrid would require you to route mail through an on-premises server, add no value for a tenant-to-tenant consolidation, and leave the acquired tenant's mailboxes completely untouched.
- ✓
Perform a cross-tenant mailbox migration
Why this is correct
Cross-tenant mailbox migration is the correct approach because it uses the Cross-Tenant migration API or Enable-CrossTenantMailboxMigration cmdlets to move mailbox content, settings, and sometimes Office 365 groups between two AAD tenants. This process preserves the mailbox's ExchangeGuid, is silent to end users, and allows for redirection of the primary SMTP address so email continues to arrive without interruption. It is the only option that both consolidates data and retains user identity while minimizing disruption.
- ✗
Delete all users from the acquired tenant and recreate them in the parent tenant
Why it's wrong here
Deleting users from the acquired tenant and re-creating them in the parent tenant is a destructive, manual process that permanently removes all mailbox data, OneDrive files, Teams, and Exchange archives. User accounts that are re-created will not have the same object ID or immutable ID, breaking any B2B applications, licenses, or hybrid identity references that depended on the original accounts. This approach forces users to generate new passwords, re-enroll in MFA, and lose access to historical records, which is neither a migration nor a consolidation but a total loss of state.
- ✗
Set up a federation trust between the tenants
Why it's wrong here
A federation trust between tenants, such as setting up an organization relationship or Microsoft Entra ID federation, only enables single sign-on and shared calendar/free/busy or book-access across tenant boundaries. It does not move one byte of mailbox data, does not change the user's home tenant, and does not consolidate licensing or management into the parent tenant. Users still live in two separate directories with two separate mailboxes, so the parent tenant's goal of unifying the organization is not achieved.
Go deeper
Related to this question
Learn chapter
Tenant-Wide Settings and Org Profile
Key term
Microsoft 365
Microsoft 365 is a subscription-based cloud service from Microsoft that combines productivity tools like Office apps with security, device management, and online storage.
Key term
Mailbox
A mailbox is a storage location on a mail server where incoming and outgoing email messages are kept for a user or group.
About these practice questions
One of 712 original MS-102 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This MS-102 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the MS-102 exam.