MD-102 MD-102 Skills measured July 24, 2026 Optimize endpoint operations by using automation, monitoring, and reporting Runs in your browser · no setup Original practice · Review pending

Automate an endpoint health response

Use scoped reporting evidence to target remediation and verify endpoint health.

Estimated12 min
DifficultyIntermediate
Points7
Scenario brief

A restart regression affects a subset of devices after an application update. Version 7.4.1 is a required assignment to the Pilot group only; the Broad group is due to be added next week. Build a bounded response.

Content record

Original practice · Review pending

Mapped to Microsoft MD-102 objectives · Internal validation 2026-10-06 · Original ITForMe practice mapped to published objectives; not an official exam question. A named independent subject-matter expert has not yet verified the question and answer key.

Community review →
5.1Automate endpoint-management tasks. 5.2Monitor and optimize endpoint health and performance.
Show review record and official sources

Method: Clean-room scenario and answer key checked against MD-102 objectives 5.1 and 5.2; independent SME review remains pending.

Current-profile check: 2026-09-30 · Next review due 2026-10-26

01

Inspect the evidence

Use only the information provided to complete the tasks.

Health summary

table
GroupRestart increaseApp version
Pilot+42%7.4.1
Broad+2%7.3.8
UnmanagedNo dataUnknown

If columns are offscreen, scroll sideways or focus the table and use arrow keys.

02

Complete the response

Partial credit is available for matching, ordering, and multi-select tasks.

Changes will save automatically.
01
multi select

Select the THREE safest next steps.

3 pts
Need a hint?

Evaluate each option independently against the scenario evidence instead of treating the list as one decision.

Show another hint

Choose only options that directly satisfy the prompt; being generally true is not enough.

02
ordering

Order the health response.

4 pts

Drag the rows or use the arrow buttons to reorder.

  1. 1 Confirm affected version and device scope
  2. 2 Hold the 7.4.1 assignment at Pilot so Broad is not added
  3. 3 Test remediation on a small managed group
  4. 4 Compare restart and failure measures before extending 7.4.1
Need a hint?

Identify the prerequisite that must happen first and the verification or documentation that belongs last.

Show another hint

For the middle steps, ask what must already be true before each action can safely happen.

Ready to check your work?Unanswered tasks and matches earn no points. A partial submission is scored and saved in your history.
Persistent progress

Attempt history

Every submission is retained. Starting another attempt never replaces or unlocks the previous one.

No attempts yet

Your first submitted score and detailed answer review will appear here.

Community quality control

Question or answer look wrong?

Proposals and votes help staff prioritize review. They never change the scoring key automatically.

Full review queue →
No community corrections yet

Be the first to flag unclear wording, an answer-key issue, or a source that needs another look.

Propose a correction