GH-100 · Question #30
Which THREE of the following accurately describe how the SCIM protocol enhances user management in GitHub Enterprise Cloud? (Choose three.)
The correct answer is A. SCIM synchronizes changes to user attributes from the identity provider to GitHub. B. SCIM deactivates GitHub accounts when users are deleted from the identity provider. Note: The stated answer appears truncated - the question requires three selections, and the correct answers are A, B, and D. --- A, B, and D are correct because they describe SCIM's core lifecycle management functions: it provisions new accounts when users are added to the…
Question
Which THREE of the following accurately describe how the SCIM protocol enhances user management in GitHub Enterprise Cloud? (Choose three.)
Options
- ASCIM synchronizes changes to user attributes from the identity provider to GitHub.
- BSCIM deactivates GitHub accounts when users are deleted from the identity provider.
- CSCIM automatically deletes organization repositories when administrators are removed.
- DSCIM automates user provisioning when new users are added to the identity provider.
- ESCIM generates authentication tokens for accessing GitHub's REST API.
- FSCIM configures repository permissions based on user roles within the organization.
How the community answered
(44 responses)- A86% (38)
- C2% (1)
- D7% (3)
- E5% (2)
Explanation
Note: The stated answer appears truncated - the question requires three selections, and the correct answers are A, B, and D.
A, B, and D are correct because they describe SCIM's core lifecycle management functions: it provisions new accounts when users are added to the identity provider (D), syncs attribute changes (like name or email) in real time (A), and deprovisions accounts by suspending or deactivating them when users are removed (B). Together these automate the full user lifecycle without manual GitHub admin intervention.
C is wrong because SCIM manages users, not repository resources - removing an admin never triggers repository deletion, which would be a destructive and unintended side effect.
E is wrong because authentication token generation is handled by OAuth, personal access tokens, or GitHub Apps - not SCIM, which is a provisioning protocol, not an authentication mechanism.
F is wrong because SCIM does not control repository permissions; that's governed by GitHub's own role and team system, not the provisioning layer.
Memory tip: Think of SCIM as an HR system integration - it hires (provisions), updates job titles (syncs attributes), and fires (deprovisions) accounts. It has no authority over what projects (repositories) exist or who can push code.
Topics
Community Discussion
No community discussion yet for this question.