GitHub-Foundations
GitHub FoundationsExam
GitHub Foundations Exam Guide: What to Study and How to Plan Your Attempt
GitHub Foundations validates beginner-level understanding of GitHub, Git, repositories, collaboration, project management, modern development practices, privacy, security, administration, and the GitHub community. It serves non-developers, developers, administrators, and other GitHub users who need a structured foundation rather than an advanced programming credential. This guide helps you decide whether your current experience is sufficient, which domains deserve the most study time, how to use Microsoft’s preparation resources, and when to schedule Exam GH-900.
What the GitHub Foundations certification validates
The certification tests whether you can recognize and use the foundational concepts behind working on GitHub, not whether you can build a complex application. Microsoft describes the audience as GitHub users seeking proficiency with collaborating, contributing, and working on GitHub. The certification page lists the level as Beginner and associates it with Administrator, App Maker, Developer, DevOps Engineer, and Solution Architect roles.
This makes the exam useful for candidates whose work touches repositories, issues, pull requests, projects, or GitHub administration but who do not yet need a specialist credential. A developer may use it to organize existing knowledge. A project or operations professional may use it to establish a shared vocabulary with development teams. A student or career changer may use it as a structured first target.
The official audience profile expects foundational knowledge of GitHub and its core features, including Git, repositories, collaboration tools, project management, and modern development practices. Treat that profile as a readiness description rather than a claim that extensive professional experience is required. The official pages do not state a mandatory prerequisite.
Which skills carry the most exam weight
The January 2026 skills outline gives the largest range to Understand Git and GitHub basics, at 25–30% of the exam. Study that domain first, but do not ignore the remaining domains: the outline covers seven areas that together define the exam’s foundation-level scope.
The official domain ranges are Understand Git and GitHub basics (25–30%), Work with GitHub repositories (10–15%), Collaborate using GitHub (10–15%), Apply modern development practices (10–15%), Manage projects with GitHub (5–10%), Understand privacy, security, and administration (10–15%), and Explore the GitHub community (5–10%). Keep each percentage attached to its named domain when planning study time; the figures are not interchangeable labels for difficulty.
The study guide explains that the bullets beneath each measured skill illustrate assessment coverage and that related topics may also appear. It also notes that most questions cover generally available features, although preview features may be included when they are commonly used. Use the outline as a map, not as a promise of exact question wording or a complete list of questions.
Turn the weights into a study order
Begin with Git and GitHub basics because Understand Git and GitHub basics is the 25–30% domain. Then study repositories, collaboration, modern development practices, and privacy, security, and administration because each is assigned 10–15%. Finish with project management and community topics, while still reserving enough review time for them because their ranges are 5–10%.
This is a practical recommendation, not an official required sequence. If your work already involves Git and pull requests, you may move more quickly through the first domain and spend that time on security, administration, or Projects. If you are new to Git, keep the first domain at the center of your plan even if the interface feels familiar.
What to learn about Git and GitHub basics
You should be able to explain why version control is used, distinguish Git from GitHub, and identify the roles of repositories, commits, and branches. The study guide also points to GitHub accounts, organizations, enterprise options, GitHub Flow, Markdown in issues and pull requests, and when GitHub Desktop or GitHub Mobile is appropriate.
Do not learn these terms as isolated definitions. Build a simple chain: a repository contains project history; a commit records a change; a branch provides a line of work; a pull request supports review and discussion before changes are integrated. Then connect that chain to GitHub as the platform where people collaborate around Git-based work.
Review account, organization, and enterprise concepts as distinct levels of GitHub use. Your goal is to recognize why a team might organize repositories and people under an organization and how enterprise options fit a larger administrative context. Avoid assuming that a product label automatically tells you which permissions or features are available; verify current details in the Microsoft Learn material.
Markdown deserves practical attention because the outline places it in the basics domain. Practice making a clear issue or pull request description with headings, links, lists, code formatting, and task checkboxes. This is more useful than memorizing syntax without considering how the rendered message helps another contributor understand the change.
The learning path includes Introduction to Git and Introduction to GitHub modules. Use the first to establish source-control vocabulary, then use the second to connect issues, notifications, branches, commits, and pull requests. That sequence reduces a common mistake: studying Git commands without understanding the collaborative workflow they support.
How to prepare for repositories and collaboration
Repository and collaboration questions are easier when you can follow a change from creation to review. Practice describing repository management, branch-based work, commits, pull requests, issues, discussions, notifications, and subscriptions as parts of a working process rather than unrelated GitHub screens.
Create a small personal repository or use an appropriate learning exercise. Make a change on a branch, commit it with a meaningful message, and inspect how the change is proposed for review. If you can safely do so, open a pull request, add explanatory Markdown, review the comparison, and follow the notification generated by the activity. The exercise is a preparation recommendation, not a simulation of the exam.
When reviewing collaboration, ask what problem each feature solves. Issues can capture and track work. Discussions support conversation where a formal code change is not necessarily the immediate goal. Pull requests organize proposed changes and review. Notifications and subscriptions help a participant follow activity without treating every repository event as a direct task.
A useful study note has three columns: feature, purpose, and decision. For example, record the purpose of an issue, then write when you would use it instead of opening a pull request. This forces you to compare tools by their intended use, which is safer than relying on visual familiarity with the GitHub interface.
The official course overview specifically includes repository management, commits, branches, merging, the GitHub flow, issues, discussions, notifications, and subscriptions. Work through those topics in that order, then revisit any feature you can name but cannot explain in a realistic collaboration scenario.
The collaboration mistake to avoid
Do not treat a pull request as merely a place to upload files. A sound explanation includes the branch or proposed change, the comparison with the target branch, review or discussion, and the eventual merge decision. Similarly, do not assume that every issue is a code defect; issues can support broader work tracking and communication.
How to cover modern development practices without overstudying
The modern development practices domain is 10–15% of the exam, and the official learning path includes code scanning, GitHub Actions, GitHub Copilot, and GitHub Codespaces. Study what each capability is intended to do, how it fits a development workflow, and which problem it addresses rather than trying to become an expert in every configuration detail.
Code scanning is presented in the learning path as a capability that can be implemented with CodeQL, third-party tools, and GitHub Actions. Your preparation should connect scanning with identifying code issues during development. Compare the roles of the scanning capability, the analysis technology, and the automation mechanism so that their names do not blur together.
The same path describes GitHub Copilot as an AI-powered coding assistant that can help generate, understand, refactor, and debug code through inline suggestions and conversational interaction in a development environment. Focus on its purpose and appropriate place in a workflow. Do not treat familiarity with generated code as a substitute for reviewing or understanding that code.
Codespaces is described as a fully configured development environment hosted in the cloud. The official material explains that a workspace and configured development environments can be available from any computer with internet access. Learn the access and environment concept, but do not infer that every repository or plan has identical configuration or permissions.
GitHub Actions should be studied as part of automation and as a component used by other GitHub capabilities in the official learning material. At this level, be able to explain why a team might automate a development task and how that automation relates to repository work. Use current Microsoft Learn content for feature details because product behavior and availability can change.
How to study Projects, security, and administration
Projects receives 5–10% of the exam, while privacy, security, and administration receives 10–15%. Learn Projects by using it to represent work and relationships between work items. Learn security and administration by separating visibility, access, protective controls, and organizational governance instead of memorizing a long list of settings.
The official learning path describes GitHub Projects as a way to create issues, break them into tasks, track relationships, add custom fields, and have conversations. Build a small planning board or table around a hypothetical feature. Start with an issue, split it into tasks, identify a relationship, and decide which custom field would make progress easier to understand.
For privacy and security, make a comparison sheet of repository visibility, user or team access, and security-oriented capabilities. Add administration as a separate column. The exam outline names the domain broadly, so use the detailed current study guide and linked learning resources to determine which feature explanations you still need. Do not turn an unverified assumption about a plan or permission into a study rule.
A strong answer in this area usually begins with the outcome: who can see the work, who can change it, how risk is identified or reduced, and who administers the setting. When you encounter a feature, write that outcome beside it. This method is more durable than copying interface labels that may be rearranged.
The learning path includes Configure code scanning on GitHub and Manage your work with GitHub Projects. These modules are useful companions to the exam outline because they connect modern development, security, and project-management concepts to practical GitHub workflows.
A security preparation boundary
Foundations preparation should establish correct concepts, not encourage experimentation with sensitive repositories or organizational settings. Use a personal or approved practice repository, avoid exposing credentials or proprietary code, and never enable a security feature in a workplace organization without authorization. Those are practical safeguards, not additional Microsoft exam requirements.
What the GitHub community domain requires
Explore the GitHub community is 5–10% of the exam, so it should be a deliberate review topic rather than an afterthought. Prepare to recognize how GitHub users participate in and communicate around projects, and connect community behavior with respectful, useful contribution.
Use the official study guide to identify the current examples and related topics within this domain. Then review how issues, discussions, pull requests, documentation, and Markdown support communication. A candidate who can explain the purpose of these channels will be better positioned than one who simply memorizes their names.
Keep this domain distinct from collaboration mechanics. Collaboration asks how work moves through GitHub; community study asks how people communicate, contribute, and participate around GitHub projects. The same feature may support both, but your notes should explain the different purpose being tested.
Which Microsoft Learn resources should you use
Start with the official GH-900 study guide because it identifies the exam, audience, measured domains, updates, and additional preparation links. Use the GitHub Foundations certification page for the exam sandbox, practice assessment, language information, scheduling direction, and current exam details. Use the learning path and course when you need structured instruction.
The GitHub Foundations learning path is identified as Part 1 of 2 and contains 8 Modules. Its listed modules include Introduction to Git, Introduction to GitHub, Introduction to GitHub’s products, Configure code scanning on GitHub, Introduction to GitHub Copilot, Code with GitHub Codespaces, Manage your work with GitHub Projects, and Communicate effectively on GitHub using Markdown.
Microsoft also offers the course GH-900T00-A: GitHub Foundations. The course page identifies it as beginner level, lists instructor-led and self-paced preparation, and gives a course duration of 2 days. Choose the course if you want a compact, guided route; choose the learning path if you prefer to progress module by module and pause for hands-on work.
The learning path is not a replacement for the skills outline. It contains useful product learning, but the exam domains are the controlling study map. Cross-reference each module with the domain it supports, and return to the study guide for any domain that the learning path does not cover in enough detail.
Use the Microsoft Learn practice assessment after you have studied once, not as your only learning resource. Microsoft says the assessment helps candidates understand question style, wording, and difficulty, identify preparation needs, and fill knowledge gaps. Treat a result as a diagnostic signal. Review the underlying topic after every missed or uncertain answer rather than memorizing the answer pattern.
How to use the exam sandbox and practice assessment
The sandbox lets you interact with the exam interface and question types used during the exam, while the practice assessment gives a separate readiness check. Complete both before scheduling if possible. The sandbox answers interface questions; the practice assessment exposes content gaps. Neither should be treated as access to live exam questions.
During the sandbox, note how you move between questions, read instructions, and handle any interactive component. The official certification page states that the exam is proctored and may include interactive components. The point of the sandbox is therefore practical familiarity with the testing environment, not prediction of the live assessment.
After the practice assessment, classify each result as know, uncertain, or do not know. For uncertain answers, return to the official module or study-guide topic even if the answer happened to be correct. For incorrect answers, write a short explanation of the concept and a contrasting example. This creates a review record that is more valuable than a single score.
Do not use dumps, leaked questions, or memorized answer sets as a preparation strategy. They are not an authoritative representation of the current skills outline, do not build usable GitHub knowledge, and cannot guarantee a passing result. The official practice assessment and Microsoft Learn resources are the safer basis for preparation.
A practical four-stage study roadmap
A staged plan works best: establish vocabulary, practice the workflow, close domain gaps, and then verify readiness. The exact number of study hours should vary with your GitHub experience, so use demonstrated ability rather than a fixed calendar as the decision point for scheduling.
Stage one is orientation. Read the GH-900 study guide, copy the seven named domains into your notes, and mark each as familiar, partly familiar, or new. Complete Introduction to Git before Introduction to GitHub. At the end of this stage, explain Git, GitHub, repositories, commits, branches, and pull requests without relying on copied definitions.
Stage two is workflow practice. Work through a repository change from branch creation to commit, proposed review, discussion, and merge in an approved practice environment. Add an issue and use Markdown to describe the work. Review notifications and subscriptions. Then use Projects to split a feature into tasks and track a relationship between work items.
Stage three is breadth and gap repair. Study GitHub products and account structures, modern development practices, privacy, security, administration, and the GitHub community. Revisit code scanning, Actions, Copilot, Codespaces, Projects, and Markdown through the official learning path. For every topic, write its purpose, the problem it addresses, and one related GitHub workflow.
Stage four is verification. Complete the sandbox, take the practice assessment, and compare the result with your domain checklist. Schedule only when you can explain the concepts behind missed questions and can navigate the official scope without repeatedly guessing. This is a practical readiness standard, not a Microsoft pass rule.
If your background is mainly project coordination, give extra practice to Git concepts, branches, commits, and pull requests. If you are a developer, do not assume that coding experience covers account structures, Projects, privacy, administration, or community topics. If you are an administrator, deliberately practice the contributor workflow so that repository and collaboration questions are not treated as purely governance questions.
Exam delivery, languages, and scheduling decisions
Microsoft states that the assessment takes 100 minutes and is proctored; it may include interactive components. The exam is offered in English, Spanish, Portuguese (Brazil), Korean, and Japanese. Schedule through Pearson VUE using the current Microsoft certification route, and check the official exam page for the details that apply to your location and chosen delivery arrangement.
The certification page lists the price as US$99 and states that pricing is based on the country or region in which the exam is proctored. Treat the displayed local price and scheduling terms as the final authority rather than assuming the US amount applies everywhere.
Microsoft recommends registering with a personal Microsoft account. The certification page warns that using an organizational work or school account can cause exam records to be lost and unrecoverable if you leave the organization. Make this account decision before scheduling, then confirm that the certification profile is connected to the Microsoft Learn profile you intend to use.
Microsoft’s study guide says that if the exam is not available in your preferred language, you can request an additional 30 minutes. The certification page lists the available languages, while the study guide notes that localized versions may not always be updated on the same schedule as English. Check the current scheduling and accommodation instructions before relying on a language arrangement.
Pearson VUE provides a test-center locator for finding available centers by location and a program-specific login directory. Use the Microsoft scheduling link first so that you enter the correct exam program. Do not use unrelated Pearson VUE or AWS store information to infer GitHub exam pricing, delivery, or eligibility.
What to confirm before paying or booking
Confirm the exam name is GH-900: GitHub Foundations, the account is personal and correctly connected, the selected language is suitable, the location and proctoring arrangement are available, and any accommodation request has been handled. These checks are practical recommendations. Microsoft’s official page remains the authority for current availability, price, scheduling, and policy details.
How scoring and retakes affect your plan
Microsoft’s study guide states that a score of 700 or greater is required to pass. Use that as the official pass threshold, but do not translate a practice-assessment percentage into a guaranteed exam result because the practice assessment and certification exam are different instruments.
After a failed attempt, Microsoft states that a candidate may retake the certification exam 24 hours after the first attempt. Later retake intervals vary under the retake policy. A sensible response is to diagnose the failed domains, revise the study plan, and check the current retake policy before booking again rather than immediately repeating the same preparation.
Keep a domain-based error log. Record the question topic in your own words, the concept you misunderstood, the official resource used to correct it, and a small action you can perform or explain. This helps distinguish a vocabulary gap from a workflow gap and prevents broad, unfocused rereading.
Do not schedule solely because you have completed every module. Schedule when you can explain why a GitHub feature is used, distinguish neighboring features, and apply the concepts in a simple workflow. Completion is evidence of exposure; explanation and practice are better evidence of readiness.
Common preparation mistakes and better alternatives
The most damaging mistake is studying only visible GitHub screens. Replace screen recognition with purpose-based practice: identify the problem, select the relevant feature, and explain how the feature fits repository work or collaboration.
Another mistake is treating the largest domain as the whole exam. Understand Git and GitHub basics is 25–30%, but the official outline also assigns 10–15% to repositories, 10–15% to collaboration, 10–15% to modern development practices, 5–10% to projects, 10–15% to privacy, security, and administration, and 5–10% to the GitHub community. Cover every named domain.
Avoid using old notes without checking the current study guide. The verified outline is identified as the January 2026 skills outline, and Microsoft notes that exam content and localized versions can change. Recheck the official study guide before your final review, especially if your preparation has taken place over an extended period.
Do not overfocus on advanced implementation. This is a beginner-level certification. Learn the purpose and relationship of capabilities such as code scanning, Copilot, Codespaces, Projects, and GitHub Actions at the level defined by the official resources. Spend less time building elaborate systems and more time explaining core decisions accurately.
Finally, do not confuse confidence with readiness. Use the sandbox, practice assessment, hands-on workflow, and domain checklist together. A candidate who can explain an answer and identify the relevant domain has stronger evidence than one who has merely encountered the same terminology several times.
Your final review checklist
Before scheduling, you should be able to describe the purpose of version control; distinguish Git and GitHub; explain repositories, commits, branches, and GitHub Flow; and use Markdown appropriately in GitHub communication. These are core checks for the largest measured domain.
You should also be able to explain repository management, collaboration through issues and pull requests, discussions, notifications and subscriptions, modern development practices, GitHub Projects, privacy and security considerations, administration concepts, and participation in the GitHub community. Keep the explanations tied to the seven official domains.
Complete the exam sandbox and practice assessment. Review every uncertain response. Confirm your personal Microsoft account, preferred language, scheduling route, and any accommodation needs. Read the current Microsoft certification page and study guide once more before booking because delivery details, localized content, and exam information can be updated.
On exam day, use the official time limit of 100 minutes as a pacing constraint, read each prompt for the requested outcome, and take care with interactive instructions. These are practical test-taking recommendations, not claims about the exact number or format of questions. Concentrate on the feature purpose and workflow described by the scenario rather than trying to recall leaked or unofficial material.
Conclusion
GitHub Foundations is a sensible entry point when you need validated knowledge of how GitHub supports version control, collaboration, planning, modern development, and administration. Base preparation on the GH-900 study guide, prioritize the 25–30% Understand Git and GitHub basics domain, then cover every remaining domain with hands-on workflow practice. Use the official sandbox and practice assessment to check both interface familiarity and knowledge gaps. Schedule through Microsoft’s Pearson VUE route only after your account, language, delivery details, and readiness evidence are in order.
Related exams
- GitHub-Actions exam — GitHub Actions Certificate Exam
- GitHub-Advanced-Security exam — GitHub Advanced Security GHAS Exam
- GitHub-Copilot exam — GitHub CopilotCertification Exam