Exam MS-101 topic 1 question 7 discussion

NO-YES-YES

N: Device1 is not in the pilot group N: All devices regardless of in the pilot group or not are switched to update via InTune. Y: Device2 is in the pilot group and anything in the pilot group should be managed by InTune. Configuration Manager: Configuration Manager continues to manage this workload. Pilot Intune: Switch this workload only for the devices in the pilot collection. You can change the Pilot collections on the Staging tab of the co-management properties page. Intune: Switch this workload for all Windows 10 devices enrolled in co-management.

No Yes Yes

No,yes,yes?

The answer should be No, Yes, Yes. 1. Device1 doesn't enroll to co-management since it's not in the pilot collection. Thus everything's must be manage by CM. -> No 2. Since every setting or configuration of Devices1 must be manage by CM, thus the answer is -> Yes 3. This is obviously clear that device2 is in the pilot collection, so it's being manage by co-management -> Yes

No Yes Yes Quest 2 is catching a lot of people out, it is asking about 'Config Manager' not Intune (unlike qu1), so as Device 1 isn't being managed by intune at all (not a member of pilot group) the answer is actually Yes.

✑ Automatic enrollment in Intune: Pilot ✑ Pilot collection for all workloads: Collection2 Collection 1 (Device 1) is not being targeted, so answer has to be N-N-Y

The answer is pretty clear, if you read the question carefully. First one - NO. Device1 is not part of the Pilot collection (Collection2) so compliance is managed by CM. Second one - NO. Same reason as above. Even if "Windows Update Policies" slider is set to "Intune", the question clearly states that "Automatic enrollment in Intune: Pilot" so only the devices from the Pilot collection (Collection2) are enrolled in Intune and thus have the update policies managed by Intune. Third one is yes, for obvious reasons (Device2 is part of the Pilot Collection).

its N,Y,Y. The second question indeed does not mention the configuration of the ConfigMngr but by default settings for Clients Updates are enabled, so by default ConfigMngr is controlling updates.

There is a lot of confusion on this question, specifically number 2. Some people seem to think these settings don't tell us anything about co-management for device 1. That's incorrect. We know all devices are in configuration manager based on what the question said, and (this is where the confusion is at) we know co-management was enabled because we wouldn't be able to get to the properties of co-management before activating co-management, so co-management is enabled, and that means the answer for option 2 is NO. The policy created only determines which devices are in the pilot group. All other devices not in that group follow the co-management settings. If you read this document, you will see what I am referring to. "You can switch workloads when you enable co-management, or later when you're ready. If you haven't already enabled co-management, do that first." https://docs.microsoft.com/en-us/mem/configmgr/comanage/how-to-switch-workloads Answers are N, N, Y.

+ You use Microsoft Endpoint Configuration Manager for device management. + Device1 -->Collection1 + Pilot collection for all workloads : Collection2 --> ("co-management") + Answer 2: Yes

NO, Yes, Yes

No- YES- YES( refer lucidgreens explanation) It makes Perfect Sense

Obvious: 1: NO 3: YES Now lets go to the 2nd question: I will go with the (NO) Explanation The device1 Windows updates are NOT managed by Intune, that is for sure. All of you assume that device1 Win updates are managed by ConfigManager because they are not managed by Intune. Why? Do we have this information in the facts of the question? No! The Win Updates could be not managed at all! Think out of the box! NO NO YES

N-Y-Y Auto enrollment in Intune excludes device 1 from being managed by Intune. https://docs.microsoft.com/en-us/mem/configmgr/comanage/how-to-enable

So what's the right answer? -- Nothing tells me that Device1 is a part of a pilot collection group. Microsft Intune manages the compliance policies for Device1: NO ConfMgr manages the Windows Update policies for Device1: Yes Intune manages Endpoint Protection for Device2: Yes

YYN 2 is Yes because Device 1 is NOT enrolled in Intune and therefore cannot use any Intune workload. It can only use CM. Read: Automatic enrollment into Intune - Pilot: Only the Configuration Manager clients that are members of the Intune Auto Enrollment collection are automatically enrolled to Intune. https://docs.microsoft.com/en-us/mem/configmgr/comanage/tutorial-co-manage-clients.