Instiq
Chapter 5 · Optimize endpoint operations·v1.0.0·Updated 6/30/2026·~12 min

What's changed: Created MD-102 Chapter 5 (domain: Optimize endpoint operations). Automate management tasks (PowerShell/Microsoft Graph, custom compliance, Security Copilot agents in Intune), monitor/optimize health (Endpoint Analytics device health scores/startup performance/application reliability, proactive remediations detection/remediation scripts), and reporting/alerts (reporting/workbooks/dashboards/export, tenant health/service health dashboard/message center, alerts and notifications compliance drift/enrollment failures/configuration conflicts). This completes the MD-102 textbook: all 5 chapters / 13 sections.

5.2Monitor and optimize health

Key points

Understand Endpoint Analytics (device health scores, startup performance, application reliability) and proactive remediations (detection/remediation scripts).

Make endpoint performance and reliability visible, and auto-remediate common issues.

5.2.1Endpoint Analytics

Endpoint Analytics surfaces device health scores, startup performance, app startup performance, restart frequency, and application reliability metrics to make endpoint performance/reliability and user experience visible. This identifies slow startups or crash-prone configs and prioritizes improvements. Endpoint Analytics’ role is "scores and visibility"

5.2.2Proactive remediations

Proactive remediations pair a detection script with a remediation script to automatically detect and fix common issues on devices (e.g., restart a stopped service). Run them on a schedule to check periodically and fix before users notice. Versus Endpoint Analytics (visibility), proactive remediations’ role is "detect-and-fix automation"

Exam point

Cues: "score and visualize startup/restart frequency/app reliability" = Endpoint Analytics. "detection script + remediation script to auto-fix common issues" = proactive remediations. "device health scores" = Endpoint Analytics.

Warning

Watch the mix-ups: (1) Endpoint Analytics (scoring/visibility) vs proactive remediations (detect+remediate scripts auto-fix). (2) Proactive remediations run on a schedule. (3) These are monitoring/optimization—distinct from reporting and alerts.

Diagram: Endpoint Analytics visualizes endpoint performance/reliability and user experience via device health scores, startup performance, application reliability; proactive remediations pair a detection script with a remediation script to auto-detect and fix common issues on a schedule (Analytics = visualize, remediations = detect-and-fix — distinct roles).
Visualize vs auto-fix

5.2.3Section summary

  • Endpoint Analytics visualizes device health scores/startup performance/app reliability
  • Proactive remediations auto-fix common issues with detection + remediation scripts
  • Proactive remediations run on a schedule for periodic checks

Sign in to track progress — Log in.

Quick check

(just a quick review)

Q1. You want to visualize performance/reliability scores like slow startup and app crash trends to find improvements. Best?

Q2. You want to auto-detect and fix common issues, e.g., restart a stopped service automatically. Best?

Q3. You want to schedule remediation of common issues to fix them before users notice. Best?

Q4. What correctly distinguishes Endpoint Analytics from proactive remediations?

Q5. Which is an example of a metric Endpoint Analytics provides?

Check your understandingPractice questions for Chapter 5: Optimize endpoint operations

Keep track of your progress

The full study guide is free to read. Sign up free to practice with the question bank, track what you have read, review your mistakes, and highlight passages.