Sign in
Home/Microsoft/Microsoft 365 Administrator (MS-102)/Free questions

Microsoft 365 Administrator (MS-102) — Free Practice Questions

10 free sample questions from a bank of 447, with the correct answers and explanations. No signup required — start practising right now.

1Overview - Fabrikam, Inc. is an electronics company that produces consumer products. Fabrikam has 10,000 employees worldwide. Fabrikam has a main office in London and branch offices in major cities in Europe, Asia, and the United States. Existing Environment - Active Directory Environment - The network contains an Active Directory forest named fabrikam.com. The forest contains all the identities used for user and computer authentication. Each department is represented by a top-level organizational unit (OU) that contains several child OUs for user accounts and computer accounts. All users authenticate to on-premises applications by signing in to their device by using a UPN format of [email protected]. Fabrikam does NOT plan to implement identity federation. Network Infrastructure - Each office has a high-speed connection to the Internet. Each office contains two domain controllers. All domain controllers are configured as DNS servers. The public zone for fabrikam.com is managed by an external DNS server. All users connect to an on-premises Microsoft Exchange Server 2016 organization. The users access their email by using Outlook Anywhere, Outlook on the web, or the Microsoft Outlook app for iOS. All the Exchange servers have the latest cumulative updates installed. All shared company documents are stored on a Microsoft SharePoint Server farm. Requirements - Planned Changes - Fabrikam plans to implement a Microsoft 365 Enterprise subscription and move all email and shared documents to the subscription. Fabrikam plans to implement two pilot projects: Project1: During Project1, the mailboxes of 100 users in the sales department will be moved to Microsoft 365. Project2: After the successful completion of Project1, Microsoft Teams will be enabled in Microsoft 365 for the sales department users. Fabrikam plans to create a group named UserLicenses that will manage the allocation of all Microsoft 365 bulk licenses. Technical Requirements - Fabrikam identifies the following technical requirements: All users must be able to exchange email messages successfully during Project1 by using their current email address. Users must be able to authenticate to cloud services if Active Directory becomes unavailable. A user named User1 must be able to view all DLP reports from the Microsoft Purview compliance portal. Microsoft 365 Apps for enterprise applications must be installed from a network share only. Disruptions to email access must be minimized. Application Requirements - Fabrikam identifies the following application requirements: An on-premises web application named App1 must allow users to complete their expense reports online. App1 must be available to users from the My Apps portal. The installation of feature updates for Microsoft 365 Apps for enterprise must be minimized. Security Requirements - Fabrikam identifies the following security requirements: After the planned migration to Microsoft 365, all users must continue to authenticate to their mailbox and to SharePoint sites by using their UPN. The membership of the UserLicenses group must be validated monthly. Unused user accounts must be removed from the group automatically. After the planned migration to Microsoft 365, all users must be signed in to on-premises and cloud-based applications automatically. The principle of least privilege must be used. You are evaluating the required processes for Project1. You need to recommend which DNS record must be created while adding a domain name for the project. Which DNS record should you recommend?
  • host (A)
  • host information (HINFO)
  • text (TXT)
  • pointer (PTR)
Answer: C

The short version

C — create a TXT record to verify the custom domain. Microsoft 365 requires TXT proof of ownership before Project1 mail flow.

Key concepts in this question

  • Custom domain onboarding: adding fabrikam dot com to Microsoft 365 so users keep current email addresses.
  • TXT verification: DNS text record hosting a Microsoft-supplied code proving administrative control of the domain.
  • Project1 mail flow: moving 100 sales mailboxes while preserving address continuity and minimizing disruption.
  • A versus PTR versus HINFO: host mapping, reverse lookup, and host-info records that do not prove ownership.

Why C is correct

C is correct because Microsoft 365 domain setup mandates TXT verification before Exchange Online accepts the domain for mailbox moves. Creating the TXT host with the supplied value lets Microsoft confirm control without changing mail routing prematurely. This step enables later MX and Autodiscover work while satisfying the evaluation of required processes.

Why the others are wrong

  • A. Host A maps names to IPs and does not verify domain ownership for Microsoft 365.
  • B. Host information describes CPU and OS and plays no role in domain verification.
  • D. Pointer enables reverse lookup and cannot prove forward domain control.

MS-102 exam tip

Start every domain add with TXT: ownership proof first, mail routing second.

2Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You have a Microsoft 365 E5 subscription. You create an account for a new security administrator named SecAdmin1. You need to ensure that SecAdmin1 can manage Microsoft Defender for Office 365 settings and policies for Microsoft Teams, SharePoint, and OneDrive. Solution: From the Microsoft 365 admin center, you assign SecAdmin1 the Exchange Administrator role. Does this meet the goal?
  • Yes
  • No
Answer: B

The short version

B — No, Exchange Administrator cannot manage Defender policies for Teams plus SharePoint plus OneDrive. Threat-policy scope belongs to security roles, not mailbox administration.

Key concepts in this question

  • Defender for Office 365 policies: Safe Links and Safe Attachments that protect collaboration workloads across services.
  • Exchange Administrator scope: manages mail flow, recipients, and Exchange settings, without cross-workload threat policy rights.
  • Security Administrator scope: owns threat management and Defender portal policy authoring for protected workloads.
  • Workload versus policy admin: administering Teams or SharePoint differs from managing Defender settings that apply to them.
  • Series evaluation: each solution alone must grant the full stated Defender management capability.

Why B is correct

Assigning Exchange Administrator gives mailbox control but not Defender for Office 365 policy rights that span Teams, SharePoint, and OneDrive. Those settings live in the Defender portal under security-role authority. Vendor consensus is unanimous for No because the role does not meet all requirements. Only Security Administrator or equivalent threat-management rights would satisfy the goal.

Why the others are wrong

  • A. Yes is wrong because Exchange Administrator lacks Defender cross-workload policy management authority.

MS-102 exam tip

Defender policies for Teams plus SharePoint equals Security Admin, not Exchange or Teams Admin.

3You have a Microsoft 365 subscription. You have an Azure AD tenant that contains the users shown in the following table. You configure Tenant properties as shown in the following exhibit. Which users will be contacted by Microsoft if the tenant experiences a data breach?
Microsoft 365 Administrator (MS-102) question 3Microsoft 365 Administrator (MS-102) question 3
  • User1 only
  • User2 only
  • User3 only
  • User1 and User2 only
  • User2 and User3 only
Answer: B

The short version

B — User2 only is contacted as global privacy contact for breach notice. Microsoft uses that tenant property, falling back to global admins only when empty.

Key concepts in this question

  • Tenant properties contact: global privacy contact email for personal-data inquiries and breach notifications.
  • User2 mapping: the exhibit account designated as privacy contact, distinct from other admins.
  • Fallback rule: without a listed contact, Microsoft notifies global administrators instead.
  • User1 and User3 contrast: hold other roles or no privacy designation, so they are not breach contacts here.
  • Exhibit reading: table plus tenant screenshot together identify who receives the notice.

Why B is correct

Microsoft contacts the configured global privacy contact for Azure AD data-breach matters, as quoted in vendor docs. The exhibit shows User2 in that slot, so only User2 gets the notice. Other users lack that property even if they are admins, and fallback to all globals does not trigger when a contact exists. Consensus favors B, confirming the single-contact outcome.

Why the others are wrong

  • A. User1 only misses the designated privacy contact shown as User2.
  • C. User3 only has no privacy-contact designation in the exhibit.
  • D. User1 and User2 over-notifies because User1 is not the privacy contact.
  • E. User2 and User3 over-notifies because User3 is not the privacy contact.

MS-102 exam tip

Breach contact equals global privacy contact first, global admins only when that field is blank.

4Overview - Litware, Inc. is a consulting company that has a main office in Montreal and a branch office in Seattle. Litware collaborates with a third-party company named A. Datum Corporation. Environment - On-Premises Environment - The network of Litware contains an Active Directory domain named litware.com. The domain contains three organizational units (OUs) named LitwareAdmins, Montreal Users, and Seattle Users and the users shown in the following table. The domain contains 2,000 Windows 10 Pro devices and 100 servers that run Windows Server 2019. Cloud Environment - Litware has a pilot Microsoft 365 subscription that includes Microsoft Office 365 Enterprise E3 licenses and Azure AD Premium P2 licenses. The subscription contains a verified DNS domain named litware.com. Azure AD Connect is installed and has the following configurations: • Password hash synchronization is enabled. • Synchronization is enabled for the LitwareAdmins OU only. Users are assigned the roles shown in the following table. Self-service password reset (SSPR) is enabled. The Azure AD tenant has Security defaults enabled. Problem Statements - Litware identifies the following issues: • Admin1 cannot create conditional access policies. • Admin4 receives an error when attempting to use SSPR. • Users access new Office 365 service and feature updates before the updates are reviewed by Admin2. Requirements - Planned Changes - Litware plans to implement the following changes: • Implement Microsoft Intune. • Implement Microsoft Teams. • Implement Microsoft Defender for Office 365. • Ensure that users can install Office 365 apps on their device. • Convert all the Windows 10 Pro devices to Windows 10 Enterprise ES. • Configure Azure AD Connect to sync the Montreal Users OU and the Seattle Users OU. Technical Requirements - Litware identifies the following technical requirements: • Administrators must be able to specify which version of an Office 365 desktop app will be available to users and to roll back to previous versions. • Only Admin2 must have access to new Office 365 service and feature updates before they are released to the company. • Litware users must be able to invite A. Datum users to participate in the following activities: • Join Microsoft Teams channels. • Join Microsoft Teams chats. • Access shared files. • Just in time access to critical administrative roles must be required. • Microsoft 365 incidents and advisories must be reviewed monthly. • Office 365 service status notifications must be sent to Admin2. • The principle of least privilege must be used. You need to configure Azure AD Connect to support the planned changes for the Montreal Users and Seattle Users OUs. What should you do?
Microsoft 365 Administrator (MS-102) question 4Microsoft 365 Administrator (MS-102) question 4
  • From PowerShell, run the Add-ADSyncConnectorAttributeInclusion cmdlet.
  • From the Microsoft Azure AD Connect wizard, select Manage federation.
  • From the Microsoft Azure AD Connect wizard, select Customize synchronization options.
  • From PowerShell, run the Start-ADSyncSyncCycle cmdlet.
Answer: C

The short version

C — Customize synchronization options adds Montreal plus Seattle OUs to sync. The wizard scope controls which OUs flow to the tenant.

Key concepts in this question

  • Azure AD Connect scope: OU filtering decides which on-premises objects synchronize to the cloud.
  • Current state: only LitwareAdmins OU syncs, leaving Montreal and Seattle users unsynced.
  • Customize synchronization options: wizard path to edit domains, OUs, and optional features after initial install.
  • Manage federation contrast: changes sign-in method, not the set of synced OUs.
  • Cmdlet traps: attribute inclusion and sync-cycle cmdlets tune or trigger sync without changing OU scope selection.

Why C is correct

Expanding sync from one OU to two additional OUs requires re-entering the wizard and updating OU filtering. Customize synchronization options is the documented entry point for that scope change. Vendor consensus is unanimous for C. Managing federation alters auth, while the listed cmdlets do not reselect OUs, so they cannot satisfy the planned change.

Why the others are wrong

  • A. Attribute inclusion cmdlet filters attributes, not which OUs are included in sync.
  • B. Manage federation switches sign-in topology without adding OUs to synchronization.
  • D. Start sync cycle triggers a run with existing scope, leaving Montreal and Seattle still excluded.

MS-102 exam tip

Add OUs to sync equals rerun Connect plus Customize synchronization options, not federation or manual cycle.

5You have a Microsoft 365 subscription. Your company has a customer ID associated to each customer. The customer IDs contain 10 numbers followed by 10 characters. The following is a sample customer ID: 12-456-7890-abc-de-fghij. You plan to create a data loss prevention (DLP) policy that will detect messages containing customer IDs. What should you create to ensure that the DLP policy can detect the customer IDs?
  • a PowerShell script
  • a sensitivity label
  • a sensitive information type
  • a retention label
Answer: C

The short version

C — create a sensitive information type for customer-ID detection. Custom patterns plus validation let DLP find the 10-plus-10 format.

Key concepts in this question

  • Sensitive information type: reusable entity combining regex, keywords, and confidence logic for content matching.
  • DLP policy: rule set scanning Exchange, SharePoint, and Teams content for sensitive entities and applying actions.
  • Custom pattern need: 10 numbers followed by 10 characters requires a tailored expression, not a built-in type.
  • Labels versus types: sensitivity and retention labels classify and govern, while information types detect.

Why C is correct

C is correct because DLP detection of a bespoke customer ID depends on defining a sensitive information type with regex for the numeric and character segments. That type can then be referenced by the DLP policy to flag messages containing matches with appropriate confidence. Scripts, sensitivity labels, and retention labels do not provide content-detection signatures.

Why the others are wrong

  • A. PowerShell script automates administration but does not define DLP content detection.
  • B. Sensitivity label classifies and protects already-found content rather than detecting patterns.
  • D. Retention label governs lifecycle and disposal, not pattern-based DLP identification.

MS-102 exam tip

Detect with types, protect with labels: custom ID patterns always mean create a sensitive information type.

6You have a Microsoft 365 E5 subscription. You define a retention label that has the following settings: Retention period: 7 years - Start the retention period based on: When items were created You need to prevent the removal of the label once the label is applied to a file. What should you select in the retention label settings?
  • Retain items forever or for a specific period
  • Mark items as a regulatory record
  • Mark items as a record
  • Retain items even if users delete
Answer: B

The short version

B — mark items as a regulatory record to block label removal. It locks the label so even admins cannot remove it after application.

Key concepts in this question

  • Retention label: 7-year keep control starting at creation for compliance preservation.
  • Record versus regulatory record: record blocks edits and deletion by users, while regulatory record also blocks admin label removal.
  • Label removal risk: users or admins unassigning the label to bypass retention if not locked.
  • Prevent removal requirement: strongest lock needed once the file is labeled.

Why B is correct

B is correct because regulatory record is the strictest declaration, preventing anyone including administrators from removing the label or altering the item. Standard retain settings preserve content but still permit label changes that would defeat governance. Record status helps but still allows admin removal, so only regulatory record meets the prevent-removal wording.

Why the others are wrong

  • A. Retain for a period preserves items but does not lock the label against removal.
  • C. Mark as a record blocks user edits yet still permits admin label removal.
  • D. Retain even if users delete protects against deletion, not against label unassignment.

MS-102 exam tip

Need irremovable labels: choose regulatory record when even admins must be blocked.

7Overview - Fabrikam, Inc. is an electronics company that produces consumer products. Fabrikam has 10,000 employees worldwide. Fabrikam has a main office in London and branch offices in major cities in Europe, Asia, and the United States. Existing Environment - Active Directory Environment - The network contains an Active Directory forest named fabrikam.com. The forest contains all the identities used for user and computer authentication. Each department is represented by a top-level organizational unit (OU) that contains several child OUs for user accounts and computer accounts. All users authenticate to on-premises applications by signing in to their device by using a UPN format of [email protected]. Fabrikam does NOT plan to implement identity federation. Network Infrastructure - Each office has a high-speed connection to the Internet. Each office contains two domain controllers. All domain controllers are configured as DNS servers. The public zone for fabrikam.com is managed by an external DNS server. All users connect to an on-premises Microsoft Exchange Server 2016 organization. The users access their email by using Outlook Anywhere, Outlook on the web, or the Microsoft Outlook app for iOS. All the Exchange servers have the latest cumulative updates installed. All shared company documents are stored on a Microsoft SharePoint Server farm. Requirements - Planned Changes - Fabrikam plans to implement a Microsoft 365 Enterprise subscription and move all email and shared documents to the subscription. Fabrikam plans to implement two pilot projects: • Project1: During Project1, the mailboxes of 100 users in the sales department will be moved to Microsoft 365. • Project2: After the successful completion of Project1, Microsoft Teams will be enabled in Microsoft 365 for the sales department users. Fabrikam plans to create a group named UserLicenses that will manage the allocation of all Microsoft 365 bulk licenses. Technical Requirements - Fabrikam identifies the following technical requirements: • All users must be able to exchange email messages successfully during Project1 by using their current email address. • Users must be able to authenticate to cloud services if Active Directory becomes unavailable. • A user named User1 must be able to view all DLP reports from the Microsoft Purview compliance portal. • Microsoft 365 Apps for enterprise applications must be installed from a network share only. • Disruptions to email access must be minimized. Application Requirements - Fabrikam identifies the following application requirements: • An on-premises web application named App1 must allow users to complete their expense reports online. App1 must be available to users from the My Apps portal. • The installation of feature updates for Microsoft 365 Apps for enterprise must be minimized. Security Requirements - Fabrikam identifies the following security requirements: • After the planned migration to Microsoft 365, all users must continue to authenticate to their mailbox and to SharePoint sites by using their UPN. • The membership of the UserLicenses group must be validated monthly. Unused user accounts must be removed from the group automatically. • After the planned migration to Microsoft 365, all users must be signed in to on-premises and cloud-based applications automatically. • The principle of least privilege must be used. You are evaluating the required processes for Project1. You need to recommend which DNS record must be created while adding a domain name for the project. Which DNS record should you recommend?
  • host (A)
  • alias (CNAME)
  • text (TXT)
  • host (AAAA)
Answer: C

The short version

C — Text TXT record proves domain ownership for Microsoft 365 onboarding. Verification TXT or MX at the public DNS host confirms control before services move.

Key concepts in this question

  • Domain verification: Microsoft requires a DNS proof that the tenant admin controls fabrikam.com.
  • TXT mechanism: adding the provided TXT value at the host proves ownership without altering mail or web traffic.
  • Host A and AAAA contrast: map names to IPv4 or IPv6 addresses for connectivity, not ownership proof.
  • CNAME contrast: aliases one name to another for service routing, not the standard verification token.
  • Pilot context: Project1 mailbox moves and Teams enablement both depend on verified domain and licenses.

Why C is correct

Microsoft 365 domain setup instructs admins to add a TXT record with a generated value at any DNS host, then verifies it before allowing mailbox or Teams use. Vendor prose cites TXT or MX as valid verification, with TXT preferred when mail must stay on-premises during pilot. Host and alias records provide no verification token, so they cannot complete the step. Settled key C therefore matches official onboarding.

Why the others are wrong

  • A. Host A creates IPv4 resolution, but carries no Microsoft verification value.
  • B. Alias CNAME routes service names without proving domain control to Microsoft.
  • D. Host AAAA creates IPv6 resolution, unrelated to ownership verification.

MS-102 exam tip

Verify Microsoft 365 domain equals add TXT first, MX only when ready to move mail flow.

8Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. Your network contains an on-premises Active Directory domain named contoso.com. The domain contains the users shown in the following table. The domain syncs to an Azure AD tenant named contoso.com as shown in the exhibit. (Click the Exhibit tab.) User2 fails to authenticate to Azure AD when signing in as [email protected]. You need to ensure that User2 can access the resources in Azure AD. Solution: From the on-premises Active Directory domain, you assign User2 the Allow logon locally user right. You instruct User2 to sign in as [email protected]. Does this meet the goal?
Microsoft 365 Administrator (MS-102) question 8Microsoft 365 Administrator (MS-102) question 8
  • Yes
  • No
Answer: B

The short version

B — No, local logon rights do not fix a UPN domain mismatch. User2 needs the fabrikam domain added as a custom domain, not workstation rights.

Key concepts in this question

  • On-premises UPN versus Azure AD UPN: sync matches authenticated domain suffixes to verified tenant domains.
  • Custom domain requirement: fabrikam dot com must be verified in Microsoft 365 before user2 at fabrikam dot com can sign in.
  • Contoso versus Fabrikam mismatch: domain is contoso dot com on premises, so fabrikam suffix is unrecognized without registration.
  • Allow logon locally: workstation privilege unrelated to cloud identity routing and token issuance.

Why B is correct

B is correct because Azure AD authentication fails when the UPN suffix has no verified custom domain backing it. Granting Allow logon locally affects only interactive logon to a local machine and does not create the cloud domain trust. The goal therefore remains unmet until the alternate domain is added and verified, warranting a No answer.

Why the others are wrong

  • A. Yes is wrong because local rights cannot substitute for custom-domain verification in Azure AD.

MS-102 exam tip

Treat UPN failures as domain issues: unknown suffix means add and verify the custom domain first.

9Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You have a Microsoft 365 E5 subscription. You create an account for a new security administrator named SecAdmin1. You need to ensure that SecAdmin1 can manage Microsoft Defender for Office 365 settings and policies for Microsoft Teams, SharePoint, and OneDrive. Solution: From the Microsoft 365 admin center, you assign SecAdmin1 the SharePoint Administrator role. Does this meet the goal?
  • Yes
  • No
Answer: B

The short version

B — No, SharePoint Admin cannot manage Defender for Office 365 policies. Service administration does not grant security-policy control.

Key concepts in this question

  • SharePoint Administrator role: manages SharePoint sites, sharing, and service settings without security-center rights.
  • Defender for Office 365: threat policies for Teams, SharePoint, and OneDrive managed in the Defender portal.
  • Security Administrator role: grants Defender, alert, and threat-policy management across workloads.
  • Least-privilege check: verifying whether the assigned role actually includes the requested policy scope.

Why B is correct

B is correct because SharePoint Administrator centers on collaboration service management and lacks Defender policy permissions. Managing Safe Attachments, Safe Links, and Teams plus SharePoint threat settings requires security-role grants. Assigning only SharePoint Admin therefore leaves SecAdmin1 without the needed Defender authority, so the solution fails.

Why the others are wrong

  • A. Yes is wrong because SharePoint Admin scope excludes Defender for Office 365 policy management.

MS-102 exam tip

Separate service admin from security admin: SharePoint role manages sites, Security role manages Defender policies.

10Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You have a Microsoft 365 E5 subscription. You create an account for a new security administrator named SecAdmin1. You need to ensure that SecAdmin1 can manage Microsoft Defender for Office 365 settings and policies for Microsoft Teams, SharePoint, and OneDrive. Solution: From the Microsoft Entra admin center, you assign SecAdmin1 the Security Administrator role. Does this meet the goal?
  • Yes
  • No
Answer: A

The short version

A — Yes, Security Administrator covers Defender policies for Teams plus SharePoint plus OneDrive. Defender portal policies fall under security-role scope.

Key concepts in this question

  • Security Administrator role: Entra role authorizing threat management, alert handling, and Defender policy control.
  • Defender for Office 365 scope: Safe Links and Safe Attachments policies that apply to Teams, SharePoint, and OneDrive content.
  • Policy versus workload admin: managing threat settings in Defender differs from administering the workload services themselves.
  • Entra assignment path: granting the role in Entra admin center confers Defender portal rights.

Why A is correct

A is correct because Security Administrator includes rights to create and manage Defender for Office 365 settings that protect collaboration workloads. The requirement is to manage threat policies which apply to Teams, SharePoint, and OneDrive, not to administer those services directly. Assigning the Security Administrator role therefore satisfies the stated Defender management goal.

Why the others are wrong

  • B. No is wrong because Security Administrator does include Defender for Office 365 policy authority.

MS-102 exam tip

Read which-apply-to carefully: Security Admin manages Defender policies that protect Teams and SharePoint content.

Want the full bank of 447 questions for Microsoft 365 Administrator (MS-102)? See all practice exams.