GH-100 practice question 1 of 15
Your organization is implementing team synchronization. Which of the following should you prioritize during the setup process?
Full set: 65 questionsImplementing team synchronization requires a foundational strategy before any technical configuration. The priority is to establish a clear and logical mapping between the groups in your identity provider (IdP) and the teams within your GitHub organization. This planning phase is critical for ensuring that the correct permissions and access levels are automatically provisioned and maintained. Without this well-defined alignment, the implementation can lead to incorrect access assignments, security vulnerabilities, and operational chaos, defeating the purpose of centralized identity management.
A. Disabling the audit log stream removes essential visibility for security, compliance, and troubleshooting, which is especially critical during a change in identity management.
B. Prioritizing an infrequent sync schedule over accuracy can lead to significant delays in updating permissions, creating security risks from stale access rights.
C. Allowing manual updates on GitHub contradicts the core principle of team synchronization, which is to use the IdP as the single source of truth for membership.
1. GitHub Docs
"Managing team memberships with an identity provider": This document outlines the process of connecting IdP groups to GitHub teams. The entire procedure is predicated on the administrator knowing which IdP group to connect to which GitHub team
reinforcing that this mapping is a prerequisite. The documentation states
"You can connect one IdP group to one GitHub team." This highlights the need for a clear one-to-one alignment strategy.
Reference Section: "Connecting an identity provider group to a team"
2. GitHub Docs
"About team synchronization": This article explains that with team sync
"you can manage repository access for groups of people through your IdP." This capability is only effective if the groups are properly planned and aligned with the intended repository access structures on GitHub.
Reference Section: "About team synchronization"
3. GitHub Docs
"Reviewing the audit log for your organization": The audit log is presented as a key tool for monitoring organization activity
including changes to team membership (team.addmember
team.removemember). Disabling this would be contrary to best practices for security and governance.
Reference Section: "Searching the audit log" and "Team actions"
Keep practicing
Take the free GH-100 practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other GH-100 practice questions
- Question 2Why would someone choose to configure a security policy?
- Question 3Which events from the audit log are exposed by the GraphQL API? Each answer presents a co…
- Question 4You are using GitHub-hosted runners and need to securely deploy to an internal system. Th…
- Question 5You have subscribed to GitHub Premium Support, and you need to submit a support ticket. G…
- Question 6What distinguishes Enterprise Managed Users (EMUs) from standard GitHub accounts?
- Question 7Which of the following is the responsibility of an Organization Owner in GitHub? (Choose …
