GitHub Foundations Exam Guide 2026: GH-900 Prep That Uses GitHub

GH-900 Is Not a Git Trivia Exam

GitHub Foundations is beginner-level, but the candidates who struggle usually study it passively. They read definitions for branch, fork, pull request, issue, Actions, Dependabot, and project board without actually using them. That is the wrong prep model.

GitHub Foundations practice questionsPractice questions with detailed explanations

What Changed in the Live Credential Page

Microsoft Learn now presents GitHub Foundations as GH-900. The page was last updated February 19, 2026 and lists a 100-minute proctored assessment. It also links a free practice assessment, a free exam sandbox, and the official GH-900 study guide.

This matters because older GitHub Foundations pages around the web can still quote older timing, language lists, or registration flows. For scheduling, use Microsoft Learn as the control page.

The Hands-On Repo Drill

Create a public or private practice repository and complete this sequence:

If you can explain each action in plain English, you have covered more useful ground than a week of memorizing Git commands without context.

How to Allocate Study Time

A 2-Week Plan for New GitHub Users

Days 1-2: Complete the official study guide overview and launch the Microsoft Learn exam sandbox.

Days 3-5: Build the repository drill above and write one-sentence definitions for every feature you touched.

Days 6-8: Take free practice at /practice/github-foundations and group misses by workflow.

Days 9-11: Review Microsoft Learn modules for weak areas and repeat pull request, issue, project, and Actions tasks.

Days 12-14: Take the official practice assessment, retake weak OpenExamPrep sets, and schedule only when GitHub workflows feel familiar.

What Passive GitHub Prep Misses

The live GH-900 skill list includes administration, privacy, security, projects, community, and modern development practices. That means a repo-only tour is not enough. After you create a branch and pull request, inspect repository visibility, branch protections or rulesets, collaborators, teams, permissions, Dependabot alerts, secret scanning concepts, discussions, issue templates, project views, and Actions workflow status.

You do not need expert GitHub Enterprise administration, but you should know the difference between repository collaboration, organization-level governance, and account-level identity choices. Microsoft also recommends using a personal Microsoft account for exam registration, which is a practical trap for candidates who schedule through an employer account and later lose access.

Scheduling and Account Traps

GitHub certification scheduling now routes through official certification pages and Pearson VUE. GitHub Docs notes that candidates can choose a local test center or online proctoring, and that Pearson VUE appointments may be scheduled only within a limited future window. Build that into your plan if you are trying to certify before a hiring deadline or training reimbursement cutoff.

For online testing, run the system check before you pay, not the night before the appointment. For identity, make sure the name on your certification profile exactly matches the government ID you will use. Those are not GitHub skills, but they are common ways a prepared candidate loses the sitting.

Official Sources

Use the Microsoft Learn GitHub Foundations page for the live exam duration, language list, practice assessment, sandbox, and Pearson VUE scheduling. Use GitHub Docs on registering for certification exams and the GitHub Certification Registration portal for scheduling flow, test-center versus online delivery, system checks, and ID requirements.

The Pass Strategy

Do not study GH-900 like a vocabulary list. Study it like a user onboarding checklist. If you can collaborate in a repository, explain why teams use pull requests and issues, identify basic security controls, and recognize modern development features, the exam becomes much more predictable.

Turn the Blueprint Into Working Labs

For GitHub Foundations Exam Guide 2026: GH-900 Prep That Uses GitHub, reading alone is rarely enough. Translate each objective into a task you can perform, explain, or troubleshoot. A good study block starts with the official objective, moves into a small lab or documentation walkthrough, and ends with a timed question set. If the topic is security, build a chain from identity to detection to response. If it is cloud, map the service to a failure mode, a cost or governance concern, and an operational control. If it is DevOps or platform work, practice the command, configuration, permission model, and rollback path rather than memorizing vocabulary in isolation.

Keep a lab notebook with three fields: what I changed, what evidence proves it worked, and what would break it. That last field is where exam readiness improves. Certification questions often describe symptoms instead of naming the service or feature. If you know only the happy path, every distractor sounds plausible. If you have intentionally broken a policy, pipeline, role, cluster object, dashboard permission, integration, or service configuration, you can recognize the symptom faster under time pressure.

Official-Source Check

Use GitHub Certifications as the baseline for current exam names, objectives, retirement notices, scheduling rules, and candidate guidance. Vendor blogs, course notes, and older flashcards can be useful, but they often lag behind blueprint revisions. When an objective has changed wording, update your notes to match the current official language. That habit prevents a common failure pattern: overstudying a familiar legacy feature while underpracticing the new wording that appears in modern scenario questions.

Scenario and Troubleshooting Method

Read each technical scenario as an incident ticket. First identify the desired state: secure access, reliable deployment, compliant configuration, correct data result, restored service, or least-privilege operation. Next identify the constraint: no downtime, smallest change, approved service, auditability, cost, latency, regional availability, or user impact. Then eliminate options that solve the wrong layer. Many wrong answers are real tools, but they operate at the network layer when the problem is identity, at the code layer when the problem is configuration, or at the monitoring layer when the question asks for prevention.

For command-heavy or hands-on exams, rehearse search and verification patterns. Know how to inspect state before changing it, how to confirm the change, and how to undo or narrow the blast radius if the first attempt is wrong. For multiple-choice exams, practice explaining why each distractor is attractive. The explanation matters because the exam is testing tradeoffs, not only definitions. A correct answer usually fits the constraint with the fewest unnecessary side effects.

Practice Routing and Final Review

After every practice set, tag misses by failure type: concept, service boundary, syntax, sequence, or speed. Concept misses require documentation review. Service-boundary misses require a comparison table. Syntax misses require a short hands-on drill. Sequence misses require writing the order of operations. Speed misses require smaller timed sets with strict review afterward. Do not treat all misses as equal, because rereading a chapter will not fix a lab-verification problem.

In the final week, mix domains deliberately. Build short sets that combine identity, networking, logging, automation, data, operations, and security so you can switch context the way the exam expects. Also rehearse the first minute of a question: define the goal, underline the constraint, identify the layer, and choose the least risky action. That process is slower while practicing but faster on test day because it keeps you from rereading the same scenario three times.