GitHub · GH-900
Validates understanding of foundational topics, products, and concepts of collaborating, contributing, and working on GitHub.
Practice Questions
409
≈ 5 practice exams
Duration
100 minutes
Passing Score
700/1000
Difficulty
FoundationalLast Updated
Oct 2026
GH-900 validates everyday GitHub fluency: Git and GitHub fundamentals (25-30%), repositories (10-15%), collaboration (10-15%), modern development (10-15%), project management (5-10%), privacy, security, and administration (10-15%), and the GitHub community (5-10%). These ranges come from the revised blueprint effective January 2026; older fixed-percentage study guides no longer match the exam.
Microsoft lists 100 minutes and a passing score of 700 or greater, with pricing based on the country or region where the exam is proctored. GitHub says the exam has 60 scored multiple-choice questions plus approximately 10-15 unscored pretest questions. There are no formal prerequisites, and the Foundations credential does not require renewal.
Use these 630 questions with a real repository open beside you. Practise branches, commits, pull requests, reviews, issues, discussions, project views, releases, permissions, security features, and community workflows; the exam expects you to choose the GitHub feature or collaboration step that fits a scenario, not merely define vocabulary.
GitHub Foundations (GH-900) validates basic use of Git, repositories, collaboration workflows, project-management features, security and administration concepts, and the GitHub community. It is intended for developers and nondevelopers who need to work effectively on GitHub.
The current seven-domain blueprint took effect in January 2026. It replaces older fixed domain percentages with ranges and adds current platform topics, so candidates should avoid study guides built around the previous outline.
The GitHub Foundations certification is designed for a broad range of GitHub users, including software developers, DevOps engineers, solution architects, app makers, and IT administrators who want a formal credential validating their GitHub proficiency. It is equally suitable for non-technical roles such as project managers, technical writers, and open-source contributors who collaborate on GitHub but may not write code daily.
This certification is particularly valuable for early-career professionals and students looking to establish credibility in collaborative development environments, as well as experienced professionals who use GitHub daily but have never formally validated their skills. Anyone preparing for more advanced GitHub certifications—such as GitHub Actions, GitHub Advanced Security, or GitHub Administration—should consider GH-900 as a natural starting point.
There are no formal prerequisites required to sit for the GitHub Foundations exam. However, candidates are expected to have hands-on familiarity with GitHub's core interface and basic Git operations before attempting the exam. Comfortable navigation of repositories, understanding of commits, branches, and pull requests, and exposure to GitHub's collaboration features (issues, discussions, notifications) will provide a meaningful foundation.
Microsoft Learn recommends completing the official 'GitHub Foundations Part 1' and 'GitHub Foundations Part 2' learning paths before sitting the exam. Candidates who have spent time working on real or practice GitHub repositories—creating branches, submitting pull requests, and reviewing code—will be best positioned to pass without additional study.
Microsoft lists 100 minutes and a passing scaled score of 700 or greater. GitHub states that the exam includes 60 scored multiple-choice questions plus approximately 10-15 unscored pretest questions. Pricing varies by country or region, and delivery is through Pearson VUE.
There are no formal prerequisites. Under GitHub's current certification policy, Foundations does not require renewal.
GitHub Foundations demonstrates practical literacy with the collaboration platform used by many software teams. It is useful to developers, testers, project contributors, technical writers, administrators, and other roles that work with repositories, issues, pull requests, projects, or GitHub security settings.
It also provides a base for the role-focused GitHub Administration, GitHub Actions, GitHub Copilot, and GitHub Advanced Security certifications.
5 sample questions with answers and explanations. The full bank has 409 questions, enough for 5 full-length practice exams.
Preview — answers shown1. TechFlow Industries is training their team on Markdown shortcuts for faster documentation. The documentation manager wants to teach slash command usage. What slash command inserts a code block in Markdown?
Explanation
The /code slash command is used for adding a code block in Markdown. Slash commands provide quick shortcuts for common formatting tasks, and /code specifically creates a formatted code block that displays text in a monospace font with syntax highlighting when appropriate. /md, /block, and /syntax are not valid slash commands for inserting code blocks. The /code command is part of GitHub's enhanced Markdown interface that provides convenient shortcuts for formatting content quickly.
2. DataFlow Analytics has a new developer who needs to learn Git commands. The team lead wants to show them how to access Git's built-in documentation. What Git command provides information about how to use Git?
Explanation
The git help command provides information about how to use Git, including detailed documentation about Git commands, their options, and usage examples. You can use git help followed by a specific command name to get detailed help for that command, or just git help to see general Git usage information. Git info, git docs, and git manual are not valid Git commands. The help system is built into Git and provides comprehensive documentation without requiring internet access.
3. VersionControl Specialists is training their team on Git file states. A developer asks about a file that has been changed since the last commit but hasn't been added to the staging area yet. What state is this file in?
Explanation
A file that has been changed since the last commit but hasn't been staged is in the Modified state. In Git, tracked files can be in three substates: Unmodified (unchanged since last commit), Modified (changed but not staged), and Staged (changed and added to staging area). The file must be staged using git add before it can be committed.
4. StartupHub is onboarding new developers and needs to teach them essential Git commands. A new team member asks how to create a brand new Git repository for a project they're starting from scratch. Which command should they use?
Explanation
The git init command is used to initialize a brand new Git repository in an existing directory or create a new repository from scratch. When you run git init in a directory, it creates a hidden .git subdirectory that contains all the necessary files and metadata for version control. This transforms a regular directory into a Git repository, allowing you to start tracking changes to files. The git clone command is used to copy an existing remote repository to your local machine, while git create and git new are not valid Git commands. For starting a completely new project with version control, git init is the correct choice.
5. InnovateLabs has multiple developers working on the same project. They need to regularly get the latest changes from other team members into their local repositories. What command should they use to download and integrate remote changes?
Explanation
The git pull command downloads changes from a remote repository and automatically merges them into your current local branch. This is essentially a combination of two operations: git fetch (which downloads the changes) and git merge (which integrates them into your current branch). Pulling is the standard way to stay up to date with changes made by other team members. It ensures your local repository reflects the latest state of the shared project. Git download, git sync, and git update are not valid Git commands. Regular pulling helps prevent conflicts and keeps everyone working with the most current version of the codebase.
GitHub says there are 60 scored multiple-choice questions plus approximately 10-15 unscored pretest questions.
Microsoft lists 100 minutes for the proctored assessment.
A scaled score of 700 or greater passes.
Yes. A revised seven-domain blueprint took effect in January 2026, so older guides with fixed domain percentages are outdated.
No. The exam is intended to validate foundational GitHub knowledge and has no formal prerequisite.
No renewal is required for GitHub Foundations under GitHub's current certification policy.
$17.99
One-time access to this exam