Your organization is implementing team synchronization. Which of the following should you prioritize during the setup process?

Question

Options

• ADisabling the audit log stream
• BSetting an infrequent sync schedule to reduce performance impact
• CAllowing manual updates to team memberships
• DClearly define how identity provider groups will align with GitHub teams and roles

• A
  11% (3)
• B
  7% (2)
• C
  4% (1)
• D
  78% (21)

Explanation

Mapping identity provider (IdP) groups to GitHub teams and roles before enabling sync is the foundational step - without a clear mapping strategy, sync will create chaos: teams may be over-provisioned, under-provisioned, or inherit incorrect permissions. Option A is wrong because disabling the audit log stream removes visibility into sync events, which is critical for troubleshooting and compliance. Option B is wrong because sync schedules should align with your security requirements (typically frequent enough to reflect offboarding promptly), not be set arbitrarily infrequent. Option C is wrong because allowing manual membership changes directly conflicts with the purpose of automated sync - IdP becomes the source of truth, and manual edits will be overwritten or create drift.

Memory tip: Think of team sync like a pipeline - you must design the mapping before turning on the tap, or you'll flood the wrong rooms.

No community discussion yet for this question.