GitHub Foundations Exam Guide: What to Study, How to Prepare, and When to Schedule
GitHub Foundations validates beginner-level knowledge of GitHub concepts, products, and ways of collaborating, contributing, and working on the platform. It is intended for non-developers, developers, administrators, and other GitHub users who need a reliable foundation rather than an advanced programming credential. This guide helps you decide whether your current experience is sufficient, which exam domains deserve the most study time, how to use Microsoft’s preparation resources, and when to schedule Exam GH-900 through Pearson VUE.
What does the GitHub Foundations certification validate?
GitHub Foundations validates practical understanding of GitHub fundamentals: Git and version control, repositories, collaboration, project management, modern development practices, privacy and security, administration, and the GitHub community. It is not presented as an advanced developer exam. The official audience includes GitHub users who want to demonstrate foundational proficiency across the platform.
The associated assessment is Exam GH-900: GitHub Foundations. Microsoft describes the certification as beginner level and identifies it with Administrator, App Maker, Developer, DevOps Engineer, and Solution Architect roles. Those role labels do not mean that candidates must already work in one of those jobs; they indicate contexts in which a GitHub foundation can be useful.
The credential is a sensible target when you need a structured way to confirm that you understand how GitHub supports source control and teamwork. It is less suitable as a substitute for role-specific expertise in software architecture, advanced administration, security engineering, or complex automation. Use the official skills outline to determine whether the exam matches the capability you need to prove.
Who should take GH-900?
GH-900 is designed for non-developers, developers, and other GitHub users who want greater proficiency with GitHub fundamentals. A candidate should have foundational knowledge of Git, repositories, collaboration tools, project management, and modern development practices. The exam can therefore serve both technical newcomers and people who contribute to software work without writing most of the code.
For a developer or aspiring developer, the certification can organize knowledge that is often learned informally: repositories, commits, branches, pull requests, and the flow from proposed change to collaboration. For an administrator or DevOps-oriented learner, it provides a platform-level foundation before deeper work with governance, automation, or delivery practices.
For a project manager, product contributor, technical writer, student, or operations professional, the value is understanding how work is represented and discussed in GitHub. Issues, discussions, projects, notifications, and Markdown are not merely developer tools; they are parts of the collaboration model that the preparation resources expose.
Do not treat the beginner label as permission to skip the basics. A candidate who has only read definitions may struggle to distinguish related concepts in a scenario. Before scheduling, confirm that you can explain how the concepts fit together and can navigate the relevant GitHub features without relying on memorized answer patterns.
Which skills and domains are measured?
The January 2026 skills outline organizes GH-900 into seven domains. The largest stated domain is Understand Git and GitHub basics at 25–30% of the exam. Work with GitHub repositories is 10–15%, Collaborate using GitHub is 10–15%, Apply modern development practices is 10–15%, Manage projects with GitHub is 5–10%, Understand privacy, security, and administration is 10–15%, and Explore the GitHub community is 5–10%.
Understand Git and GitHub basics at 25–30% of the exam covers the foundation on which the other domains depend. The study guide identifies version-control fundamentals, the distinction between Git and GitHub, repositories, commits, branches, GitHub accounts and organizations, GitHub Flow, Markdown, GitHub Desktop, and GitHub Mobile as areas that may be assessed.
Work with GitHub repositories at 10–15% of the exam focuses on repository management. Prepare to reason about how a repository is used as a home for project content and collaboration rather than learning isolated vocabulary. Read the detailed bullets in the current study guide because the bullets illustrate assessment coverage and related topics may also appear.
Collaborate using GitHub at 10–15% of the exam requires more than knowing that collaboration exists. Connect the objects and actions: a proposed change, review or discussion, communication, and the resulting contribution. The official course describes GitHub Flow, issues, discussions, notifications, subscriptions, branches, commits, pull requests, and merging as part of the foundational learning experience.
Apply modern development practices at 10–15% of the exam is a reason to study the platform’s current development capabilities rather than only classic Git commands. The Microsoft Learn path includes modules on code scanning, GitHub Actions, GitHub Copilot, and GitHub Codespaces. Study each feature as a way of supporting development work, while checking the current study guide for the exam’s precise scope.
Manage projects with GitHub at 5–10% of the exam covers the project-management side of GitHub. Microsoft Learn’s learning path includes GitHub Projects, including issues, tasks, relationships, custom fields, and conversations. The smaller published range does not make the domain optional; it is a contained area that can become a useful source of marks after the larger fundamentals are secure.
Understand privacy, security, and administration at 10–15% of the exam should be studied as a governance domain, not as a list of unrelated settings. Build a clear mental model of who can access or manage work, how collaboration is controlled, and how security-oriented features fit into development. Use the current study guide rather than assuming that every GitHub plan or preview feature is assessed identically.
Explore the GitHub community at 5–10% of the exam completes the published outline. This domain reflects the broader community and contribution context around GitHub. Review the official domain bullets and related Microsoft Learn material, then test whether you can recognize the appropriate community-oriented concept in a situation rather than simply recalling its name.
The percentages describe the exam blueprint, not a guaranteed question count or a promise that every subtopic will appear in a fixed proportion. Microsoft notes that the bullets under each skill illustrate how the skill is assessed and that related topics may be covered. Most questions concern generally available features, although commonly used preview features may also appear.
How should you turn the blueprint into a study order?
Study in dependency order, not in the order of whichever feature looks most interesting. Start with Git and GitHub basics, then connect repositories to collaboration, add modern development practices, study project management, and finish with governance and community review. Use the domain ranges to allocate attention, but do not ignore a smaller domain simply because its published range is lower.
A practical sequence is: first establish the Git vocabulary; next follow a complete GitHub Flow; then examine repository and collaboration controls; after that review Projects and modern development features; finally consolidate privacy, security, administration, and community topics. This sequence reduces the risk of memorizing product names without understanding where each fits in day-to-day work.
Keep a single study table with four columns: domain, concept, evidence of understanding, and unresolved question. In the evidence column, write an explanation or workflow in your own words. In the unresolved-question column, record distinctions that you repeatedly confuse. This turns the official outline into a revision instrument instead of a checklist that can be marked complete too early.
Treat the official study guide as the authority for the current assessed scope. Its January 2026 outline is the basis for the domain weights cited above, and its update notes matter because GitHub features and exam coverage can change. Avoid building a plan from an old blog post, an unverified question bank, or a course whose version is not clear.
A useful decision rule for allocating time
Give the first study block to Understand Git and GitHub basics at 25–30% of the exam because it is both the largest domain and the vocabulary foundation for the rest. Then give comparable focused blocks to Work with GitHub repositories at 10–15% of the exam, Collaborate using GitHub at 10–15% of the exam, Apply modern development practices at 10–15% of the exam, and Understand privacy, security, and administration at 10–15% of the exam.
Reserve a shorter but deliberate review for Manage projects with GitHub at 5–10% of the exam and Explore the GitHub community at 5–10% of the exam. This is a practical recommendation, not an official timetable. If your work already involves repositories but not Projects or security controls, reverse the emphasis after an initial diagnostic.
Which official learning resources should you use?
Start with Microsoft Learn’s GH-900 study guide and certification page, then use the linked learning options to close specific gaps. The study guide explains the purpose of the document, the domains, updates, and additional resources. The certification page provides the exam sandbox and practice assessment. These resources should anchor preparation because they come from the certification owner.
The GitHub Foundations Learning Path Part 1 of 2 contains 8 Modules and is marked for beginner and intermediate learners. Its modules include Introduction to Git, Introduction to GitHub, Introduction to GitHub’s products, code scanning, GitHub Copilot, GitHub Codespaces, GitHub Projects, and Markdown. Use the path to build breadth, but map each module back to the GH-900 domains rather than assuming that completing a module proves exam readiness.
Microsoft also offers the course GH-900T00-A: GitHub Foundations. The course page describes it as a beginner course and states that preparation can be instructor-led or self-paced. It lists a course duration of 2 days. The course is useful if you prefer guided sequencing, but the stated duration is a course description, not a claim that every candidate can become exam-ready in that time.
The course syllabus emphasizes repository management, commits, branches, merging, GitHub Flow, issues, discussions, notifications, and subscriptions. Use those topics to create a small working model of collaboration. For instance, explain what happens when a contributor makes a change on a branch, proposes it, receives feedback, and merges the accepted work. The purpose is understanding the relationship between features, not reproducing a fictional project.
Use Microsoft Learn’s separate learning path when you need additional practice with the platform concepts. It introduces Git, GitHub features, products, code scanning, Copilot, Codespaces, Projects, and Markdown. The path also explains that Codespaces provides a fully configured development environment hosted in the cloud and that a workspace can be available from any computer with internet access. Treat those descriptions as conceptual study material, not as a promise that every exercise is required for the exam.
How can hands-on practice improve readiness?
Hands-on work is most useful when it answers a specific conceptual question. Create or use a safe practice repository, make a small change on a branch, record a commit, open a pull request, add discussion, and observe how the work is represented. Then review an issue, connect work to a project, and use Markdown to communicate clearly. This gives abstract terms a visible relationship.
Do not attempt to recreate an enterprise environment. A small repository is enough to practice the flow of work and to compare the roles of repository content, issues, pull requests, discussions, and project views. Keep personal material out of the exercise if you are using an account associated with work or school, and avoid changing settings in repositories you do not control.
Use the learning path’s feature coverage to choose targeted exercises. For modern development practices, read about code scanning, GitHub Actions, Copilot, and Codespaces and record the problem each feature addresses. For project management, create a simple task relationship or custom field only if the learning environment permits it. The goal is to recognize purpose and placement, not to produce a portfolio application.
After each exercise, close the browser and describe the workflow from memory. Then reopen the relevant documentation and correct the explanation. This is more revealing than copying a tutorial. If you cannot explain why a feature would be selected in a scenario, return to the concept and perform a smaller exercise.
Microsoft provides an exam sandbox that lets candidates experience the exam interface and interact with question types used in the exam. Use it before the final readiness check. The sandbox is not a source of live exam questions and should not be treated as one; its practical purpose is to reduce uncertainty about the interface and interaction style.
How should you use practice assessments?
Use the official practice assessment as a diagnostic, not as a replacement for study. Microsoft says practice assessments provide an overview of likely question style, wording, and difficulty and help candidates identify preparation needs. Review every missed or uncertain item, classify the underlying domain, and study the concept that caused the error instead of memorizing the selected response.
Take a first practice assessment after you have reviewed the outline and completed enough learning to recognize the main concepts. Record three results for each item: confident and correct, uncertain and correct, or incorrect. The second category matters because a lucky answer does not demonstrate readiness. Revisit those concepts before relying on the result to make a scheduling decision.
Build a gap list using the official domain names. A gap such as “GitHub is confusing” is too broad to act on. Replace it with a precise statement such as “I cannot distinguish the purpose of a branch from the purpose of a repository” or “I cannot explain how project-management items relate to repository work.” Then use the study guide or Microsoft Learn module that addresses the distinction.
Do not infer a passing threshold from an unofficial practice score. The official study guide states that a score of 700 or greater is required to pass the certification exam, but practice assessments are preparation tools rather than the certification result. Make the scheduling decision only after you can explain your weak areas and have confirmed the current exam information on Microsoft Learn.
What exam delivery details should you confirm?
The GitHub Foundations assessment is proctored, may include interactive components, and gives candidates 100 minutes to complete the assessment. Microsoft directs candidates to schedule through Pearson VUE. Confirm the current appointment and delivery information through the official certification page rather than assuming that a previous booking experience or third-party listing still applies.
The exam is offered in English, Spanish, Portuguese (Brazil), Korean, and Japanese. Microsoft notes that localized versions may not always be updated on the same schedule as the English version and that localized updates can differ. If the exam is not available in your preferred language, the study guide says you can request an additional 30 minutes. Check the current accommodation and scheduling instructions before booking.
Microsoft strongly recommends registering with a personal Microsoft account. If you use an organizational work or school account, your exam records may be lost and unrecoverable if you leave that organization. This is an important administrative decision to make before scheduling, especially for students, contractors, and employees whose account access may change.
The certification page says that price is based on the country or region in which the exam is proctored. Do not use a price from another country as your expected fee. Review the official scheduling path for the amount applicable to your location and any available appointment choices.
Pearson VUE’s test-centre locator instructs candidates to select their exam programme and search for available test centres by location. Use the locator if a test-centre appointment is your preferred route. Pearson VUE’s programme login directory is also available for test-taker access, but Microsoft’s certification page remains the appropriate starting point for the GH-900 scheduling workflow.
If you require assistive devices, extra time, or a modification to the exam experience, request an accommodation through the official process before the appointment. Do not wait until the assessment begins. Record the approved arrangement and check that it is reflected in the booking details.
What should you check before paying or booking?
Confirm the exam identifier, language, delivery option, account used for registration, regional price, appointment location, and accommodation status. Also review the current study guide because Microsoft provides update information and warns that localized versions may lag behind the English version. These checks prevent an avoidable administrative problem from becoming a preparation problem.
What does a realistic study roadmap look like?
A practical roadmap uses four phases: establish the baseline, learn the core workflow, extend into products and governance, and verify readiness. The exact calendar depends on prior GitHub experience, so use the sequence rather than an invented promise about how quickly every candidate can prepare. Set a review checkpoint after each phase and change the plan when evidence shows a gap.
Phase one is orientation. Read the certification page and the current GH-900 study guide, copy the seven domain names into your study table, and mark each as strong, developing, or unfamiliar. Confirm the meaning of Git, GitHub, repository, commit, branch, and pull request in your own words. Finish this phase by identifying which domain is most likely to consume extra study time.
Phase two is the core workflow. Work through Introduction to Git and Introduction to GitHub in the Microsoft Learn path. Follow a small change from branch to commit to pull request and merging, and practice communicating with Markdown. Add notes about accounts, organizations, GitHub Flow, issues, discussions, notifications, GitHub Desktop, and GitHub Mobile as they appear in the learning materials.
Phase three broadens the platform view. Study repository management, collaboration, GitHub Projects, and modern development features. Review code scanning, GitHub Actions, GitHub Copilot, and Codespaces from the official learning resources. Then study privacy, security, and administration and the GitHub community. For each feature, answer three questions: what problem does it address, where does it fit, and which GitHub object or workflow does it affect?
Phase four is verification. Take the official practice assessment, analyze uncertain and incorrect answers, revisit the corresponding modules, and use the exam sandbox. Repeat the diagnostic only after correcting the knowledge gaps. Schedule when your explanations are consistent across the domains and you have checked the current official exam details—not merely when you have finished watching lessons.
The roadmap should remain flexible. Someone who already manages repositories may shorten the repository review and spend more time on governance or modern development practices. Someone new to Git should do the opposite. The blueprint gives a shared scope; your practice evidence determines the order and depth.
Which preparation mistakes create avoidable risk?
The most damaging mistake is studying isolated feature names without connecting them to a workflow. GH-900 covers collaboration, repositories, projects, modern development, and governance as related areas. Build explanations that show when a feature is used and what it changes. This approach is more durable than copying definitions from a question bank.
Do not mistake course completion for exam readiness. Microsoft Learn’s course and learning path are useful preparation resources, but finishing a module does not prove that you can distinguish similar concepts under assessment conditions. After each module, write a short explanation from memory and test it with a practical example or a comparison table.
Do not overfocus on Git commands while neglecting GitHub’s collaboration and administration model. Git is part of the foundation, but the assessed domains also include projects, privacy, security, administration, modern development practices, and the community. A command-line-only plan leaves important platform concepts unexamined.
Do not treat a single practice result as a guarantee. Review uncertain correct answers, check the domain behind each error, and look for patterns. A candidate who repeatedly misses the same distinction needs targeted study, even if an overall practice attempt appears encouraging.
Do not rely on exam dumps, leaked questions, or memorization as a preparation strategy. They cannot establish that you understand the platform, may be inaccurate or outdated, and do not replace authorized learning. Practice with concepts, workflows, the official assessment materials, and the sandbox instead.
Do not schedule with an organizational Microsoft account simply because it is convenient. Microsoft specifically recommends a personal MSA account and warns about the loss of exam records if an organizational account becomes unavailable. Resolve the account decision before you select an appointment.
Do not assume every visible GitHub feature is equally relevant or permanently in scope. The study guide says most questions cover generally available features and may include commonly used preview features. Use the current outline and linked resources to determine what to study, rather than treating the entire GitHub product surface as examinable.
Do not ignore language and accommodation planning. The listed exam languages, localization timing, additional-time guidance, and accommodation process affect scheduling decisions. Check them early enough to make an informed appointment choice.
How should you decide whether to schedule now?
Schedule only when you can explain the major GitHub workflows without notes, identify your weaker domains, and have used the official practice and sandbox resources to address those gaps. The decision should be based on evidence of understanding and confirmed appointment conditions, not on a fixed number of study days or confidence generated by memorizing practice answers.
Use this final checklist: explain Git versus GitHub; describe repositories, commits, branches, and pull requests; trace a basic GitHub Flow; identify the roles of issues, discussions, notifications, and projects; summarize the purpose of modern development features in the learning materials; explain the purpose of privacy, security, and administration controls; and recognize the community context of GitHub work.
Then verify the administrative items: current Exam GH-900 details, language, regional price, personal Microsoft account, Pearson VUE route, appointment location or delivery option, and any accommodation. Microsoft states that the assessment is proctored and may contain interactive components, so complete the exam sandbox before the appointment.
The official passing requirement is a score of 700 or greater. That threshold is useful for understanding the result standard, but it should not become a reason to chase an unofficial prediction. Your stronger indicator is whether you can reason through unfamiliar wording by applying the concepts and relationships in the study guide.
If you fail, Microsoft states that a retake is available 24 hours after the first attempt, while later retake intervals vary under the retake policy. Treat a retake as a new diagnostic opportunity: obtain the score report, identify the domains needing attention, and change the study plan before booking again.
What should you do after choosing GitHub Foundations?
Make the official Microsoft Learn certification page and GH-900 study guide your two control documents. Use the learning path or course to build knowledge, the sandbox to understand the interface, and the practice assessment to expose gaps. Before scheduling, recheck language, account, accommodation, delivery, and regional pricing details through the official links.
A good next action is to create the domain table today and complete a short baseline review. Mark the seven domains honestly, begin with Git and GitHub basics, and write down the questions you cannot yet answer. Progress from definitions to a complete collaboration workflow, then broaden into Projects, modern development practices, governance, and community topics.
For candidates who are ready to book, use Microsoft’s Schedule Exam route to Pearson VUE and register with a personal Microsoft account. For candidates who are not ready, schedule a review checkpoint instead of an exam appointment. The purpose of the checkpoint is to decide from evidence whether the remaining gaps are small, understood, and fixable before test day.
Conclusion
GitHub Foundations is best approached as a platform-literacy assessment, not a memorization exercise. The January 2026 outline gives the scope, Microsoft Learn supplies the study material and practice environment, and Pearson VUE handles the scheduling path. Build from Git and GitHub basics into repositories, collaboration, modern development, projects, governance, and community concepts. When you can explain those relationships and have verified the current delivery details, you can make a responsible decision about scheduling Exam GH-900.
Related exams
- GitHub-Actions exam — GitHub Actions Certificate Exam
- GitHub-Advanced-Security exam — GitHub Advanced Security GHAS Exam
- GitHub-Copilot exam — GitHub CopilotCertification Exam
