Free MS-102 practice test: 30 questions with answers

Alert policies in Defender for Office 365 notify administrators of suspicious or malicious email activity. Printed logs, calendar reminders, and screenshots do not provide timely alerts.

Threat explorer and email threat reports identify targeted users and attack patterns. Birthday lists, printer reports, and room bookings are unrelated.

Safe Links checks URLs at the time of click, which protects users even after delivery. Printed warnings, longer passwords, and disabling links do not provide click-time protection.

Threat and vulnerability management ranks vulnerable devices and critical issues, which guides patch priorities. Printer lists, logos, and holiday calendars are unrelated.

Mail flow rules or transport policies can block automatic external forwarding. Allowing all forwarding, deleting email, and relying on user care do not enforce the restriction.

External access settings control which external domains users can communicate with in Teams. Wallpapers, icon colours, and site logos do not control external communication.

Restricting sharing to approved domains limits external access. Public sites, open links, and removing owners do not control access appropriately.

Verifying the partner and adding it to an allowed list fixes false positives appropriately. Disabling filtering exposes users to threats, changing domains is unrealistic, and deleting contacts does not change filtering.

A retention label with a seven-year period and deletion action enforces the requirement. Sensitivity labels hide or protect content rather than retaining it, printed copies are unmanaged, and one-year deletion violates the requirement.

DLP policies detect sensitive information types such as card numbers and block or warn on sharing. Wall signs, blanket blocking, and handbooks are not enforcement.

eDiscovery searches and exports relevant content across mailboxes for legal matters. Teams chat alone, printer queues, and calendars do not support cross-mailbox legal search.

DLP policies can detect and block sensitive data going to personal accounts. Reminder emails rely on people, printing is not a control, and disabling all email is disproportionate.

Microsoft Entra Connect with password hash sync or pass-through authentication keeps credentials aligned. Separate passwords, printed credentials, and disabled synchronization do not meet the requirement.

Enterprise application single sign-on uses the corporate identity for the SaaS app. Shared logins, printed cards, and public passwords are insecure.

Conditional access can combine location and MFA conditions for an application. Shared passwords, printed rules, and calendar reminders do not enforce access.

Guest invitations with team membership manage external access in a governed way. Creating internal accounts with partner passwords, shared owner passwords, and public teams are unsafe.

Windows Autopilot configures devices at first use and joins them to Microsoft Entra ID. Manual imaging, printed instructions, and self-configuration are slower and inconsistent.

Enrolment restrictions can block personal devices by ownership and platform. Wallpapers, screen savers, and printer quotas do not control enrolment.

Conditional access can use compliance state to block access. Compliance state can be informational only if configured that way, but deletion of devices or email is not an automatic result.

Required assignments install apps automatically on targeted devices. Available assignments depend on users, messages request action, and emailed installers are manual.

Domain verification through DNS proves ownership, and the email records (MX, SPF, DKIM, DMARC) are needed for mail flow. Hardware, turning off email, and name changes are not required steps.

The service health dashboard shows incidents and advisories for Microsoft 365 services. Newspapers, team calendars, and blogs are not authoritative service status sources.

Workload-specific admin roles give only the permissions required. Global Administrator and shared passwords grant far more access, and no roles cannot manage the workloads.

Managed deployment with a configured update channel keeps installations consistent and supportable. Self-downloads, email installers, and free choice cause drift.

Group-based licensing with dynamic department groups assigns licenses automatically and consistently. Manual daily assignment, blanket licensing, and self-purchase waste money or create gaps.

Converting to a shared mailbox and granting access preserves the content and gives controlled access. Sharing passwords, immediate deletion, and public folders are unsafe or destructive.

A validated CSV bulk import creates accounts efficiently and accurately. Manual creation is slow, shared accounts remove accountability, and self-created accounts with arbitrary names lack governance.

Checking service health first reveals whether the problem is a platform incident rather than a local fault. Wallpapers, printer paper sizes, and birthdays are unrelated.

Service health alerts and notifications inform administrators promptly. Calendar reminders, printed sheets, and weekly manual checks are too slow for incidents.

Usage reports show active use of apps and services. Guesses from licence counts, coffee orders, and printer reports do not measure usage.