MD-102 - Optimize Endpoint Operations by Using Automation, Monitoring, and Reporting (13% of the exam) - Section 5.2

Monitor and optimize endpoint health with Intune reporting, Endpoint Analytics and alerts.

Implement Intune reporting with customised reports, filters, workbooks and data export, and monitor endpoint performance, reliability and user experience scores with Endpoint Analytics. Configure and schedule proactive remediation scripts, monitor tenant health and service communications, and set alert rules for compliance drift, enrollment failures and configuration conflicts.

Intune reportsEndpoint Analyticsproactive remediationsstartup performanceservice healthalert rules

Practice question for this objective

Free sampleOptimize Endpoint Operations by Using Automation, Monitoring, and Reportingmedium

Since this morning no Apple device in a tenant has been able to enrol in Microsoft Intune, while Windows enrolment continues to succeed. Before any enrolment policy is altered, an administrator must establish whether a tenant level condition accounts for the failure. Which TWO checks on the Tenant status page of the Microsoft Intune admin center address that question? Select TWO.

AReview the service health information on the Tenant status page for an active Microsoft Intune incident or advisory affecting enrolment. Correct
BCreate an alert rule for the device enrolment failure condition and name the operations mailbox as the recipient of the notification.
COpen the Endpoint Analytics device health scores and read the values reported for the Apple devices that failed to enrol today.
DReview the connector status on the Tenant status page for an Apple MDM push certificate that has passed its expiry date. Correct
EExport the device compliance report from Microsoft Intune and filter it for the Apple devices recorded in the tenant.

Tenant wide failures are diagnosed on the Tenant status page, where service health reports service incidents and connector status reports expired tokens and certificates. The Tenant status page gathers the tenant level facts that sit above any individual policy. Service health shows whether Microsoft has an open incident or advisory against Microsoft Intune, and connector status shows whether a connector or token the tenant depends on, such as the Apple MDM push certificate, has expired. A platform specific failure alongside a healthy service points at the connector, and both checks belong before an enrolment policy is changed.

Why A is correct: Service health on the Tenant status page reports the incidents and advisories Microsoft has raised against the service, so it establishes whether the failure originates in the service rather than in the tenant's own configuration.

Why B is wrong: An alert rule is a reasonable thing to hold for the future and enrolment failure is a genuine alert condition, but a rule created now watches for later occurrences and explains nothing about the failure already in progress.

Why C is wrong: Endpoint Analytics is tempting because it carries the word health, yet it scores the experience of managed Windows devices already reporting data and holds nothing about a device that never completed enrolment.

Why D is correct: Connector status on the same page reports the state of the tenant's connectors and tokens, and an expired Apple MDM push certificate stops every Apple enrolment while leaving other platforms untouched.

Why E is wrong: A compliance report describes the policy state of devices that are already enrolled, so a handset that failed to enrol has no row in it and the export cannot show why enrolment stopped.

See more MD-102 practice questions, answers explained.

Exam traps in Optimize Endpoint Operations by Using Automation, Monitoring, and Reporting

Answers that look right on this material and are not. Each one is a distractor from a different question in the MD-102 bank for this domain.

Have the detection script write its result to a log file on the device, and set the assignment schedule to run hourly.
Why it is wrong: Writing to a log file and running more often feels like better instrumentation, but the schedule only decides how often detection runs, and a file on the device is not read by the service, so the exit code still reports every device as healthy.
The restart frequency recorded for the same laptops, because the number of restarts a device performs each week is what sets its startup performance score in Endpoint Analytics.
Why it is wrong: Restart frequency is a genuine Endpoint Analytics measurement and a slow estate often restarts often, which makes this tempting, but restart counts describe how frequently devices restart rather than how long either startup phase takes, so they cannot separate the two phases.
It measures the time a device spends installing quality updates while it restarts, so a month carrying a large cumulative update lowers the reported score for that device.
Why it is wrong: Update installation time does contribute to how long some restarts feel to a user, which makes this tempting, but the score is not a measure of update installation work and is not driven by the size of a given monthly update.

Examworthy is not affiliated with or endorsed by Microsoft. Original, blueprint-aligned practice material only.