Pass Microsoft MD-102 Exam in First Attempt Guaranteed!
Get 100% Latest Exam Questions, Accurate & Verified Answers!
30 Days Free Updates, Instant Download!
Microsoft MD-102 Practice Test 70
Question 690
An automation uses a broadly privileged application identity to export endpoint compliance but its task requires only read access. Select TWO choices that would create avoidable endpoint security or reliability risk.
Explanation
Correct Answer
“Grant DeviceManagementManagedDevices.ReadWrite.All to every public script because reporting otherwise needs an access token” would violate the requirement. Graph application permissions govern what service principals may access, independently of script comments or friendly descriptions.
“Store a global directory administrator credential directly inside the PowerShell script for convenience” would violate the requirement. Graph application permissions govern what service principals may access, independently of script comments or friendly descriptions.
Incorrect Answers
“Grant only approved Microsoft Graph read permissions and validate administrator consent and scoped access requirements” is the controlled implementation, not an unsafe workaround. Graph application permissions govern what service principals may access, independently of script comments or friendly descriptions. Confirm that the script reads permitted compliance data while write and wipe API operations return appropriate access failures.
The script reads permitted compliance data while write and wipe API operations return appropriate access failures. This is a bounded acceptance test of the intended outcome, not an unsafe production shortcut.
“Inspect Entra app registration, Microsoft Graph permission scopes, consent grants, access token roles, and audit logs” is the relevant troubleshooting evidence, not a reason to bypass safeguards. Graph application permissions govern what service principals may access, independently of script comments or friendly descriptions.
Question 691
A support automation accepts arbitrary device IDs from a spreadsheet and could mistakenly wipe a production fleet. Which administrative action should resolve this managed-device problem?
Explanation
Correct Answer
A support automation accepts arbitrary device IDs from a spreadsheet and could mistakenly wipe a production fleet. Design explicit authorization, dry-run, validated scope, and human approval before invoking destructive Graph device actions. Graph service automation executes with assigned authority; script input validation does not come automatically from Microsoft Intune. A test run on dummy records produces no real device wipe and requests approval for an intentionally authorized pilot.
Incorrect Answers
It would not produce the required result: A test run on dummy records produces no real device wipe and requests approval for an intentionally authorized pilot.
“Run a wipe API call for every spreadsheet row before validating the device identity and ownership status” does not implement the control that the facts call for. Instead, design explicit authorization, dry-run, validated scope, and human approval before invoking destructive Graph device actions.
“Treat a user-provided device display name as sufficient authorization to wipe any similarly named device” does not implement the control that the facts call for. Instead, design explicit authorization, dry-run, validated scope, and human approval before invoking destructive Graph device actions.
Question 692
A support automation accepts arbitrary device IDs from a spreadsheet and could mistakenly wipe a production fleet. Which technical checks best identify the relevant management failure?
Explanation
Correct Answer
A support automation accepts arbitrary device IDs from a spreadsheet and could mistakenly wipe a production fleet. Inspect Graph app permissions, target managedDevice IDs, operation logs, dry-run mode, and approval evidence. Graph service automation executes with assigned authority; script input validation does not come automatically from Microsoft Intune. A test run on dummy records produces no real device wipe and requests approval for an intentionally authorized pilot.
Incorrect Answers
This evidence primarily tests security copilot agent triage of endpoint threat; it would not isolate the actual failure boundary in this scenario. The targeted checks are: Inspect Graph app permissions, target managedDevice IDs, operation logs, dry-run mode, and approval evidence.
This evidence primarily tests enrollment failures operational alerting; it would not isolate the actual failure boundary in this scenario. The targeted checks are: Inspect Graph app permissions, target managedDevice IDs, operation logs, dry-run mode, and approval evidence.
This evidence primarily tests compliance drift alert rule thresholds; it would not isolate the actual failure boundary in this scenario. The targeted checks are: Inspect Graph app permissions, target managedDevice IDs, operation logs, dry-run mode, and approval evidence.
Question 693
A support automation accepts arbitrary device IDs from a spreadsheet and could mistakenly wipe a production fleet. Which test would best prove the endpoint requirement is met?
Explanation
Correct Answer
A test run on dummy records produces no real device wipe and requests approval for an intentionally authorized pilot. Design explicit authorization, dry-run, validated scope, and human approval before invoking destructive Graph device actions.
Incorrect Answers
This could validate remediation output secret redaction, but it does not prove the specific requirement has been met. Instead measure: A test run on dummy records produces no real device wipe and requests approval for an intentionally authorized pilot.
This could validate security copilot remediation approval workflow, but it does not prove the specific requirement has been met. Instead measure: A test run on dummy records produces no real device wipe and requests approval for an intentionally authorized pilot.
This could validate remediation script executing repeatedly, but it does not prove the specific requirement has been met. Instead measure: A test run on dummy records produces no real device wipe and requests approval for an intentionally authorized pilot.
Question 694
A support automation accepts arbitrary device IDs from a spreadsheet and could mistakenly wipe a production fleet. What technical constraint most strongly justifies the proposed fix?
Explanation
Correct Answer
Inspect Graph app permissions, target managedDevice IDs, operation logs, dry-run mode, and approval evidence. A test run on dummy records produces no real device wipe and requests approval for an intentionally authorized pilot.
Incorrect Answers
This concerns security copilot agent triage of endpoint threat, which is a different mechanism than the one causing the stated symptom. The principle that applies here is: Graph service automation executes with assigned authority; script input validation does not come automatically from Microsoft Intune.
This concerns endpoint analytics startup score investigation, which is a different mechanism than the one causing the stated symptom. The principle that applies here is: Graph service automation executes with assigned authority; script input validation does not come automatically from Microsoft Intune.
This concerns remediation output secret redaction, which is a different mechanism than the one causing the stated symptom. The principle that applies here is: Graph service automation executes with assigned authority; script input validation does not come automatically from Microsoft Intune.
Question 695
A support automation accepts arbitrary device IDs from a spreadsheet and could mistakenly wipe a production fleet. Which TWO shortcuts conflict with the stated management requirements?
Explanation
Correct Answer
“Treat a user-provided device display name as sufficient authorization to wipe any similarly named device” would violate the requirement. The appropriate control instead is to design explicit authorization, dry-run, validated scope, and human approval before invoking destructive Graph device actions.
“Run a wipe API call for every spreadsheet row before validating the device identity and ownership status” would violate the requirement. The appropriate control instead is to design explicit authorization, dry-run, validated scope, and human approval before invoking destructive Graph device actions.
Incorrect Answers
“Design explicit authorization, dry-run, validated scope, and human approval before invoking destructive Graph device actions” is the controlled implementation, not an unsafe workaround. Confirm that a test run on dummy records produces no real device wipe and requests approval for an intentionally authorized pilot.
“Inspect Graph app permissions, target managedDevice IDs, operation logs, dry-run mode, and approval evidence” is the relevant troubleshooting evidence, not a reason to bypass safeguards.
A test run on dummy records produces no real device wipe and requests approval for an intentionally authorized pilot. This is a bounded acceptance test of the intended outcome, not an unsafe production shortcut.
Question 696
A long-running nightly compliance export fails after an hour because its interactive access token expires. What is the most appropriate supported endpoint management change?
Explanation
Correct Answer
A long-running nightly compliance export fails after an hour because its interactive access token expires. Use a supported unattended authentication method with approved permissions and token refresh handling. PowerShell automation should use governed identity and renew expiring access credentials instead of caching personal interactive secrets. The nightly job completes a multi-hour pilot without human login and records its authorized service identity.
Incorrect Answers
“Disable token expiry checks and assume Microsoft Graph accepts a previously expired access token forever” would not meet the requirement. PowerShell automation should use governed identity and renew expiring access credentials instead of caching personal interactive secrets. Instead, use a supported unattended authentication method with approved permissions and token refresh handling.
It would not produce the required result: The nightly job completes a multi-hour pilot without human login and records its authorized service identity.
“Paste a personal refresh token into public source control so every scheduled job can reuse it indefinitely” does not implement the control that the facts call for. PowerShell automation should use governed identity and renew expiring access credentials instead of caching personal interactive secrets. Instead, use a supported unattended authentication method with approved permissions and token refresh handling.
Question 697
A long-running nightly compliance export fails after an hour because its interactive access token expires. Which evidence most directly isolates the endpoint issue?
Explanation
Correct Answer
A long-running nightly compliance export fails after an hour because its interactive access token expires. Inspect token expiry, authentication method, app permissions, scheduled job context, and 401 response logs. PowerShell automation should use governed identity and renew expiring access credentials instead of caching personal interactive secrets. The nightly job completes a multi-hour pilot without human login and records its authorized service identity.
Incorrect Answers
This evidence primarily tests application reliability score after update; it would not isolate the actual failure boundary in this scenario. The targeted checks are: Inspect token expiry, authentication method, app permissions, scheduled job context, and 401 response logs.
This evidence primarily tests compliance drift alert rule thresholds; it would not isolate the actual failure boundary in this scenario. The targeted checks are: Inspect token expiry, authentication method, app permissions, scheduled job context, and 401 response logs.
This evidence primarily tests microsoft graph device wipe api safeguards; it would not isolate the actual failure boundary in this scenario. The targeted checks are: Inspect token expiry, authentication method, app permissions, scheduled job context, and 401 response logs.
Question 698
A long-running nightly compliance export fails after an hour because its interactive access token expires. What measured result confirms the endpoint deployment now works?
Explanation
Correct Answer
PowerShell automation should use governed identity and renew expiring access credentials instead of caching personal interactive secrets. The nightly job completes a multi-hour pilot without human login and records its authorized service identity.
Incorrect Answers
This could validate microsoft graph intune pagination when listing devices, but it does not prove the specific requirement has been met. Instead measure: The nightly job completes a multi-hour pilot without human login and records its authorized service identity.
This could validate endpoint analytics startup score investigation, but it does not prove the specific requirement has been met. Instead measure: The nightly job completes a multi-hour pilot without human login and records its authorized service identity.
This could validate compliance drift alert rule thresholds, but it does not prove the specific requirement has been met. Instead measure: The nightly job completes a multi-hour pilot without human login and records its authorized service identity.
Question 699
A long-running nightly compliance export fails after an hour because its interactive access token expires. Which underlying Intune or Windows behavior is most relevant here?
Explanation
Correct Answer
PowerShell automation should use governed identity and renew expiring access credentials instead of caching personal interactive secrets. Use a supported unattended authentication method with approved permissions and token refresh handling.
Incorrect Answers
This concerns security copilot device performance recommendation, which is a different mechanism than the one causing the stated symptom. The principle that applies here is: PowerShell automation should use governed identity and renew expiring access credentials instead of caching personal interactive secrets.
This concerns endpoint analytics recommended action validation, which is a different mechanism than the one causing the stated symptom. The principle that applies here is: PowerShell automation should use governed identity and renew expiring access credentials instead of caching personal interactive secrets.
This concerns compliance drift alert rule thresholds, which is a different mechanism than the one causing the stated symptom. The principle that applies here is: PowerShell automation should use governed identity and renew expiring access credentials instead of caching personal interactive secrets.
Question 700
A long-running nightly compliance export fails after an hour because its interactive access token expires. Which TWO unsafe endpoint management actions should be rejected?
Explanation
Correct Answer
“Paste a personal refresh token into public source control so every scheduled job can reuse it indefinitely” would violate the requirement. PowerShell automation should use governed identity and renew expiring access credentials instead of caching personal interactive secrets.
“Disable token expiry checks and assume Microsoft Graph accepts a previously expired access token forever” would violate the requirement. PowerShell automation should use governed identity and renew expiring access credentials instead of caching personal interactive secrets.
Incorrect Answers
“Use a supported unattended authentication method with approved permissions and token refresh handling” is the controlled implementation, not an unsafe workaround. PowerShell automation should use governed identity and renew expiring access credentials instead of caching personal interactive secrets.
“Inspect token expiry, authentication method, app permissions, scheduled job context, and 401 response logs” is the relevant troubleshooting evidence, not a reason to bypass safeguards. PowerShell automation should use governed identity and renew expiring access credentials instead of caching personal interactive secrets. Confirm that the nightly job completes a multi-hour pilot without human login and records its authorized service identity.
The nightly job completes a multi-hour pilot without human login and records its authorized service identity. This is a bounded acceptance test of the intended outcome, not an unsafe production shortcut.
Endpoint Administrator (MD-102) Practice Tests
- Microsoft MD-102 Practice Test 68 - 10 Questions (Last Reviewed 06-Nov-2026)
- Microsoft MD-102 Practice Test 69 - 10 Questions (Last Reviewed 05-Nov-2026)
- Microsoft MD-102 Practice Test 70 - 10 Questions (Last Reviewed 04-Nov-2026)
- Microsoft MD-102 Practice Test 71 - 10 Questions (Last Reviewed 03-Nov-2026)
- Microsoft MD-102 Practice Test 72 - 10 Questions (Last Reviewed 02-Nov-2026)
