GH-900 Practice Test – 200 Free GitHub Foundations Questions

Microsoft GH-900 Practice Test

Preparing for the Microsoft GH-900 GitHub Foundations exam becomes much easier when you know what to study and how to check your progress. Our Edurely certification practice tests help students become familiar with topic-based questions, identify weak areas, and build confidence before exam day. This guide explains the current GH-900 exam topics in simple language and shows you how to use practice questions as part of a complete study plan.

GH-900 exam overview: the quick answer

GH-900 is the exam for the GitHub Foundations certification. It tests whether you understand the essential ideas, products, and features used to work and collaborate on GitHub. It is a beginner-level exam intended for developers, non-developers, students, administrators, DevOps learners, and other GitHub users.

You should be able to explain Git and GitHub basics, work with repositories, use collaboration tools, understand modern development features, manage projects, recognize access and security controls, and participate in the GitHub community. The exam does not expect you to be an expert programmer. However, some practical experience with a GitHub account and a sample repository will make the concepts far easier to remember.

According to the official GitHub Foundations certification page, candidates receive 100 minutes to complete the proctored exam. The current official GH-900 study guide states that a score of 700 or higher is required to pass.

What does a GH-900 practice test measure?

A useful GH-900 practice test measures more than your ability to recognize definitions. It checks whether you can choose the right GitHub feature for a simple situation.

For example, you may need to decide whether a team should open an issue, start a discussion, create a pull request, or add an item to a GitHub Project. You may also need to recognize the purpose of a README, a CODEOWNERS file, a branch protection rule, GitHub Actions, GitHub Copilot, or Codespaces.

Good practice questions should help you do four things:

1. Recall important terms. You should know what repositories, branches, commits, issues, pull requests, forks, and workflows are.
2. Compare similar features. You should understand Git versus GitHub, issues versus discussions, github.dev versus Codespaces, and public versus private repositories.
3. Apply a concept to a scenario. You should be able to choose a suitable tool when a small team wants to plan, review, automate, secure, or share work.
4. Review your reasoning. An answer explanation should show why the correct choice fits and why the other choices do not.

Practice tests are most valuable when they reveal a study gap. They should not be treated as collections of real exam questions. Memorizing answers without understanding the feature will not prepare you for newly worded scenarios.

Who should take the Microsoft GH-900 exam?

GH-900 is suitable for students and early-career professionals who want to show that they understand GitHub fundamentals. It can be especially useful for:

• Students learning version control for the first time
• Junior developers who are beginning to work in shared repositories
• Project coordinators who use issues, milestones, and GitHub Projects
• DevOps learners who want a foundation before studying advanced automation
• Administrators who need a basic understanding of accounts, organizations, teams, and roles
• Technical writers who contribute documentation through repositories and pull requests
• Non-developers who work with software teams on GitHub
• Open-source contributors who want to understand common community workflows

The certification is not limited to programmers. The official audience description specifically includes developers, non-developers, and other GitHub users. Coding knowledge is helpful for context, but the main goal is to understand how GitHub supports version control, collaboration, planning, automation, security, and community participation.

If you are comparing credentials before deciding what to study, Browse Microsoft exams by certification to view other practice-test options and choose a path that matches your goals.

Current Microsoft GH-900 exam topics and weights

Microsoft significantly changed the GH-900 skills outline in January 2026. Older study pages may show a different structure, so students should follow the current seven-domain outline.

1. Understand Git and GitHub basics: 25–30%

This is the largest domain. Begin by learning why version control exists. Version control records changes to files, helps people work safely on different ideas, and provides a history that can be reviewed or restored.

Git is a distributed version control system. It tracks file history and supports operations such as committing changes, creating branches, and merging work. GitHub is a cloud-based platform built around Git repositories. It adds hosting, pull requests, issues, discussions, projects, automation, security tools, and community features. Git can be used without GitHub, while GitHub uses Git as the foundation for version-controlled work. GitHub’s introductory explanation of GitHub and Git is a useful starting point for beginners.

You should understand these core terms:

• A repository stores a project and its history.
• A commit is a recorded set of changes with an identifying message.
• A branch is a separate line of development.
• A merge combines compatible work from one branch into another.
• A pull request proposes changes and provides a place to review them before merging.

The domain also covers personal accounts, organizations, and enterprise options. A personal account represents an individual. An organization allows groups to manage repositories, people, teams, and permissions. Enterprise options add centralized governance across organizations.

Learn the basic GitHub Flow: create a branch, make and commit changes, open a pull request, discuss and review the work, and merge approved changes. Also study how Markdown improves communication with headings, lists, links, code formatting, checklists, and other readable elements in issues and pull requests.

Finally, know when GitHub Desktop or GitHub Mobile is useful. Desktop provides a graphical way to work with repositories and common Git actions from a computer. Mobile is helpful for reviewing notifications, issues, and pull requests while away from a desk.

2. Work with GitHub repositories: 10–15%

This domain focuses on how a repository is organized and maintained. Learn the purpose of common community and documentation files:

• README: Introduces the project, explains what it does, and often provides setup or usage instructions.
• LICENSE: States the legal terms under which others may use, change, or distribute the project.
• CONTRIBUTING: Explains how people should propose changes and follow the project’s contribution process.
• CODEOWNERS: Identifies people or teams responsible for areas of the repository and can support review requests.
• SECURITY: Tells users how to report a vulnerability responsibly and describes the project’s security policy.

You should know how to create and organize repositories, add files, use branches, and start from a repository template. A template provides a reusable starter structure. A branch supports work within the same repository without changing the main branch immediately.

Review repository visibility, maintenance, and insight features at a basic level. Stars let users bookmark or show interest in repositories. Insights and metrics can help maintainers understand repository activity. Dependency information helps teams see the software packages a project relies on. Feature previews allow users to try selected changes to the GitHub interface before general release.

3. Collaborate using GitHub: 10–15%

Collaboration questions often describe a goal and ask which GitHub feature fits best.

• Use an issue to track a bug, task, request, or unit of work.
• Use a pull request to propose, discuss, review, and merge file changes.
• Use a discussion for an open-ended conversation, community question, announcement, or idea that is not yet a defined task.

You should know that pull requests can be linked to issues. Supported closing keywords can automatically close a linked issue when a pull request merges. Templates help people provide consistent information when opening issues or pull requests. Filters help users find relevant items, while assignments show who is responsible for work.

Notifications keep you informed about activity you participate in, watch, or subscribe to. Good notification settings reduce distractions while preserving important updates.

Also review the purposes of Gists, Wikis, and GitHub Pages. A Gist is useful for sharing code snippets, notes, or small files. A Wiki provides repository-linked documentation pages. GitHub Pages publishes a website from a repository and is commonly used for documentation, portfolios, and project sites.

4. Apply modern development practices: 10–15%

This domain introduces automation, AI-assisted development, and cloud development environments.

GitHub Actions automates workflows in response to events or schedules. A workflow might run tests when someone opens a pull request, build an application after a commit, or deploy approved code. At the foundational level, focus on purpose, triggers, jobs, and common use cases rather than advanced YAML syntax.

GitHub Copilot provides AI-powered assistance such as code suggestions and chat-based help. The current blueprint also includes Copilot agents, Agent Mode, and multi-model support. Learn the high-level difference between receiving suggestions while you work and delegating a defined task to an agent. AI output still needs human review, testing, and security judgment. Also review how Copilot capabilities and administration differ across individual, business, and enterprise offerings, because plans and policies affect availability.

GitHub Codespaces provides a cloud-hosted development environment that can be configured for a repository. A dev container describes tools, runtimes, extensions, and settings so contributors can start with a more consistent environment. GitHub’s Codespaces overview explains how these environments reduce local setup and can be opened from a browser or a supported editor.

The GitHub.dev editor is a lightweight web editor that is convenient for quick file changes and navigation. Codespaces supplies compute, a terminal, and a fuller development environment. If you need to run, build, or test a project in the cloud, Codespaces is generally the better match. If you only need a quick browser-based edit, GitHub.dev may be enough.

5. Manage projects with GitHub: 5–10%

GitHub Projects helps teams plan and track work. Projects can show items through layouts such as tables, boards, and roadmaps. Fields, filters, views, and workflows help organize information for different audiences.

Know the roles of labels, milestones, assignees, and saved replies. Labels categorize work, such as bug, documentation, or priority-high. Milestones group issues and pull requests around a goal or delivery period. Assignees show who owns a task. Saved replies provide reusable responses for common questions.

Project insights and charts can help a team observe progress, workload, and productivity patterns. For the exam, focus on selecting a feature that improves visibility or reduces repetitive management work.

6. Understand privacy, security, and administration: 10–15%

Security begins with the user account. Two-factor authentication, or 2FA, requires an additional factor beyond a password. A passkey uses a cryptographic credential and can offer phishing-resistant sign-in. Students should recognize both as stronger protections than relying on a password alone.

You should understand the principle of least privilege: give users only the access they need. Repository and organization roles provide different levels of permission. Teams make it easier to manage groups of organizational members. Organization settings apply policies and features across that organization.

Learn the basic differences among repository visibility choices:

• Public: visible to everyone on the internet.
• Private: visible only to people who are granted access.
• Internal: visible to members of an enterprise when that option is available.

Branch protection rules and rulesets can require checks or reviews and can restrict actions before important branches are changed. The blueprint also covers Enterprise Managed Users, which support centrally managed identities, and organization-wide Copilot policies, which let administrators control AI feature access and behavior. You do not need to memorize every setting, but you should understand the purpose of centralized identity, access, and policy management.

7. Explore the GitHub community: 5–10%

The final domain covers participation and discovery. Open-source projects make source code available under a license that defines permitted use and contribution. GitHub Sponsors gives eligible open-source contributors a way to receive financial support.

Following users and organizations helps you keep up with their public activity. GitHub Marketplace helps users find apps, actions, and other integrations that extend GitHub workflows.

InnerSource applies open-source working methods inside an organization. Teams may use visible repositories, contribution guidance, issues, and pull requests so employees outside the owning team can discover and contribute to internal projects.

Be ready to compare forks, templates, and discoverable repositories. A fork creates an independent copy under another account while maintaining a connection to the original network. A template helps people start a new repository with similar files and structure without carrying over the same collaboration relationship. Discoverability helps users find relevant work and communities.

High-value GH-900 comparisons to remember

How Our GH-900 Preparation Turns Study into Progress

Preparation should make each study session useful, even if you have only a short amount of time. Our GH-900 practice approach is designed to help you learn the terminology, apply it to realistic situations, and see which domain needs more attention.

When you prepare with us, you can use:

• Domain-based practice: Focus on one blueprint area instead of mixing every topic at the beginning.
• Clear answer explanations: Learn why a choice is correct rather than memorizing a letter.
• Student-friendly wording: Build technical vocabulary through simple explanations and practical examples.
• Progressive difficulty: Begin with core terms, then move to comparisons and short scenarios.
• Weak-area review: Turn incorrect answers into a focused list for your next study session.
• Timed attempts: Practise making careful decisions while managing the clock.
• Readiness checks: Use scores by domain to decide when you are ready for a full mock exam.

Do not aim for one lucky passing score. Aim for consistent results and the ability to explain your answer in your own words. When you are ready to move from reading to active review, Start Practicing Today and use each result to guide your next lesson.

How to use a Microsoft GH-900 practice test effectively

Step 1: Take a short diagnostic test

Start with 20 to 30 mixed questions before studying heavily. Record your score by domain. The goal is to identify your starting point, not to judge yourself.

Step 2: Study one domain at a time

Read the current official objectives and use Microsoft Learn and GitHub Docs for the topics you missed. Give extra time to Git and GitHub basics because it represents 25–30% of the blueprint.

Step 3: Complete a small hands-on task

Create a practice repository. Add a README, open an issue, create a branch, make a commit, and open a pull request. The actions will give meaning to the terms you read.

Step 4: Review every incorrect answer

For each mistake, write down the tested concept, the correct reasoning, and the clue you missed. Also review correct guesses. A guessed answer is still a knowledge gap.

Step 5: Retest after a gap

Wait a day or two before repeating a topic test. A delayed attempt shows whether you truly learned the idea instead of remembering the screen.

Step 6: Use timed full-length practice

Near the end of your preparation, use a timed mock test. The real exam provides 100 minutes, but the number of questions can vary. Practise steady pacing rather than assuming a fixed time per question.

A four-week GH-900 study plan

Week 1: Git, GitHub, and repository basics

Study version control, Git versus GitHub, repositories, commits, branches, and GitHub Flow. Create a personal repository and add README, LICENSE, CONTRIBUTING, SECURITY, and CODEOWNERS files. Practise creating a branch and making a clear commit.

Weekly goal: Explain the basic workflow without notes and score at least 75% on a domain quiz.

Week 2: Collaboration and project management

Open sample issues, create issue templates, link a pull request to an issue, and explore discussions and notifications. Create a small GitHub Project with a table or board view. Add labels, a milestone, assignees, and a saved reply.

Weekly goal: Choose confidently among issues, discussions, pull requests, and project items in short scenarios.

Week 3: Modern development, security, and administration

Learn about Actions, Copilot, Codespaces, dev containers, and GitHub.dev do. Review 2FA, passkeys, roles, teams, visibility, branch protection, Enterprise Managed Users, and Copilot policies. Focus on purpose and suitable use cases rather than advanced configuration.

Weekly goal: Complete comparison questions without confusing editing, automation, AI assistance, planning, and security features.

Week 4: Community topics and final review

Study open source, Sponsors, following, Marketplace, InnerSource, forks, templates, and repository discovery. Take at least two timed mixed practice tests on different days. Review every error and revisit only the domains that remain below your target.

Weekly goal: Produce consistent practice results and explain the reasoning behind each answer.

Hands-on tasks that make GH-900 concepts easier

Use one disposable practice repository to complete these tasks:

1. Create a repository with a descriptive README.
2. Add a license and contribution instructions.
3. Open an issue for a small documentation improvement.
4. Create a branch and edit a Markdown file.
5. Commit the change with a meaningful message.
6. Open a pull request and link it to the issue.
7. Request or simulate a review, then merge the change.
8. Create labels, a milestone, and a small project board.
9. Inspect the Actions tab and identify workflow triggers in an example file.
10. Open github.dev and compare it with the Codespaces creation experience.
11. Review repository visibility and branch rules without changing an important project.
12. Find an app or Action in the GitHub Marketplace and explain its purpose.

You do not need a complex application. A few Markdown files are enough to practise most foundational workflows safely.

Common GH-900 preparation mistakes

Studying an old exam outline

The blueprint changed significantly in January 2026. Use the current seven domains and include newer objectives such as Copilot agents, Agent Mode, multi-model support, repository metrics, project insights, passkeys, Enterprise Managed Users, and InnerSource.

Memorizing terms without comparing them

Many beginner errors come from mixing up related tools. Create comparison cards for issue versus discussion, fork versus template, GitHub.dev versus Codespaces, and Actions versus Projects.

Ignoring the smaller domains

A 5–10% domain is still part of the exam. Community and project-management questions may be easier points when you have studied their purpose clearly.

Taking repeated tests without review

Immediate repetition can create a misleading high score. Review explanations, study the missing concept, and leave time before trying a fresh question set.

Using unauthorized question dumps

Exam dumps can be inaccurate, outdated, and inconsistent with certification rules. Use official learning material and original practice questions that teach the published objectives.

Skipping hands-on practice

Simple actions such as opening an issue or pull request turn abstract words into a memorable workflow. Reading alone is less effective for many students.

GH-900 exam-day tips

• Schedule through the official certification page and confirm your time zone.
• Use a personal Microsoft account for exam registration when possible. Microsoft warns that records tied to an organizational work or school account can become unrecoverable if you leave that organization.
• Complete the official exam sandbox so you know how navigation, review markers, and the timer work.
• Read the testing provider’s system and identification requirements before exam day.
• Answer the question being asked, not a more advanced problem you imagine.
• Eliminate options that solve a different task. For example, Actions automate a workflow, while Projects track work.
• Watch the clock, but do not rush through easy definitions.
• Remember that Microsoft Learn is not available during GitHub exams, according to Microsoft’s exam experience policy. Prepare to answer without opening documentation.
• Check the current retake policy before scheduling another attempt. The certification page states that a first retake may be taken after 24 hours, while later waiting periods vary.

Microsoft GH-900 frequently asked questions

What is the Microsoft GH-900 exam?

GH-900 is the certification exam for GitHub Foundations. It validates beginner knowledge of Git, GitHub repositories, collaboration, project management, modern development tools, privacy and security, administration, and the GitHub community.

Is GH-900 the same as GitHub Foundations?

GH-900 is the exam code, while GitHub Foundations is the name of the certification. You may see students search for “Microsoft GH-900,” “GitHub GH-900,” or “GitHub Foundations exam”; these phrases refer to the same exam path.

Is GH-900 suitable for beginners?

Yes. Microsoft labels the certification as beginner level. Basic hands-on familiarity is still recommended because it helps you understand scenario questions.

Do I need to know programming for GH-900?

Advanced coding is not required. You should understand how files, changes, branches, commits, and pull requests fit together. Basic Markdown and simple repository practice are more important than learning a programming language for this exam.

Are there prerequisites for the GH-900 exam?

The official page does not list a required certification or training prerequisite. Candidates should have foundational knowledge of GitHub and its core features.

How difficult is the GH-900 exam?

GH-900 is a foundational exam, but it can still be challenging for someone who has only memorized definitions. Its breadth is the main difficulty: students must distinguish many related GitHub features and apply them to short situations.

How long is the GH-900 exam?

The official certification page currently provides 100 minutes to complete the assessment. Your total appointment time may also include instructions, agreements, and other check-in activities.

What score do I need to pass GH-900?

The current official study guide says that a score of 700 or greater is required to pass. This is a scaled score, so it should not be interpreted as a guaranteed requirement to answer exactly 70% of questions correctly.

How many questions are on the GH-900 exam?

Microsoft does not publish a fixed GH-900 question count on the certification page, and exam forms can change. Prepare for the full topic outline instead of planning around an unofficial number found on a blog or forum.

What question types appear on GH-900?

Microsoft protects exam security and does not promise specific formats in advance. Use the official exam sandbox to become familiar with the testing interface and representative interaction styles.

Is the GH-900 exam open book?

No. Microsoft states that access to Microsoft Learn is not available during GitHub exams. Do not expect to search documentation while answering questions.

Can I take GH-900 online?

The exam is proctored and scheduled through Pearson VUE. Available delivery options and check-in requirements can depend on location and current provider policies, so confirm the choices shown during official scheduling.

How much does the GH-900 exam cost?

The official page displays pricing according to the country or region where the exam is proctored. Select your location on the official page for the current amount rather than relying on a universal price quoted elsewhere.

Which languages are available for GH-900?

At the time of this update, the official page lists English, Spanish, Portuguese (Brazil), Korean, and Japanese. Check again before scheduling because availability can change.

Does GH-900 include GitHub Copilot?

Yes. The current outline includes AI-powered code suggestions, Copilot agents, Agent Mode, multi-model support, and broad differences among Copilot offerings. Focus on capabilities, responsible review, and policy concepts.

Does GH-900 include GitHub Actions?

Yes. You should understand why Actions is used and recognize common automation scenarios such as testing, building, and deployment. Foundations candidates do not need to master every advanced workflow configuration.

How much Git command knowledge do I need?

Focus first on the concepts behind repositories, commits, branches, and merges. Hands-on familiarity with a few common operations is useful, but the published outline emphasizes understanding Git and GitHub rather than memorizing a long list of command options.

How long should I study for GH-900?

There is no single correct number of days. A student who already uses GitHub may need one or two weeks of focused review, while a complete beginner may prefer four to six weeks. Set your schedule using diagnostic results, not someone else’s timetable.

How many practice tests should I take?

Quality matters more than quantity. One diagnostic test, several domain quizzes, and two or more fresh timed mock tests are a sensible starting structure. Continue until your performance is consistent and you can explain the answers.

What should I do if I fail GH-900?

Use the score report to identify weaker areas, review the current study guide, and complete new hands-on tasks before retesting. The official page says a first retake can be scheduled after 24 hours; waiting rules for later attempts vary, so read the current retake policy.