How I Passed the GH-900 GitHub Foundations Exam: A Practical Guide from a Microsoft Certified Professional

As someone who has spent years working through the Microsoft certification ecosystem—Azure, DevOps, and cloud fundamentals—the GH-900 GitHub Foundations exam initially looked like a simple add-on certification. I already used GitHub daily for repositories, pull requests, and CI/CD pipelines, so my first thought was: How hard could a fundamentals exam really be?
That assumption lasted about one hour into my preparation.
The GitHub Foundations certification is designed to validate your understanding of GitHub workflows, collaboration tools, repository management, and modern development practices. While it’s considered an entry-level exam, it covers much more than basic Git commands. In practice, it tests whether you understand how real teams actually use GitHub in modern DevOps environments.
I decided to take GH-900 mainly for three reasons:
- It complements Azure certifications like AZ-900 and AZ-204.
- GitHub has become central to modern cloud development.
- It validates collaboration and DevOps knowledge beyond just coding.
After passing the exam and comparing my experience with other candidates across forums and community discussions, I realized that a lot of people approach GH-900 the wrong way. This guide shares what actually worked for me.
You’ll learn what the exam really tests, how I prepared in about two weeks, the resources that helped the most, and the practical strategies that made the difference on exam day.
Why I Took the GH-900 (and Why It Might Be Worth It for You)
When Microsoft acquired GitHub, the platform quickly became the backbone of modern software development workflows. Today, GitHub is far more than a code hosting service—it’s a collaboration platform, CI/CD engine, security hub, and project management tool rolled into one.
That shift is exactly why the GH-900 GitHub Foundations certification exists.
For me, the biggest motivation was how well it complements other Microsoft certifications. If you’ve already earned something like AZ-900 or AZ-104, you’ve likely encountered GitHub in documentation, DevOps pipelines, or infrastructure projects. The GH-900 exam fills in the practical workflow layer between development and cloud operations.
In real teams, GitHub sits at the center of everything:
- Developers push code to repositories
- Teams review pull requests
- CI pipelines run through GitHub Actions
- Security alerts surface through Dependabot
- Projects and issues track work
Without understanding these workflows, cloud knowledge alone isn’t enough.
Another reason this certification is gaining traction is simple market demand. GitHub hosts hundreds of millions of repositories globally, and many organizations use it as their default development platform. Employers increasingly expect developers, DevOps engineers, and IT professionals to understand GitHub collaboration practices—not just Git commands.
What I found especially valuable is that GH-900 isn’t limited to developers. It’s also useful for:
- IT professionals transitioning into DevOps
- Project managers working with development teams
- Students entering software engineering
- Career switchers exploring cloud technology
If you’re building a cloud or DevOps career path, GH-900 is one of the easiest ways to validate GitHub knowledge early on.
GH-900 Exam Overview: What to Expect
Before studying, I wanted to understand exactly what the GitHub Foundations exam looks like in practice. The official documentation gives a solid overview, but community reports helped me understand the real exam experience.
Here’s the core structure.
| Exam Feature | Details |
|---|---|
| Exam Code | GH-900 |
| Duration | ~100 minutes |
| Question Count | Typically 45–75 questions |
| Passing Score | ~700 out of 1000 |
| Difficulty | Beginner / foundational |
| Cost | Around $99 |
The exam focuses heavily on concepts rather than syntax. You won’t need to memorize complex Git commands, but you must understand how GitHub workflows function in real projects.
Most questions fall into a few formats:
- Multiple choice
- Multiple select
- Scenario-based questions
- Workflow diagrams
According to official documentation and exam guides, GH-900 covers seven domains, with the largest focus on GitHub collaboration workflows.
Another interesting observation from candidate reports is that many questions test practical decision-making rather than definitions. For example:
- When should you fork vs branch?
- What protects the main branch in a production repo?
- Which GitHub feature automatically updates vulnerable dependencies?
These are things teams encounter daily.
Compared to AZ-900, GH-900 feels slightly more practical. AZ-900 tests cloud concepts broadly, while GH-900 focuses on how work actually happens inside development teams.
The 7 Key Domains – What Actually Matters Most
The GH-900 study guide defines seven knowledge domains. Understanding the weight of each domain helps prioritize your study time.
| Domain | Weight |
|---|---|
| Git & GitHub Basics | 25–30% |
| GitHub Repositories | 10–15% |
| Collaboration | 10–15% |
| Modern Development | 10–15% |
| Project Management | 5–10% |
| Security & Administration | 10–15% |
| GitHub Community | 5–10% |
Let’s break down what actually matters.
Git and GitHub Basics
This domain builds the foundation for everything else.
You should understand:
- What Git is and why version control exists
- The difference between Git and GitHub
- Local vs remote repositories
- Basic Git workflow
In practice, Git follows a simple cycle:
Edit → Commit → Push → Review → Merge
Common exam topics include:
- Branching vs merging
- Pull vs fetch
- Forking repositories
- GitHub interface basics
Tip: Don’t just memorize definitions. Think about how developers collaborate on code changes.
Working with GitHub Repositories
This section focuses on how repositories are structured and managed.
Key areas include:
- Repository visibility (public vs private)
- Repository templates
- README and documentation
- Repository permissions
One question type I saw often involves repository configuration. For example:
Which feature ensures only reviewed code can reach the main branch?
Answer: Branch protection rules
These features become important when teams scale.
Collaboration Features
This is the largest and most important domain.
Collaboration is the heart of GitHub.
Expect questions about:
- Pull requests
- Code reviews
- Forking workflows
- Issues and labels
- GitHub Projects
Example workflow:
| Step | GitHub Feature |
|---|---|
| Suggest code change | Pull Request |
| Track work | Issues |
| Organize tasks | Projects |
| Review code | Code Review |
If you remember only one thing for GH-900, remember this:
Pull requests are the center of GitHub collaboration.
Modern Development Practices
This domain introduces DevOps concepts.
Topics include:
- CI/CD pipelines
- GitHub Actions
- Automated testing
- Continuous integration
GitHub Actions is particularly important.
Example workflow:
Push code → Trigger workflow → Run tests → Deploy
Understanding triggers like push, pull_request, and scheduled workflows helps answer many questions.
Project Management with GitHub
GitHub isn’t just for code.
It also helps manage work.
Important tools:
- Issues
- Labels
- Milestones
- GitHub Projects boards
Think of GitHub Projects as a lightweight version of Jira.
Security and Administration
Security questions are very common.
You should understand:
- Branch protection rules
- Dependabot alerts
- Secret scanning
- Repository permissions
Example:
| Security Feature | Purpose |
|---|---|
| Dependabot | Detects vulnerable dependencies |
| Branch protection | Prevents unsafe commits |
| Secret scanning | Detects exposed credentials |
GitHub Community
The final domain focuses on open source.
Topics include:
- Forking open source projects
- Submitting pull requests
- GitHub Discussions
- Community contributions
Even if you’re not an open-source contributor, understanding the process helps.
My Proven 10–14 Day Preparation Roadmap
I passed GH-900 in about two weeks using a simple preparation plan.
Here’s the approach that worked.
| Day | Focus |
|---|---|
| 1–2 | Understand exam domains |
| 3–6 | Microsoft Learn modules |
| 7–8 | Hands-on GitHub practice |
| 9–11 | Practice questions |
| 12–14 | Review weak areas |
The key principle was hands-on learning.
Instead of just reading documentation, I created test repositories and practiced workflows.
Example exercises:
- Create a repository
- Open a pull request
- Merge branches
- Configure branch protection
- Trigger a GitHub Actions workflow
These exercises made the exam questions much easier to interpret.
Essential Study Resources That Delivered Results
The best GH-900 resources are actually free.
Start with the official Microsoft learning path.
- https://learn.microsoft.com/en-us/training/courses/gh-900t00
- https://learn.microsoft.com/en-us/credentials/certifications/github-foundations/
- https://learn.microsoft.com/en-us/credentials/certifications/resources/study-guides/gh-900
These resources explain the exam objectives and provide structured lessons.
Another resource I found useful was the free practice assessment from Microsoft. It gives a good sense of the question style.
However, there’s a noticeable gap between learning material and the actual exam. Microsoft Learn teaches the concepts, but it doesn’t always simulate the exam difficulty.
For final review, I used additional practice questions to test real scenarios. One solid set of practice materials I found useful was:
https://www.leads4pass.com/gh-900.html
The reason it helped was simple: the questions were closer to the scenario-based format used in the actual exam. This helped me identify weak areas like repository permissions and GitHub Actions triggers.
The best study stack looked like this:
| Resource | Purpose |
|---|---|
| Microsoft Learn | Core concepts |
| GitHub Skills labs | Hands-on practice |
| Practice assessments | Exam simulation |
Exam Day Strategies and Pitfalls I Avoided
On exam day, preparation is only half the battle.
The way you approach the test matters.
Here are a few strategies that helped me.
1. Read scenario questions carefully
Many questions describe a situation like:
A team wants to prevent direct commits to main.
The key is recognizing the feature being described.
2. Watch for “select all that apply”
These questions are tricky.
You might know the topic but still lose points by missing one option.
3. Use elimination
When unsure, eliminate obviously incorrect answers first.
GitHub features often have very specific names.
4. Manage time wisely
With roughly 60 questions in 100 minutes, you have plenty of time.
Aim for about:
1–1.5 minutes per question.
1–1.5 minutes per question.
After Passing: How to Leverage the GH-900 on Your Resume and Career
Passing the GitHub Foundations certification is just the beginning.
The first thing you should do is claim your badge through Microsoft’s certification dashboard.
Then add it to:
- LinkedIn certifications section
- Your technical resume
- GitHub profile README
Example resume entry:
GitHub Foundations (GH-900)
Microsoft Certification validating GitHub collaboration workflows, CI/CD basics, repository management, and DevOps practices.
Once you complete GH-900, the next certifications in the GitHub ecosystem include:
- GitHub Administration (GH-100)
- GitHub Actions (GH-200)
- GitHub Copilot (GH-300)
You can explore these in my guide here:
[Follow Fulldumps: I will publish all corresponding certification articles in a future update.]
Final
The GH-900 exam is one of the most practical certifications in the Microsoft ecosystem.
It validates something many developers use every day but rarely study formally: how teams collaborate in GitHub.
If you’re planning to take the exam, here’s a simple action plan:
- Review the official study guide
- Complete the Microsoft Learn learning path
- Practice GitHub workflows hands-on
- Take realistic practice tests
- Review security and collaboration features
With consistent preparation, most candidates can pass GH-900 in about two weeks.
FAQs
1. How difficult is the GH-900 exam?
The GH-900 GitHub Foundations exam is considered beginner level, but it still requires understanding real GitHub workflows like pull requests, issues, and CI/CD automation.
2. How long should I study for GH-900?
Most candidates prepare for 10–14 days, especially if they already use GitHub.
3. Is GH-900 worth it for developers?
Yes. It validates collaboration workflows and DevOps fundamentals that employers expect developers to understand.
4. What is the passing score for GH-900?
The exam uses a scaled scoring system where 700 out of 1000 is typically the passing score.
5. Does GH-900 expire?
Yes. The certification is generally valid for two years, after which renewal may be required.
