Domain 3: Repository & Organization Management
GitHub Administration · 60 questions
- What is the maximum number of organization owners GitHub recommends for most organizations?
- What does the 'Billing Manager' organization role allow a user to do?
- How does a CODEOWNERS file affect the pull request review process?
- What is the difference between a repository ruleset and a branch protection rule in GitHub?
- What happens when an organization's repository is forked by a member?
- Which GitHub feature allows organizations to define template repositories that users can use as starting points for new repositories?
- In GitHub, what is the purpose of a team's 'maintainer' role?
- What is the 'internal' repository visibility setting, and which GitHub product supports it?
- What does the 'Archive repository' action do in GitHub?
- How does GitHub's 'Require signed commits' branch protection rule work?
- What is the difference between 'outside collaborators' and 'organization members' in GitHub?
- What is the purpose of GitHub's 'base permissions' setting for an organization?
- How can an organization restrict which users are allowed to create repositories?
- What is the purpose of GitHub's 'mandatory code review dismissal' feature in branch protection?
- What is a GitHub organization's 'fork policy' and what does restricting it accomplish?
- What is the GitHub 'Merge Queue' feature and what problem does it solve?
- How does GitHub handle repository transfers between organizations?
- What is GitHub Copilot Business, and what administrative controls are available for enterprise administrators?
- What is the purpose of a GitHub 'team discussion' feature?
- What happens to forked repositories when the parent repository is deleted?
- What is the 'GitHub Sponsors for companies' feature and how can organizations use it?
- What is the purpose of GitHub's 'saved replies' feature for repository maintainers?
- How do GitHub organization-level secrets differ from repository-level secrets in GitHub Actions?
- What is the 'watch' functionality in GitHub repositories and how does it affect notifications?
- What is the purpose of GitHub's 'Required workflows' feature at the organization level?
- In GitHub, what is a 'milestone' and how is it used for project tracking?
- What is the function of GitHub's 'auto-link references' feature in organizations?
- What does the 'Allow auto-merge' setting in a repository do?
- How does GitHub's 'Require branches to be up to date before merging' protection work?
- What is a GitHub 'project' (GitHub Projects) and how does it differ from issues?
- What is the GitHub 'issue template chooser' and how is it configured?
- What is the purpose of 'GitHub Copilot for Business' and what can administrators control?
- How does GitHub handle the 'inner source' model using repository visibility settings?
- What is the 'repository network' in GitHub and how do forks relate to it?
- What is the GitHub 'Merge Queue' and what problem does it solve?
- What are 'GitHub Actions environments' and how do they provide deployment protection?
- What is the GitHub 'repository transfer' feature and what happens to existing links after transfer?
- What is the GitHub 'organization profile README' and where does it display?
- What is the GitHub 'repository ruleset' status and how does it differ from branch protection rules status?
- What does the 'Restrict deletions' rule in GitHub repository rulesets or branch protection do?
- Compared with classic branch protection rules, what advantage do repository rulesets provide for administrators?
- What is the purpose of setting a repository ruleset enforcement status to 'Evaluate' (when available)?
- Which two uses of repository custom properties are valuable for enterprise administrators? (Choose two)
- What can push rulesets help prevent at the repository or organization level?
- When administering a merge queue for a busy repository, what must typically be true for a pull request to be merged by the queue?
- Why would an administrator create rulesets that apply to tags?
- What is a responsible use of a ruleset bypass list in an organization?
- An enterprise policy prevents members from changing repository visibility. What risk does this primarily reduce?
- How do CODEOWNERS and required reviews commonly work together in a governed repository?
- When an organization renames the default branch across repositories (for example master to main), what administrative concern is most important?
- An organization sets base permissions to 'No permission'. What is the practical effect for members who are not granted access through teams or direct collaborator assignments?
- Why would enterprise or organization administrators restrict who can create repositories?
- Which two outcomes should administrators plan for when transferring a repository to another account or organization? (Choose two.)
- What is the primary effect of archiving a GitHub repository for ongoing development work?
- What does setting a repository or organization ruleset enforcement status to 'Evaluate' (or equivalent non-enforcing mode) allow administrators to do?
- What is the main operational benefit of synchronizing IdP groups to GitHub teams?
- In GitHub Enterprise Cloud with an enterprise account, what does 'internal' repository visibility enable for inner-source practices?
- How can organization or enterprise custom repository properties help administrators govern large repository fleets?
- When administrators rename a repository default branch, which follow-up is most important for enterprise stability?
- An organization restricts forking of private repositories. What risk is this policy primarily intended to reduce?