Free Microsoft GH-100 Actual Exam Questions - Question 1 Discussion

C/D? I’m between C and D since allowing manual updates could help fix errors quickly, but without the clear mapping in D, manual updates might just cause confusion. So D feels safer overall.

It’s D because without a clear mapping from identity provider groups to GitHub teams, you risk inconsistent permissions. Sync frequency or manual updates don’t solve the root problem of alignment.

Maybe B, since too frequent syncing could mess up performance initially.

D imo, syncing relies on clear group-role mapping to avoid chaos later.

I’m going with D here. Getting the identity provider groups clearly mapped to GitHub teams and roles upfront prevents confusion and errors down the line. If that’s not nailed, you’ll end up with mismatched permissions no matter how often you sync or update manually. So, prioritizing clear group alignment makes sense before worrying about manual tweaks or sync frequency.

It’s C because manual updates can handle edge cases syncs might miss.

Not B, frequent syncs keep team data accurate and reduce manual fixes.

It’s D because defining group alignment upfront avoids messy mismatches later.

Option B might be worth considering since an infrequent sync schedule can help prevent system overload during initial setup, especially if the team structure is complex. Starting slow lets you monitor performance and adjust before ramping up.

That said, without a solid mapping between identity groups and GitHub teams (like in D), even a well-paced sync could cause chaos. But at least pacing the sync gives some breathing room to catch issues early on.

Setup should focus on avoiding sync conflicts, so D fits best here.

It’s D because without defining how groups map to teams, the sync can create confusion or conflicts. Manual updates (C) help later but nailing the alignment first is key.

Option C makes sense from a control perspective. Allowing manual updates to team memberships can help handle exceptions or urgent changes that the automated sync might miss. It adds flexibility during the initial setup before everything fully stabilizes. Disabling audit logs or setting infrequent syncs (A and B) could cause issues with tracking or timing, so they don’t seem like top priorities.

D sounds right—making sure identity groups match GitHub teams and roles is key for smooth sync.