GitHub Foundations Intermediate Practice Exam: Medium Difficulty 2025

Your team is working on a feature branch called 'feature-login' and you need to incorporate the latest changes from the main branch before submitting a pull request. You want to maintain a clean, linear commit history. Which approach should you use?

A developer accidentally committed sensitive API keys to a public GitHub repository three commits ago. The commits have not been pushed to the remote repository yet. What is the MOST secure approach to resolve this issue?

Your organization has a repository with multiple collaborators. You need to ensure that all code merged into the main branch has been reviewed by at least two team members and passes all automated tests. Which combination of GitHub features should you implement?

You are managing a repository that receives frequent contributions from external developers. After merging several pull requests, you notice the main branch commit history has become cluttered with many small, incremental commits. For future pull requests, what merge strategy should you configure to maintain a cleaner history while preserving attribution?

A development team uses GitHub Flow for their workflow. A critical bug is discovered in production that needs immediate attention while several feature branches are in progress. What is the BEST practice for handling this scenario?

Your team is conducting a code review on a pull request. The reviewer notices several issues: two minor style inconsistencies and one critical security vulnerability. How should the reviewer use GitHub's pull request review features to provide the most effective feedback?

A project maintainer needs to coordinate work across multiple contributors for an upcoming release. The release involves 8 different features being developed simultaneously, each requiring coordination between frontend and backend work. Which GitHub collaboration feature would BEST help organize and track this complex, multi-contributor effort?

An open-source project receives numerous issues daily, many of which are duplicates or lack sufficient information. The maintainers want to standardize issue submission and automatically label issues based on their content. What combination of GitHub features should they implement?

A company is evaluating GitHub plans for their 50-person development team. They need private repositories, required reviewers, branch protection rules, and code owners. They also want basic support and user management capabilities. Which GitHub plan would meet their minimum requirements most cost-effectively?

Your organization needs to manage access to multiple repositories across different teams. The Data Science team should have write access to data-* repositories, the Frontend team should have write access to ui-* repositories, and the DevOps team should have admin access to all repositories. What is the MOST efficient way to manage these permissions in GitHub?