GitHub Foundations #1: Exam Overview — Structure and Study Strategy
If you have worked through the six parts of Git Basics — from the snapshot model to your first Pull Request — and the seven parts of Practical Git Workflows, covering branching strategy through PR operations, the natural next step is validating that skill with a certification. GitHub runs an official certification program: above the entry-level GitHub Foundations sit certifications like GitHub Actions, GitHub Copilot, GitHub Advanced Security, and GitHub Administration. This series is a ten-part track covering everything you need to pass the starting point, the GitHub Foundations Certification.
This post is the starting point of the series. Before diving into questions, we put the full picture in place: what the exam asks, in what format, and in what order to prepare.
What kind of certification is GitHub Foundations #
GitHub Foundations tests how well you understand and use the GitHub platform. It does not test your ability to write code or solve algorithm problems. Instead, it checks whether you can answer questions like these without hesitating.
- How are Git and GitHub different?
- When do you use a fork, a clone, and a template repository?
- What collaboration problems do Issues, Pull Requests, and Discussions each solve?
- Which stage of the development flow do GitHub Actions, Codespaces, and Copilot automate?
- How are repository permissions and security features organized in an organization?
The exam is entirely multiple choice with no hands-on component, so people who are not comfortable in a terminal can still take it. There are no prerequisites either. That is why the audience is not limited to developers.
| Audience | Value |
|---|---|
| New developers, junior engineers | The fastest way to build a systematic GitHub collaboration vocabulary. A first credential for the portfolio |
| PMs, planners, designers | The minimum set for reading and writing Issues and PRs in the same vocabulary as the dev team |
| Members of organizations adopting GitHub | The ability to understand plan, permission, and security boundaries and follow decisions |
| Candidates for higher certifications | The shared foundation before moving on to Actions, Advanced Security, and other exams |
Conversely, if you are an engineer who has been running PRs on GitHub daily for years, this exam will not teach you much that is new. Even then, areas you may not touch day to day (Projects, organization administration, community features) are in scope, so a strategy of scanning the domain map and filling only the gaps works well.
Exam structure #
| Item | Details |
|---|---|
| Format | Multiple choice (single select + multiple select) |
| Questions | About 75 scored questions plus a small number of unscored pretest questions |
| Time | 120 minutes |
| Passing bar | Scaled scoring; commonly reported to be around 70% |
| Delivery | PSI online proctoring or a test center |
| Cost | Around 99 US dollars (subject to change) |
| Validity | 3 years |
| Prerequisites | None |
Registration goes through GitHub’s official certification registration site. If you choose online proctoring, you take the exam at home under webcam supervision, so prepare three things in advance.
- ID — You need identification in the Latin alphabet that matches the name you registered with.
- Environment — You must be alone in a quiet space, and there is a check-in step where you show your desk area on webcam before the exam.
- Network and hardware — Confirm your computer and connection can run the proctoring software reliably. A system test is provided; passing it no later than the day before the exam is the safe move.
Time per question is generous. With 120 minutes for roughly 90 questions, you get more than a minute per question, and with no hands-on tasks the pass/fail line is decided less by time pressure and more by whether you covered the full scope. Multiple-select questions state how many options to choose, so the only thing to watch is not missing that count in the prompt.
Passing earns you a digital badge. It attaches to your résumé and LinkedIn profile as a verifiable link, so you can share the credential without paperwork.
The seven-domain map #
The exam scope is divided into seven domains. Each part of this series takes one domain.
| Domain | Covers | This series |
|---|---|---|
| 1. Introduction to Git and GitHub | Git basics, GitHub accounts and plan structure | #2 |
| 2. Working with GitHub Repositories | Repository creation, branches, tags, releases, gists | #3 |
| 3. Collaboration Features | Issues, PRs, code review, Discussions | #4, #5 |
| 4. Modern Development | Actions, Codespaces, Copilot, Packages | #6 |
| 5. Project Management | Projects, automation, insights | #7 |
| 6. Privacy, Security, and Administration | Permissions, 2FA, Dependabot, security features | #8 |
| 7. Benefits of the GitHub Community | Open source, InnerSource, community features | #9 |
| (All domains) | Full-scale 50-question practice exam | #10 |
Collaboration Features (Domain 3) is reported to carry the largest weight, with Introduction to Git and GitHub (Domain 1) next. The detailed weights can be revised, so check the latest values in the official study guide before you sit the exam. This series matches that emphasis by giving collaboration two parts (#4 and #5).
Study strategy — features you have clicked through stick #
We recommend preparing in four steps.
- Read the official study guide first. It lists the detailed objectives per domain, which immediately separates the areas you already know from the gaps.
- Practice with GitHub Skills. These are free interactive courses from GitHub where you learn by opening Issues and merging PRs in a real repository. Most features the exam asks about exist as a course.
- Skim the GitHub Foundations learning path on Microsoft Learn. It is organized in nearly the same order as the domains, which makes it a good fit for consolidating theory.
- Use this series to review the exam-oriented essentials, then run the #10 practice exam as the final check.
If Git commands themselves are unfamiliar, finish this blog’s Git Basics series first. The Git questions in Domain 1 overlap almost entirely with that series.
How to allocate study time depends on your background.
- Developers who use GitHub daily — Skim the familiar areas (repositories, PRs) and concentrate on what you do not normally touch: Projects, organization administration, community features, and plan boundaries. Preparation can be short.
- Beginners new to GitHub — Build Domains 1 and 3 thoroughly through hands-on practice, and cover the remaining domains at the concept level. Following the GitHub Skills courses in order is the most reliable path.
- Non-developer roles — For Git commands, stop at table level (which command plays which role) and put your weight on the web-based collaboration features and concept distinctions. The exam does not require terminal proficiency.
Wrapping up #
Three takeaways from this post.
- GitHub Foundations is a multiple-choice, entry-level certification about GitHub platform concepts, open to developers and non-developers alike with no prerequisites.
- The exam consists of seven domains, 120 minutes, and about 75 scored questions, with collaboration features carrying the largest weight.
- Prepare by finding your gaps with the official study guide, then operating the features yourself through GitHub Skills and a practice account.
The next post, “GitHub Foundations #2 Domain 1: Git and GitHub Basics — Version Control and Product Structure”, covers the first domain. We start with the concepts that underpin the whole exam: the boundary between Git and GitHub, and the account and plan structure.