Question 384 of 823
AZ-400 Develop a security and compliance plan Practice Question
Your team uses GitHub. You need to automatically remove a user's access to all repositories when they leave the company. What is the most efficient approach?
⚠ Common exam trap
Many exam-takers confuse SAML SSO (which only handles authentication) with SCIM (which handles provisioning), leading them to choose SAML as the solution for deprovisioning access.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Enable SCIM provisioning from Microsoft Entra ID to GitHub
SCIM (System for Cross-domain Identity Management) provisioning from Microsoft Entra ID to GitHub automates user lifecycle management. When a user is disabled or removed from Entra ID, SCIM automatically deprovisions their access across all GitHub resources, including repositories, without manual intervention. This is the most efficient approach because it is event-driven and scales to thousands of users.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Assign the user to a 'Leaver' team and remove all repository permissions
Why it's wrong here
Assigning the user to a 'Leaver' team is an ineffective approach because it only changes team membership and does not automatically revoke direct repository-level permissions, organization access, or external collaborators' access, requiring manual follow-up and leaving the user active until an administrator intervenes.
- ✗
Manually remove the user from each repository
Why it's wrong here
Manually removing the user from each repository is inefficient and error-prone, especially in large organizations, because it requires an administrator to identify every repository and permission grant, and it does not handle centralized identity lifecycle events, so the user may retain access if any repository is overlooked.
- ✗
Configure SAML single sign-on (SSO) with Microsoft Entra ID
Why it's wrong here
Configuring SAML SSO with Microsoft Entra ID only enforces authentication at sign-in; it does not automatically remove a user's existing access to GitHub resources after they leave, because SAML lacks provisioning/deprovisioning capabilities—only SCIM can synchronize user status and revoke access automatically.
- ✓
Enable SCIM provisioning from Microsoft Entra ID to GitHub
Why this is correct
Enabling SCIM provisioning from Microsoft Entra ID to GitHub is the correct solution because SCIM automatically creates, updates, and deactivates GitHub user accounts based on Entra ID group membership, so when a user is removed from the source group or disabled in Entra ID, GitHub automatically revokes their access without manual intervention.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jul 4, 2026
This AZ-400 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-400 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.