Endpoint Administrator MD-102 Practice Test 26
Question 250
A Windows 365 Enterprise administrator updates the base image for an existing provisioning policy, but management must not unexpectedly rebuild employee Cloud PCs. What does saving the image change do to already provisioned Cloud PCs?
- Silently replace the image on all existing Cloud PCs overnight without any action
- Remove all assigned users to force a non-destructive image patch
- Publish the image to the Windows Store to trigger policy adoption
- Apply the new image to new or explicitly reprovisioned Cloud PCs, while existing Cloud PCs remain unchanged until a deliberate reprovision
Explanation
Correct Answer
D:Editing a provisioning-policy image is not an automatic in-place existing-VM upgrade
Incorrect Answers
A:Existing Cloud PCs do not automatically adopt a changed base image
B:Unassignment affects Cloud PC lifecycle and is not a safe in-place image update
C:Store app updates do not replace the Cloud PC base image
Question 251
A Windows 365 Enterprise administrator updates the base image for an existing provisioning policy, but management must not unexpectedly rebuild employee Cloud PCs. After the policy image is changed, newly provisioned Cloud PCs use the new image while an old Cloud PC stays on the previous image. What is the correct interpretation?
- The old Cloud PC failed to receive a wallpaper policy, which blocks image refresh
- A tenant administrator forgot to rename the provisioning policy
- The image has been replaced in the provisioning-policy definition, but no maintenance window was set for existing Cloud PCs
- The old Cloud PC was not reprovisioned; current policy image changes are applied at new provisioning or reprovision
Explanation
Correct Answer
D:This is expected policy propagation behavior, not an image-download error
Incorrect Answers
A:Wallpaper policy is not a base image mechanism
B:Display name does not refresh existing machines
C:A maintenance window alone does not retrofit a new base image to already provisioned Cloud PCs; image changes affect new provisioning or explicit reprovisioning.
Question 252
A Windows 365 Enterprise administrator updates the base image for an existing provisioning policy, but management must not unexpectedly rebuild employee Cloud PCs. Which comparison validates the nondisruptive rollout intent?
- Verify the provisioning-policy image picker displays the new entry
- Confirm that an old Cloud PC wallpaper changed
- Compare a newly provisioned Cloud PC and an untouched existing Cloud PC, confirming only the new device uses the new image and old user data remains available
- Use the Reprovision action on the entire existing fleet just to test the edit
Explanation
Correct Answer
C:Shows correct policy scope and no unintended rebuild
Incorrect Answers
A:Configuration selection does not show existing device impact
B:Wallpaper is not a trustworthy base-image fingerprint
D:Reprovisioning is destructive and violates the nondisruption constraint
Question 253
A Windows 365 Cloud PC has persistent corruption and IT considers reprovisioning while the user has data saved only on the Cloud PC disk. Which preparation is required before initiating reprovision?
- Secure or migrate user data off the Cloud PC and explicitly authorize the destructive reprovision action
- Promise that reprovision retains the entire user disk by default
- Delete the current provisioning policy before preserving files
- Assign a Windows feature-update ring as if it were a user-data backup
Explanation
Correct Answer
A:Reprovision creates a new Cloud PC and deletes the old data, apps and customizations
Incorrect Answers
B:Microsoft explicitly describes loss of the old disk data and apps
C:Removing the policy does not protect user data and can disrupt provisioning
D:Update policy is not a backup of local Cloud PC files
Question 254
A Windows 365 Cloud PC has persistent corruption and IT considers reprovisioning while the user has data saved only on the Cloud PC disk. The reprovisioned Cloud PC has a new name and lacks the users locally stored settings and app. What explains the observation?
- The Microsoft 365 sign-in session refreshed the installed operating system without affecting storage
- An app protection policy only selectively wiped corporate data from the original browser
- The old Cloud PC was moved intact to a different region
- The old Cloud PC was wiped and replaced under the current provisioning policy, which does not retain its local content
Explanation
Correct Answer
D:Reprovisioning is a destructive rebuild
Incorrect Answers
A:Authentication sessions do not cause this complete device replacement
B:MAM selective wipe is not Windows 365 reprovision
C:A move preserves the device and differs from a reprovision
Question 255
A Windows 365 Cloud PC has persistent corruption and IT considers reprovisioning while the user has data saved only on the Cloud PC disk. What evidence is appropriate after a planned approved reprovision?
- The original Cloud PC remains listed as the same disk image after reprovision
- Windows Update shows a successful patch history on the old device
- A new Cloud PC from the current provisioning policy reaches a healthy provisioned state and the user restores previously protected data from approved backup storage
- The user saw a status email without signing in to the new Cloud PC
Explanation
Correct Answer
C:Validates rebuild and deliberate data recovery
Incorrect Answers
A:Reprovision should replace the prior virtual machine
B:Patch history does not validate replacement provisioning
D:Notification alone is not endpoint acceptance evidence
Question 256
A lab plans classic Windows Autopilot self-deploying mode for shared Windows workstations and tests on virtual machines without a physical TPM 2.0. Which platform prerequisite must the team enforce before the pilot?
- Depend on the virtual machines simulated TPM 1.2 and omit attestation
- Keep the test as a general-purpose virtual machine and enable a software TPM without validating attestation support
- Add another Entra user sign-in and call it self-deploying mode
- Use supported physical devices with TPM 2.0 attestation for classic self-deploying mode
Explanation
Correct Answer
D:Self-deploying Entra join uses device TPM attestation and unsupported VMs can fail
Incorrect Answers
A:TPM 1.2 does not meet the documented self-deployment requirement
B:A virtual TPM indicator is not proof the classic self-deploying attestation path is supported; the case requires eligible hardware with functioning TPM 2.0 attestation.
C:User-driven sign-in is a distinct deployment mode
Question 257
A lab plans classic Windows Autopilot self-deploying mode for shared Windows workstations and tests on virtual machines without a physical TPM 2.0. A self-deploying pilot produces 0x801c03ea during OOBE on the test hardware. What does this error identify?
- The device has only one available Windows feature update
- TPM attestation failed, preventing the self-deploying device-token join
- A user chose a long device display name
- The TPM is present but the attestation service has not returned a successful attestation token for this client
Explanation
Correct Answer
B:This exact failure code indicates the attestation boundary
Incorrect Answers
A:Servicing cadence is not the TPM attestation error
C:Display name length is not indicated by this attestation code
D:Attestation failure is the keyed diagnosis, whereas mere TPM presence or pending attestation does not establish a different independent cause; check the specific attestation result behind the device-join error.
Question 258
A lab plans classic Windows Autopilot self-deploying mode for shared Windows workstations and tests on virtual machines without a physical TPM 2.0. What proof establishes that the hardware is suitable and self-deployment worked?
- A VM with a simulated TPM lists a Windows product key
- A user-driven Autopilot deployment succeeds with a named user
- The device can open a web page before Entra join
- A physical TPM 2.0 device completes self-deploying OOBE with successful device identity and Intune enrollment without a user sign-in step
Explanation
Correct Answer
D:Confirms attestation-dependent device-token join and required userless experience
Incorrect Answers
A:License data does not validate attestation
B:Different deployment mode cannot validate self-deploying prerequisites
C:Network connectivity alone is insufficient for TPM-based provisioning
Question 259
A new Windows 11 rollout uses Autopilot device preparation, but selected required apps are not appearing in its OOBE progress. How must application assignments align with the device-preparation policy?
- Assign apps only to an unrelated All Employees user group and expect preparation to infer the device group
- Assign every selected application and script to the device security group specified in the device-preparation policy
- Use classic ESP required-app assignment without specifying any app in device preparation
- Make each app Available in Company Portal but not Required for the specified device group
Explanation
Correct Answer
B:Device preparation tracks the chosen apps/scripts through the policy device-group targeting
Incorrect Answers
A:The selected device-group targeting requirement remains unmet
C:Classic ESP tracking is not the device-preparation app set
D:Optional app availability does not satisfy the tracked preparation requirements
Question 260
A new Windows 11 rollout uses Autopilot device preparation, but selected required apps are not appearing in its OOBE progress. The device shows the device-preparation progress interface but the VPN app is missing from the tracked list. Which cause should be examined?
- Windows Defender Antivirus completed a daily scan
- Another user successfully installed VPN manually from Company Portal
- A classic Autopilot Enrollment Status Page rule is set to ten minutes
- The VPN application is not properly targeted to the exact device group selected by the device-preparation policy
Explanation
Correct Answer
D:Group mismatch means the app cannot be tracked as expected
Incorrect Answers
A:Antivirus scanning does not supply the missing required-app assignment
B:Manual user availability cannot prove a device preparation assignment
C:The device-preparation flow does not use the classic ESP