What the GitHub Foundations exam covers

On Monday, April 12, 2027, Owen Tremblay booked a small meeting room at the Tidewater Trail Guides office in Moncton for twelve lunchtime sessions in a row. His GitHub Foundations exam, Exam GH-900, was booked for 9:00 in the morning on Wednesday, April 28, to be taken online from home. He had finished both earlier courses: Git and GitHub Foundations in the autumn and winter, and GitHub Collaboration, Security and Administration Basics in March and early April. Priya Nair, the team's Git lead, agreed to run the sessions with him, and Rosa Delgado, who administers Tidewater's GitHub organization, offered to take the security and administration review. "You already know most of this," Priya told him. "The next two weeks are about knowing it in the way the exam asks, finding the gaps, and walking in calm."

This course is that readiness sprint. The first two lessons explain what the exam covers and how it is delivered. Lessons 3 to 9 review the seven areas of the exam one at a time, linking each skill back to the lessons where it was first taught. Lesson 10 collects the mistakes candidates make most often, lesson 11 builds a study plan from the exam weights and Owen's own results, and lesson 12 is a final review with an exam-day checklist. Each lesson ends with practice questions in the exam's styles.

Who the exam is for

GitHub Foundations is the entry-level GitHub certification. Microsoft, which now delivers GitHub's certifications through Microsoft Learn, describes it as a beginner exam for anyone who uses GitHub: developers, but also people who never write code, such as project managers, technical writers, designers, students and administrators. That suits Owen, a guidebook editor whose daily GitHub work is reviewing text in pull requests and keeping the corrections board tidy. There are no formal prerequisites. The exam expects foundational knowledge of GitHub's core features: what they are for, when to use each one, and how the pieces fit together, rather than deep command-line skill.

The certification does not expire and does not need renewing, unlike Microsoft's associate and expert certifications. Once Owen passes, the credential stays on his Microsoft Learn profile. The other GitHub certifications, on GitHub Actions, GitHub Administration, GitHub Advanced Security and GitHub Copilot, build on the same foundation, and several other Tidewater programs list this course's two predecessors as their starting point.

The skills outline

Every Microsoft exam has a published study guide with a skills outline: the list of what can be tested, grouped into areas, each with a weight. The GH-900 outline was revised substantially in January 2026: new objectives were added, some were removed, and the rest were reworded. That matters for anyone using older study material, because questions on removed topics will not appear, and topics added in 2026, such as passkeys, Enterprise Managed Users and Copilot agents, can. The first rule of exam preparation, Priya said, is to study from the current outline and to check its date before booking.

Reading the weights

The weights are ranges because each exam form is drawn from a larger pool of questions, so the exact share of each area varies a little from one candidate to the next. A range of 25 to 30 means that, on any form, between a quarter and nearly a third of the questions come from that area. The ranges do not add up to exactly 100 at either end: the lowest values total 75 and the highest 105. Using the middle of each range gives a sensible working figure.

Weights tell you where the questions are, not where your gaps are. Owen's weakest area, he suspected, was modern development, because Tidewater does not use Codespaces and he had only watched Priya use Copilot. It carries about a seventh of the exam. Lesson 11 combines the weights with his own practice results to decide how many of his remaining study hours each area deserves.

What "foundational" means on this exam

A foundations exam tests recognition and judgement more than procedure. Typical questions describe a situation and ask which feature fits it, what a setting does, who can do something, or what happens next. They rarely ask for exact command syntax or the location of a button that moves between interface updates. Owen tested this against the outline's wording: it uses verbs such as describe, explain, identify, differentiate and recognize much more than configure. When it does say configure, as with Projects or notifications, the question is usually about what the options are and which one fits a need.

That shapes how to study. Reading the documentation from end to end is slow and covers far more than the exam. Working through each line of the outline and asking, "Could I explain this to Grace in two sentences, and could I tell it apart from the thing it is most often confused with?" covers exactly what the exam covers. Owen made that his test for every topic in the review lessons.

Generally available features and previews

The study guide notes that most questions cover features that are generally available, meaning released for everyone and supported. Features in public preview can appear when they are widely used. GitHub releases features quickly, and Copilot in particular changes month to month, so an exam question may describe a feature slightly differently from what Owen sees on screen. The safe approach is to learn what each feature is for and how it is offered, which changes slowly, rather than the details of its interface, which change often.

Mapping the outline to what Owen already knows

Priya asked Owen to go through the outline line by line and mark each skill with one of three symbols: a tick for "I could teach it", a dot for "I recognize it but would hesitate", and a cross for "I have not met this". It took twenty minutes and produced a useful map. Most of Git and GitHub basics and almost all of collaboration were ticks. Repositories and privacy, security and administration were mostly ticks with a few dots, such as repository insights and Enterprise Managed Users. Modern development had three crosses: dev container customization, Copilot agents, and the differences between Copilot plans. Project management had dots on project insights and built-in workflows.

A self-assessment is a starting point, not a measurement. People tend to overrate topics they have used often and underrate ones they learned recently. That is why lesson 2 adds an outside check, Microsoft's free practice assessment, and why Owen kept an error log from the first practice question onwards.

Study sources that match the exam

The study guide links to free resources, and Owen listed the ones he would use. The Microsoft Learn learning path for GitHub Foundations follows the outline closely. GitHub Docs explains each feature authoritatively and is the place to settle any disagreement between sources. The practice assessment on the certification page gives sample questions in the exam's style, with explanations and links. Microsoft's exam sandbox shows the exam interface so the format holds no surprises. Third-party courses and question banks vary in quality and can be out of date, especially after the January 2026 revision, so Owen decided to use only official sources for this sprint, plus his own notes from the two earlier courses.

Setting a target

The pass mark is 700 on a scale that runs to 1,000. Scores are scaled, so 700 is not 70 correct answers out of 100, and questions can be worth different amounts. Owen asked what score he should aim for in practice. Priya's advice was to aim for a comfortable margin rather than for the pass mark: consistently answering about 80 in 100 practice questions correctly, across every area, before the exam. A margin absorbs a bad day, an unlucky mix of questions, and the difference between practice and real questions. More important than the overall figure is that no area is far below the others, because a weak area that carries 13 or 14 in 100 of the exam can sink a strong performance elsewhere.