GitHub Administration Intermediate Practice Exam: Medium Difficulty 2025

Your organization is migrating to GitHub Enterprise Cloud. Leadership wants all repositories to follow a baseline policy: require pull requests, require status checks, and restrict who can dismiss reviews. The policy must be centrally managed and automatically applied to current and future repositories without manual per-repo configuration. What should you implement?

An enterprise has multiple organizations. They want to allow employees to authenticate with SAML SSO, and also want to ensure membership and access are removed when an employee leaves the company. The solution should minimize manual user lifecycle work for org admins. What should you configure?

Your enterprise needs separate organizations for different business units, but executives want consistent oversight of security posture (e.g., visibility into risky repositories, configuration drift, and dependency risk) across all orgs. Which approach best meets this requirement?

A regulated team uses GitHub Enterprise Cloud and must ensure that only approved IP ranges can access organization resources via the web UI and Git operations. What should the GitHub admin configure?

A platform team wants to standardize repository creation for dozens of teams. New repositories must include a consistent set of files (CODEOWNERS, security policy, issue templates) and the same default branch protections. Teams should self-serve without admin intervention. What is the best solution?

A repository has sensitive code. Only a small group should be able to push to protected branches, while the broader engineering team should still be able to open pull requests and comment. What is the most appropriate configuration?

A company frequently works with contractors who need temporary access to a single private repository. The company wants to avoid adding them as full organization members, but still needs auditing and the ability to quickly remove access when the contract ends. What should you use?

Your security team wants to reduce the risk of credential leaks and ensure any secrets committed to repositories are detected quickly. They also want developers to be blocked from pushing known secrets where possible. What should you enable/configure?

A repository contains a critical deployment workflow. The organization wants to ensure that deployments to production can only run after an approval by a designated team, and that the approval requirement is enforced consistently. What should you use?

You need to integrate GitHub with a SIEM so that security analysts can monitor important events such as org-level configuration changes, repository visibility changes, and authentication-related events. The integration should be near real-time and centrally managed. What should you configure?