Endpoint Administrator MD-102 Practice Test 87
Question 860
Five Endpoint Analytics pilot devices were enrolled but only two restarted. The dashboard says insufficient data. The administrator interprets the absent score as a zero productivity score. What is the more likely explanation?
- A missing score necessarily means every app crashed during startup
- The first two reporting devices produced a high startup score and therefore all other devices should be counted as zero
- There is insufficient eligible startup telemetry; the scoring prerequisite is not met just because devices are enrolled
- Windows Update feature versions automatically determine the organization’s analytics score
Explanation
Correct Answer
C:Endpoint Analytics distinguishes missing data from poor performance and needs enough reporting devices and startup events.
Incorrect Answers
A:Application crashes are a different signal and absent telemetry is not a numeric zero score.
B:An insufficient-data cohort cannot be filled by inventing values for endpoints without startup telemetry.
D:Installed OS version alone does not create a startup score without device performance data.
Question 861
After waiting for telemetry collection, how should the analyst validate that startup reporting is now genuinely usable?
- Compare the dashboard title before and after enabling collection
- Export an empty score report and assign a value of zero to blank entries
- Review a security baseline policy description without checking reporting devices
- Check eligible reporting-device counts and fresh startup performance metrics from restarted pilot laptops rather than treating Insufficient data as a low score
Explanation
Correct Answer
D:This confirms real collection coverage and usable performance measurements before ranking devices or recommending fleet-wide changes.
Incorrect Answers
A:A title change is not evidence of performance events.
B:Substituting zero for unavailable measurements fabricates performance deterioration.
C:Policy metadata is not evidence that Endpoint Analytics received startup events.
Question 862
An IT team creates an Intune Remediations package whose detection script finds a missing required registry value and writes a warning, but returns exit code 0. The remediation script never runs. What should detection do when the issue exists?
- Return exit code 1 from the detection script when the targeted fault is detected
- Always return exit 0 because any output means failure
- Put a reboot command inside the detection script to trigger the package
- Print the word FAIL from detection and exit 0 while expecting the remediation engine to parse the text
Explanation
Correct Answer
A:Microsoft documents that a remediation script runs only when detection exits with code 1; console output alone does not trigger the fix.
Incorrect Answers
B:Exit 0 signals no remediation need even when warning text was written.
C:Microsoft advises against reboot commands in Remediations scripts and a reboot does not replace the return-code contract.
D:The Remediations engine triggers repair based on exit code 1, not a warning string.
Question 863
A Remediations package has valid assignments, but no fixes run on devices that detection identifies as failing. Script logs show output “Missing registry entry” followed by exit 0. Which contract was violated?
- A compliance policy grace period must be shortened to five minutes
- Treat a detection script’s nonempty warning output as a substitute for exit code 1
- For a detected issue the script must exit 1, not merely print a failure message and exit successfully
- The script must include a clear-text administrator password
Explanation
Correct Answer
C:The Intune Remediations engine uses the exit code to decide whether to invoke the second script, regardless of log text.
Incorrect Answers
A:Compliance marking does not control whether the Remediations detection script invokes its paired repair.
B:The engine does not infer remediation need from stdout when the script exits 0.
D:Embedding credentials is unsafe and unrelated to the required return code.
Question 864
The detection script now exits 1 for a missing registry value and 0 when present. What test verifies the Remediations workflow without an endless modification loop?
- The remediation script executes repeatedly after every successful check returning exit 0
- The package name appears in Intune with no local execution evidence
- A Windows laptop reports a high app-reliability score without a registry check
- On one controlled pilot, missing value yields exit 1 and remediation runs; a second detection after repair exits 0 and no second fix is invoked
Explanation
Correct Answer
D:The two-stage check demonstrates detection/remediation cause and convergence, not just script deployment.
Incorrect Answers
A:Repeated runs after success indicate the trigger contract or detection logic is still wrong.
B:Administrative availability does not prove detection and remediation control flow.
C:General analytics scoring cannot validate the specific detection/fix script behavior.
Question 865
After an application upgrade, Advanced Analytics detects a rise in app crashes for one device-model/driver combination. The app team wants to roll back on all hardware immediately. What is the most discriminating first action?
- Remove the app from every device without comparing affected and unaffected cohorts.
- Dismiss the issue because no Windows Stop Error occurred.
- Inspect the anomaly’s correlated app version, driver, device model and timeline, then pilot a targeted mitigation on the affected cohort.
- Roll back the application on unaffected hardware before comparing the correlated driver-and-model cohort with a matched control.
Explanation
Correct Answer
C:The report identifies correlated groups and at-risk populations; testing the suspected combination avoids treating all models identically.
Incorrect Answers
A:A fleetwide removal is not justified by a model-specific correlation.
B:App crashes and hangs are independently tracked anomalies.
D:Changing unaffected cohorts first obscures the suspected cause and increases disruption before a targeted mitigation tests the observed app/driver correlation.
Question 866
The Intune anomaly report shows a new crash spike on devices running app v7 with driver D. Other devices with v7 and driver E, and devices with v6 and driver D, remain stable over the same interval. Which hypothesis best fits the observed correlation for a targeted first test?
- An interaction between the new app build and driver D affecting the correlated laptop cohort.
- App v7 alone is unstable on every driver, so a tenant-wide application rollback is the first conclusion.
- Driver D alone is defective for both v6 and v7, independent of application build.
- The device model is the only relevant factor, so app version and driver correlation should be ignored.
Explanation
Correct Answer
A:The simultaneous dependence on app v7 and driver D supports a scoped interaction hypothesis. Correlation is not definitive causation; test it on the affected cohort and compare stable controls before wider remediation.
Incorrect Answers
B:The app v7 cohort on driver E is stable, so a universal app-version explanation is broader than the observed affected group.
C:Devices using v6 with driver D are stable, which weakens a driver-only explanation and supports examining the interaction.
D:The report ties the spike to a specific app and driver combination; ignoring those factors would discard the strongest available discriminating evidence.
Question 867
Which pilot result would validate the mitigation while detecting collateral app regressions?
- Show only that the change-management ticket was closed.
- Report that one affected user says the app feels quicker after one launch.
- Count only whether the suspected driver was removed, without measuring post-change application crashes or regressions.
- Compare app crashes per affected device before and after the targeted change, include an unchanged control cohort, and monitor other critical app health.
Explanation
Correct Answer
D:Outcome, comparator and secondary checks distinguish an effective fix from a chance fluctuation or regression.
Incorrect Answers
A:Ticket closure is not technical evidence of lower crash rates.
B:A single subjective session does not establish the crash trend and broader compatibility.
C:A completed driver operation does not establish that application reliability improved or that other critical applications were unaffected.
Question 868
After deploying a startup application, a company sees the Endpoint analytics startup score fall. Its helpdesk reports frequent reboots, but the SLA requires shorter time until the desktop is usable. Which investigation best identifies where time increased?
- Compare the Core boot, Group Policy boot, Core logon, and Group Policy logon components for the same device cohort before and after the deployment.
- Use the total restart count as the sole measure of time to a usable desktop.
- Compare only the startup score from two groups with different hardware and no time-window control.
- Inspect the latest compliance-policy assignment timestamp to estimate logon delay.
Explanation
Correct Answer
A:Component-level startup metrics distinguish slow boot from slow logon, while raw reboot counts cannot identify the delay.
Incorrect Answers
B:Restart frequency measures occurrence, not the duration of boot and sign-in.
C:An aggregate cross-cohort score may reflect hardware and sampling differences rather than the application change.
D:An Intune assignment timestamp does not measure OS boot or user sign-in duration.
Question 869
In a pilot, Core boot is unchanged but Group Policy logon time rises from 5 to 40 seconds after a new domain policy. Why is a device restart count not a sufficient diagnosis?
- The regression is concentrated in the logon policy-processing component, rather than the number of restarts or kernel boot duration.
- A high reboot count proves the firmware initialization caused the 35-second delay.
- Unchanged Core boot means there is no user-experience regression.
- The application reliability score alone identifies the affected Group Policy item.
Explanation
Correct Answer
A:The measured increase isolates policy processing during sign-in, where the added delay occurs.
Incorrect Answers
B:Firmware initialization would affect boot, not a specifically measured Group Policy logon interval.
C:Startup experience includes sign-in and desktop-readiness delays, not just Core boot.
D:App crash reliability metrics do not resolve policy-processing contributors during sign-in.
Question 870
What evidence best verifies that the targeted domain policy change fixed the startup regression?
- Observe a lower number of monthly remote restarts without timing measurements.
- Compare before-and-after Group Policy logon and desktop-ready times for the same restarted pilot devices, with a similar unaffected cohort as control.
- Verify only that the updated policy is listed as assigned in Intune.
- Read a single tenant-wide startup score after excluding all slow devices.
Explanation
Correct Answer
B:The matched measurements directly test the slow component and guard against population changes.
Incorrect Answers
A:Restart counts cannot verify that measured sign-in latency improved.
C:Assignment is configuration intent, not evidence of shorter logon processing.
D:Changing the population can improve an aggregate score without fixing the affected endpoints.