Free Microsoft Endpoint MD-102 Actual Exam Questions - Question 15 Discussion
From the Deployment Workbench, you open the New Task Sequence Wizard and select the
Standard Client Upgrade Task Sequence task sequence template.
You discover that there are no operating system images listed on the Select OS page as
shown in the following exhibit.
You need to be able to select an operating system image to perform a Windows 11 in-place
upgrade.
What should you do?
I think another angle is to consider that the ElevationRules1 policy is specifically targeting File1.exe with an automatic elevation type, which should override the default setting requiring user confirmation. So for devices in Group2, the user shouldn’t see any prompt. But for devices in Group1, since they don’t have the elevation rule assigned, they get the default policy requiring confirmation and justification. The tricky part is if a device is in both groups; it might depend on how Intune merges these policies, but usually, more specific rules (like one targeting a file) take precedence o
Devices in both groups likely get confirmation since policy settings can stack, not override.
If a device is in both groups, I think the more restrictive policy might win, so user confirmation with business justification could still be required even with the automatic elevation rule present.
From what I see, since Group1 and Group2 are separate and the policies are assigned distinctly, devices in Group1 will require user confirmation with business justification due to ElevationSettings1. Devices in Group2 get automatic elevation without prompts because of ElevationRules1. There’s no overlap mentioned, so no combined effect occurs. That means each device follows just one policy based on its group membership, not both. So it’s really about which group the device is in to determine the elevation behavior.
If a device belongs only to Group1, user confirmation and business justification apply. But for devices only in Group2, Rule1’s automatic elevation kicks in, bypassing the need for confirmation. This makes sense given the policy assignments.
If a device is only in Group2, Rule1 applies automatically without user confirmation, overriding ElevationSettings1 from Group1 since that policy isn’t targeted there. So for devices in Group2 only, automatic elevation happens.
If no device is in both groups, policies won’t conflict on any device.
Just adding that since the policies are assigned to different groups, devices in both groups might get conflicting settings. But from what I get, Group2’s automatic elevation for File1.exe overrides the default requiring confirmation on those devices. So if a device is only in Group1, user confirmation plus justification is needed. If it’s in Group2, it runs automatically without prompts. Devices not in either group won’t have these specific policies applied, so default Windows behavior would apply there. The key is knowing each device’s group membership to determine how these policies interac
If a device is only in Group1, it follows the default elevation settings needing user confirmation and justification. The automatic elevation in Rule1 only applies to devices in Group2, so those get the smooth run for File1.exe.
For the desktop in Group2, Rule1 should allow File1.exe to run automatically without confirmation since it’s assigned to that group. Everything else depends on group membership.