Microsoft MD-102 Practice Test 71 - Prepaway
Practice Exams:

Pass Microsoft MD-102 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium Bundle
$29.98
$79.99 $109.97

MD-102 Premium Bundle


  • Premium File 463 Questions & Answers. Last update: Nov 12, 2026
  • Training Course 84 Lectures
  • Study Guide 512 Pages

Microsoft MD-102 Practice Test 71

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?

  1. Use a supported unattended authentication method with approved permissions and token refresh handling.
  2. Paste a personal refresh token into public source control so every scheduled job can reuse it indefinitely.
  3. Disable token expiry checks and assume Microsoft Graph accepts a previously expired access token forever.
  4. Inspect token expiry, authentication method, app permissions, scheduled job context, and 401 response logs.
  5. The nightly job completes a multi-hour pilot without human login and records its authorized service identity.

Explanation

Correct Answer

B:

“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.

C:

“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

A:

“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.

D:

“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.

E:

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.

Question 701

An Intune rollout script manually adds devices to pilot groups and accidentally adds unsupported personal endpoints. Which Intune or Entra configuration best solves the endpoint requirement?

  1. Add every endpoint containing a common laptop substring and assume this proves business ownership and eligibility.
  2. Use supported group membership queries or dynamic device attributes with ownership verification before assigning endpoint policies.
  3. Design explicit authorization, dry-run, validated scope, and human approval before invoking destructive Graph device actions.
  4. Copy unrelated users into a device group and expect Intune device configuration policy to target their laptops.

Explanation

Correct Answer

B:

An Intune rollout script manually adds devices to pilot groups and accidentally adds unsupported personal endpoints. Use supported group membership queries or dynamic device attributes with ownership verification before assigning endpoint policies. Device grouping automation must validate authoritative identity attributes rather than trusting unreviewed display names. A test deployment selects only eligible corporate devices and records membership changes for audit.

Incorrect Answers

A:

“Add every endpoint containing a common laptop substring and assume this proves business ownership and eligibility” would not meet the requirement. Device grouping automation must validate authoritative identity attributes rather than trusting unreviewed display names. Instead, use supported group membership queries or dynamic device attributes with ownership verification before assigning endpoint policies.

C:

It would not produce the required result: A test deployment selects only eligible corporate devices and records membership changes for audit.

D:

“Copy unrelated users into a device group and expect Intune device configuration policy to target their laptops” does not implement the control that the facts call for. Device grouping automation must validate authoritative identity attributes rather than trusting unreviewed display names. Instead, use supported group membership queries or dynamic device attributes with ownership verification before assigning endpoint policies.

Question 702

An Intune rollout script manually adds devices to pilot groups and accidentally adds unsupported personal endpoints. What should the administrator inspect to diagnose this behavior?

  1. Inspect token expiry, authentication method, app permissions, scheduled job context, and 401 response logs.
  2. Inspect group rule, device ownership, Graph object IDs, registration source, and assignment results.
  3. Inspect detection and remediation log output, PowerShell transcripts, secret access method, and role-based log permissions.
  4. Inspect enrollment failure report, platform and error grouping, event timestamps, notification route, and token health.

Explanation

Correct Answer

B:

An Intune rollout script manually adds devices to pilot groups and accidentally adds unsupported personal endpoints. Inspect group rule, device ownership, Graph object IDs, registration source, and assignment results. Device grouping automation must validate authoritative identity attributes rather than trusting unreviewed display names. A test deployment selects only eligible corporate devices and records membership changes for audit.

Incorrect Answers

A:

This evidence primarily tests powershell graph authentication token renewal; it would not isolate the actual failure boundary in this scenario. The targeted checks are: Inspect group rule, device ownership, Graph object IDs, registration source, and assignment results.

C:

This evidence primarily tests remediation output secret redaction; it would not isolate the actual failure boundary in this scenario. The targeted checks are: Inspect group rule, device ownership, Graph object IDs, registration source, and assignment results.

D:

This evidence primarily tests enrollment failures operational alerting; it would not isolate the actual failure boundary in this scenario. The targeted checks are: Inspect group rule, device ownership, Graph object IDs, registration source, and assignment results.

Question 703

An Intune rollout script manually adds devices to pilot groups and accidentally adds unsupported personal endpoints. Which acceptance criterion validates the chosen endpoint management solution?

  1. A failing pilot produces a Boolean false with an expected noncompliant rule result and correct supporting evidence.
  2. Service health reporting aligns with the incident and devices recover management check-in after provider restoration.
  3. A test deployment selects only eligible corporate devices and records membership changes for audit.
  4. An affected pilot is detected and fixed once while a healthy test device remains unchanged after scheduled evaluation.

Explanation

Correct Answer

C:

Device grouping automation must validate authoritative identity attributes rather than trusting unreviewed display names. A test deployment selects only eligible corporate devices and records membership changes for audit. If this test fails, inspect group rule, device ownership, Graph object IDs, registration source, and assignment results.

Incorrect Answers

A:

This could validate powershell custom compliance json typing, but it does not prove the specific requirement has been met. Instead measure: A test deployment selects only eligible corporate devices and records membership changes for audit.

B:

This could validate tenant service health versus device issue, but it does not prove the specific requirement has been met. Instead measure: A test deployment selects only eligible corporate devices and records membership changes for audit.

D:

This could validate remediations detection and correction scripts, but it does not prove the specific requirement has been met. Instead measure: A test deployment selects only eligible corporate devices and records membership changes for audit.

Question 704

An Intune rollout script manually adds devices to pilot groups and accidentally adds unsupported personal endpoints. Which Microsoft endpoint management principle explains the decision?

  1. Device grouping automation must validate authoritative identity attributes rather than trusting unreviewed display names.
  2. Operational dashboard filtering and authorization should align so visual reports do not disclose unrelated regions.
  3. Endpoint reporting can expose sensitive device and user metadata, so export access and storage require governance.
  4. Agent-generated security recommendations support analyst judgment but do not automatically establish authority for destructive response.

Explanation

Correct Answer

A:

Device grouping automation must validate authoritative identity attributes rather than trusting unreviewed display names. Use supported group membership queries or dynamic device attributes with ownership verification before assigning endpoint policies. The decisive evidence is that a test deployment selects only eligible corporate devices and records membership changes for audit.

Incorrect Answers

B:

This concerns intune workbook operational dashboard filters, which is a different mechanism than the one causing the stated symptom. The principle that applies here is: Device grouping automation must validate authoritative identity attributes rather than trusting unreviewed display names.

C:

This concerns reporting export permissions and sensitive endpoint data, which is a different mechanism than the one causing the stated symptom. The principle that applies here is: Device grouping automation must validate authoritative identity attributes rather than trusting unreviewed display names.

D:

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: Device grouping automation must validate authoritative identity attributes rather than trusting unreviewed display names.

Question 705

An Intune rollout script manually adds devices to pilot groups and accidentally adds unsupported personal endpoints. Select TWO choices that would create avoidable endpoint security or reliability risk.

  1. Copy unrelated users into a device group and expect Intune device configuration policy to target their laptops.
  2. Add every endpoint containing a common laptop substring and assume this proves business ownership and eligibility.
  3. A test deployment selects only eligible corporate devices and records membership changes for audit.
  4. Use supported group membership queries or dynamic device attributes with ownership verification before assigning endpoint policies.
  5. Inspect group rule, device ownership, Graph object IDs, registration source, and assignment results.

Explanation

Correct Answer

A:

“Copy unrelated users into a device group and expect Intune device configuration policy to target their laptops” would violate the requirement. Device grouping automation must validate authoritative identity attributes rather than trusting unreviewed display names.

B:

“Add every endpoint containing a common laptop substring and assume this proves business ownership and eligibility” would violate the requirement. Device grouping automation must validate authoritative identity attributes rather than trusting unreviewed display names.

Incorrect Answers

C:

A test deployment selects only eligible corporate devices and records membership changes for audit. This is a bounded acceptance test of the intended outcome, not an unsafe production shortcut.

D:

“Use supported group membership queries or dynamic device attributes with ownership verification before assigning endpoint policies” is the controlled implementation, not an unsafe workaround. Device grouping automation must validate authoritative identity attributes rather than trusting unreviewed display names. Confirm that a test deployment selects only eligible corporate devices and records membership changes for audit.

E:

“Inspect group rule, device ownership, Graph object IDs, registration source, and assignment results” is the relevant troubleshooting evidence, not a reason to bypass safeguards. Device grouping automation must validate authoritative identity attributes rather than trusting unreviewed display names.

Question 706

An Intune custom compliance script reports the string false for an endpoint check, but the rules expect a Boolean. Which administrative action should resolve this managed-device problem?

  1. Print formatted colored progress messages instead of compliant JSON and assume Intune infers the desired Boolean.
  2. Use supported group membership queries or dynamic device attributes with ownership verification before assigning endpoint policies.
  3. Emit valid schema-compliant JSON using supported primitive types and align rules evaluation to actual output.
  4. Change the rule to accept any text so failing security agent checks always pass.

Explanation

Correct Answer

C:

An Intune custom compliance script reports the string false for an endpoint check, but the rules expect a Boolean. Emit valid schema-compliant JSON using supported primitive types and align rules evaluation to actual output. Custom compliance evaluates typed script output, so ambiguous strings cannot substitute for declared Boolean conditions. A failing pilot produces a Boolean false with an expected noncompliant rule result and correct supporting evidence.

Incorrect Answers

A:

“Print formatted colored progress messages instead of compliant JSON and assume Intune infers the desired Boolean” would not meet the requirement. Custom compliance evaluates typed script output, so ambiguous strings cannot substitute for declared Boolean conditions. Instead, emit valid schema-compliant JSON using supported primitive types and align rules evaluation to actual output.

B:

It would not produce the required result: A failing pilot produces a Boolean false with an expected noncompliant rule result and correct supporting evidence.

D:

“Change the rule to accept any text so failing security agent checks always pass” does not implement the control that the facts call for. Custom compliance evaluates typed script output, so ambiguous strings cannot substitute for declared Boolean conditions. Instead, emit valid schema-compliant JSON using supported primitive types and align rules evaluation to actual output.

Question 707

An Intune custom compliance script reports the string false for an endpoint check, but the rules expect a Boolean. Which technical checks best identify the relevant management failure?

  1. Inspect PowerShell JSON serialization, custom rule file, script output, Intune report, and device execution log.
  2. Inspect Endpoint Analytics app reliability events, app version, failure signatures, device group, and deployment history.
  3. Inspect alert rule scope, notification channel, thresholds, recent compliance evaluations, and incident ownership.
  4. Inspect agent evidence links, Defender timeline, device owner, recommended action, and approval decisions.

Explanation

Correct Answer

A:

An Intune custom compliance script reports the string false for an endpoint check, but the rules expect a Boolean. Inspect PowerShell JSON serialization, custom rule file, script output, Intune report, and device execution log. Custom compliance evaluates typed script output, so ambiguous strings cannot substitute for declared Boolean conditions. A failing pilot produces a Boolean false with an expected noncompliant rule result and correct supporting evidence.

Incorrect Answers

B:

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 PowerShell JSON serialization, custom rule file, script output, Intune report, and device execution log.

C:

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 PowerShell JSON serialization, custom rule file, script output, Intune report, and device execution log.

D:

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 PowerShell JSON serialization, custom rule file, script output, Intune report, and device execution log.

Question 708

An Intune custom compliance script reports the string false for an endpoint check, but the rules expect a Boolean. Which test would best prove the endpoint requirement is met?

  1. Service health reporting aligns with the incident and devices recover management check-in after provider restoration.
  2. The nightly job completes a multi-hour pilot without human login and records its authorized service identity.
  3. A failing pilot produces a Boolean false with an expected noncompliant rule result and correct supporting evidence.
  4. An authorized audit role exports only required fields to an approved location and unauthorized staff cannot view it.

Explanation

Correct Answer

C:

Custom compliance evaluates typed script output, so ambiguous strings cannot substitute for declared Boolean conditions. A failing pilot produces a Boolean false with an expected noncompliant rule result and correct supporting evidence.

Incorrect Answers

A:

This could validate tenant service health versus device issue, but it does not prove the specific requirement has been met. Instead measure: A failing pilot produces a Boolean false with an expected noncompliant rule result and correct supporting evidence.

B:

This could validate powershell graph authentication token renewal, but it does not prove the specific requirement has been met. Instead measure: A failing pilot produces a Boolean false with an expected noncompliant rule result and correct supporting evidence.

D:

This could validate reporting export permissions and sensitive endpoint data, but it does not prove the specific requirement has been met. Instead measure: A failing pilot produces a Boolean false with an expected noncompliant rule result and correct supporting evidence.

Question 709

An Intune custom compliance script reports the string false for an endpoint check, but the rules expect a Boolean. What technical constraint most strongly justifies the proposed fix?

  1. Custom compliance evaluates typed script output, so ambiguous strings cannot substitute for declared Boolean conditions.
  2. Fleet averages may mask repeated failures concentrated in one model or firmware version.
  3. Endpoint reporting can expose sensitive device and user metadata, so export access and storage require governance.
  4. Efficient API polling must obey service throttling and endpoint feature support rather than assuming unlimited request throughput.

Explanation

Correct Answer

A:

Custom compliance evaluates typed script output, so ambiguous strings cannot substitute for declared Boolean conditions. Emit valid schema-compliant JSON using supported primitive types and align rules evaluation to actual output. The decisive evidence is that a failing pilot produces a Boolean false with an expected noncompliant rule result and correct supporting evidence.

Incorrect Answers

B:

This concerns endpoint analytics device health model comparison, which is a different mechanism than the one causing the stated symptom. The principle that applies here is: Custom compliance evaluates typed script output, so ambiguous strings cannot substitute for declared Boolean conditions.

C:

This concerns reporting export permissions and sensitive endpoint data, which is a different mechanism than the one causing the stated symptom. The principle that applies here is: Custom compliance evaluates typed script output, so ambiguous strings cannot substitute for declared Boolean conditions.

D:

This concerns graph delta synchronization for device inventory, which is a different mechanism than the one causing the stated symptom. The principle that applies here is: Custom compliance evaluates typed script output, so ambiguous strings cannot substitute for declared Boolean conditions.

Question 710

An Intune custom compliance script reports the string false for an endpoint check, but the rules expect a Boolean. Which TWO shortcuts conflict with the stated management requirements?

  1. Inspect PowerShell JSON serialization, custom rule file, script output, Intune report, and device execution log.
  2. Change the rule to accept any text so failing security agent checks always pass.
  3. A failing pilot produces a Boolean false with an expected noncompliant rule result and correct supporting evidence.
  4. Print formatted colored progress messages instead of compliant JSON and assume Intune infers the desired Boolean.
  5. Emit valid schema-compliant JSON using supported primitive types and align rules evaluation to actual output.

Explanation

Correct Answer

B:

“Change the rule to accept any text so failing security agent checks always pass” would violate the requirement. Custom compliance evaluates typed script output, so ambiguous strings cannot substitute for declared Boolean conditions.

D:

“Print formatted colored progress messages instead of compliant JSON and assume Intune infers the desired Boolean” would violate the requirement. Custom compliance evaluates typed script output, so ambiguous strings cannot substitute for declared Boolean conditions.

Incorrect Answers

A:

“Inspect PowerShell JSON serialization, custom rule file, script output, Intune report, and device execution log” is the relevant troubleshooting evidence, not a reason to bypass safeguards. Custom compliance evaluates typed script output, so ambiguous strings cannot substitute for declared Boolean conditions.

C:

A failing pilot produces a Boolean false with an expected noncompliant rule result and correct supporting evidence. This is a bounded acceptance test of the intended outcome, not an unsafe production shortcut.

E:

“Emit valid schema-compliant JSON using supported primitive types and align rules evaluation to actual output” is the controlled implementation, not an unsafe workaround. Custom compliance evaluates typed script output, so ambiguous strings cannot substitute for declared Boolean conditions. Confirm that a failing pilot produces a Boolean false with an expected noncompliant rule result and correct supporting evidence.

Endpoint Administrator (MD-102) Practice Tests