Endpoint Administrator MD-102 Practice Test 71
Question 700
A payroll application uses an MSI installation wrapper. An Intune pilot shows the app installing repeatedly although the target MSI is already on the device, and a detection rule uses a file version from an old build. What should be repaired without unnecessary changes to user targeting?
- Update the Win32 app detection rule to match the actual installed version marker and maintain its requirements and assignments
- Convert the app from Required to Uninstall so it stops retrying
- Set the device compliant regardless of installation status
- Configure a Windows feature-update deferral to suppress app checks
Explanation
Correct Answer
A:Detection must reflect the installed build for Intune to recognize completion
Incorrect Answers
B:Uninstall assignment removes software instead of fixing an install state
C:Compliance status is not Win32 app detection
D:OS update deferrals do not repair stale app detection
Question 701
A payroll application uses an MSI installation wrapper. An Intune pilot shows the app installing repeatedly although the target MSI is already on the device, and a detection rule uses a file version from an old build. Intune Management Extension evaluates the package as not installed immediately after a successful MSI exit code on a pilot. What best explains the disagreement?
- The end user is not in the local Administrators group despite system-context installation
- The laptop is Entra joined rather than hybrid joined
- The antivirus signatures were updated between evaluation attempts
- The stale detection rule evaluates the old build marker instead of the installed MSI version
Explanation
Correct Answer
D:App installation and detection are separate evaluation steps
Incorrect Answers
A:Administrative group membership does not necessarily explain system-context detection failure
B:Both join types can support Intune Win32 management with prerequisites
C:Signature refresh alone cannot explain the specified stale version comparison
Question 702
A payroll application uses an MSI installation wrapper. An Intune pilot shows the app installing repeatedly although the target MSI is already on the device, and a detection rule uses a file version from an old build. Which acceptance result shows a durable fix after remediation?
- The application setup wizard can be launched manually on a technician PC
- Installed status persists over the next Intune Management Extension evaluation and installer logs show no unnecessary repeat execution
- An admin edits the app description to show the new MSI version
- Only the initial MSI process returns zero once
Explanation
Correct Answer
B:Stable detection prevents repeat installations for the recognized version
Incorrect Answers
A:Manual UI availability does not validate managed detection
C:Metadata edits are not the installed version marker
D:A single exit status cannot establish subsequent detection success
Question 703
A company is replacing a legacy secure-print client with a new release on already-managed Windows devices. A successful upgrade requires removal of the legacy build and retention of device-specific settings. Which Win32 application rollout best enforces the replacement with controlled migration?
- Configure supersedence with the supported uninstall-previous-version behavior and test a package or script that preserves the approved settings
- Mark the older print client as a prerequisite dependency and leave both installed
- Only change the required app group with no install/uninstall commands for old clients
- Use a store app shortcut with the same display name as the old print client
Explanation
Correct Answer
A:Supersedence can replace the prior build while scripted migration handles required persistent settings
Incorrect Answers
B:A prerequisite relationship does not implement version replacement
C:Assignment changes cannot guarantee the legacy binary is removed
D:A renamed shortcut is not an executable replacement
Question 704
A company is replacing a legacy secure-print client with a new release on already-managed Windows devices. A successful upgrade requires removal of the legacy build and retention of device-specific settings. Pilot users retain duplicate printer extensions after new deployment and both client versions are present. What configuration should be inspected?
- The Windows quality-update deployment schedule
- The supersedence removal choice and legacy client uninstall detection/command execution, including leftover extension cleanup
- The new Win32 app supersedes the old client but its uninstall command leaves the deprecated browser extension installed
- The Microsoft 365 Apps update channel
Explanation
Correct Answer
B:Old-build removal is separate from installing the replacement
Incorrect Answers
A:OS quality update timing does not uninstall the old print client
C:The supersedence relationship alone does not guarantee clean removal if legacy uninstall behavior leaves components behind; validate uninstall command and detection on a previously configured pilot.
D:Office servicing policies are not Win32 supersedence rules
Question 705
A company is replacing a legacy secure-print client with a new release on already-managed Windows devices. A successful upgrade requires removal of the legacy build and retention of device-specific settings. What is the minimum useful migration acceptance test?
- A clean Windows pilot installs the new VPN client successfully but never had the legacy client or browser extension installed
- The new package is in the Intune admin catalog and has a publisher name
- On a previously configured pilot, the new client works with preserved approved settings and the obsolete client and extensions are absent
- The old client remains installed alongside the new version with both launching
Explanation
Correct Answer
C:It verifies both functionality and replacement state
Incorrect Answers
A:A clean install tests the new package only; it cannot prove the supersedence and old-component removal requirements.
B:Catalog metadata is not migration evidence
D:Parallel installation violates the replacement requirement
Question 706
A field-service team uses Microsoft Outlook and Teams with work accounts on Android phones in a supported commercial-cloud tenant. It must mute only Outlook email and Teams notifications during scheduled off-duty hours while keeping Intune app protection and device compliance enforced. What is the appropriate Intune policy?
- Disable all Intune app protection policies outside the shift and turn them back on each morning
- Create an Intune Quiet Time Days of the week policy for the off-duty hours and assign it to the affected users
- Configure Android work-profile lock-screen notification blocking and treat it as a nightly Outlook-and-Teams schedule
- Apply the non-working-time Teams mode without the required Working Time API integration and assume Outlook is also muted
Explanation
Correct Answer
B:Quiet Time scheduled hours can mute Outlook email and Teams notifications on supported mobile clients for the assigned user group while separate security policies remain enforced.
Incorrect Answers
A:Disabling app protection changes data-access security rather than notification delivery and creates an unnecessary exposure window.
C:Lock-screen notification restrictions do not schedule supported Outlook/Teams quiet hours across unlocked devices and both apps.
D:Non-working time depends on the Working Time API for Teams and is not a substitute for a Days of week schedule that also covers Outlook email.
Question 707
A commercial-cloud Intune tenant configured a Days of the week Quiet Time policy for Outlook and Teams notifications on Android phones. A pilot user is in the intended assignment group, today and the current hour are included, end-user overrides are disabled, and the policy was edited ten minutes ago. The user still receives Outlook notifications. What should be checked first?
- Recent Quiet Time policy edits may take up to 24 hours to reach users; verify the active assignment and allow the documented propagation interval
- The user can always override quiet time even though the administrator disabled end-user changes
- A non-working-time policy must use Working Time API for every Days of the week policy
- Outlook notifications are never in scope for Intune Quiet Time, only Teams messages are
Explanation
Correct Answer
A:Microsoft notes a 24-hour propagation window after quiet-time changes; a ten-minute old edit cannot be judged as fully effective yet.
Incorrect Answers
B:The scenario explicitly disables user overrides; a supposed universal override does not explain the assigned policy not yet reaching the app.
C:Working Time API is needed for the separate Teams non-working-time mode, not the calendar-based Days of the week policy in this case.
D:Supported quiet time also mutes Outlook email notifications; the claim that it supports only Teams is incorrect.
Question 708
A field-service pilot uses an Intune Quiet Time Days of the week policy for supported Outlook and Teams apps on Android, with evening mute hours. After the documented propagation period has passed, which observation best verifies the policy without confusing quiet time with disabled data-security controls?
- The Android operating system is in Do Not Disturb mode, but neither Outlook nor Teams work notifications are tested
- For an assigned test account, Outlook and Teams work notifications are muted during the scheduled hours and resume outside them while app protection/compliance remain active
- Intune app protection is switched off during the shift break, producing fewer mobile prompts
- The new policy has an Assigned portal status, but no app-level notifications or active security policies are checked
Explanation
Correct Answer
B:Testing both supported apps in and out of the scheduled interval verifies notification behavior while separate app-protection and compliance checks confirm security remains in effect.
Incorrect Answers
A:OS-level Do Not Disturb can suppress many unrelated alerts and does not establish that the Intune Quiet Time policy was delivered and enforced.
C:Reducing notifications by disabling data protection is not proof the dedicated Quiet Time policy works and violates the security requirement.
D:An Assigned status is a configuration observation, not device-app evidence of muted and resumed alerts or unchanged app/data controls.
Question 709
A multinational firm installs Microsoft 365 Apps across Windows devices and wants to investigate degraded Office start-up after an app release without mistaking a portal health advisory for proof of cause. Which investigation design narrows the cause while preserving client evidence?
- Use the Windows device uptime score as the sole indicator of a Microsoft 365 Apps servicing regression
- Switch all Windows OS feature-update rings regardless of the affected Office builds
- Declare the service advisory alone conclusive proof of each local application crash
- Correlate affected Office builds and update channels with device/app health signals, installation history and cohort timing
Explanation
Correct Answer
D:Versioned client telemetry and rollout timing can separate an app regression from unrelated device issues
Incorrect Answers
A:General uptime alone cannot isolate Office build, update channel and app-specific failure cohorts; correlate the actual Office crash and install evidence.
B:OS policy changes without evidence do not isolate Office application regressions
C:A broad advisory cannot establish an endpoint-specific cause
Question 710
A multinational firm installs Microsoft 365 Apps across Windows devices and wants to investigate degraded Office start-up after an app release without mistaking a portal health advisory for proof of cause. An Office app reliability graph worsens after a new build only on one update channel. The rest of the fleet remains stable. Which diagnosis is best supported?
- A single device on the affected Office channel crashes, so treat all clients on every channel as defective
- A channel- or build-scoped application regression should be investigated using affected and unaffected cohorts, not assumed to be a tenantwide endpoint failure
- The desktop app crash rate is elevated only for a specific Microsoft 365 Apps build, but the OS version is unexamined
- Device names must be standardized to correct Office reliability metrics
Explanation
Correct Answer
B:A version-specific comparison provides stronger causal evidence than overall failure rate
Incorrect Answers
A:One device cannot establish a tenantwide failure or distinguish a bad app build from a local configuration; compare affected/unaffected build cohorts.
C:A build correlation is worth investigating, but it does not alone prove Office is the root cause without controlling for OS and device cohort differences.
D:Naming conventions do not repair application runtime faults