Free Microsoft GH-900 Exam Actual Questions & Explanations

Last updated on: Jul 17, 2026
Author: Ethan Bennett (Microsoft Learning Content Specialist)

The Microsoft GH-900 exam validates your foundational knowledge of GitHub and Git workflows within the Microsoft GitHub Certifications program. This exam is designed for developers, IT professionals, and technical teams who work with GitHub daily or plan to adopt it in their organization. The GitHub Foundations certification demonstrates competency in core version control concepts, repository management, and collaborative development practices. This page provides a structured study roadmap and resources to help you prepare effectively and confidently.

GH-900 Exam Syllabus & Core Topics

Use this topic map to guide your study for Microsoft GH-900 (GitHub Foundations) within the Microsoft GitHub Certifications path.

  • Introduction to Git and GitHub: Understand version control fundamentals, the difference between Git and GitHub, and how distributed version control enables team collaboration. You should be able to explain core concepts like commits, branches, and the GitHub workflow.
  • Working with GitHub Repositories: Create, clone, and manage repositories. Configure repository settings, manage branches, and perform common operations like pushing, pulling, and fetching changes from remote sources.
  • Collaboration Features: Use pull requests, code reviews, and issue tracking to coordinate work across teams. Understand how to request reviews, provide feedback, and merge contributions while maintaining code quality.
  • Modern Development: Apply GitHub to contemporary development practices including continuous integration, automated testing, and deployment workflows. Recognize how GitHub Actions and other tools support modern software delivery.
  • Project Management: Organize work using GitHub Projects, milestones, and labels. Track progress, prioritize tasks, and communicate project status across team members.
  • Privacy, Security, and Administration: Configure access controls, manage permissions, enable security features, and enforce organizational policies. Understand authentication, authorization, and best practices for protecting code and data.
  • Benefits of the GitHub Community: Recognize how open source contributions, community engagement, and GitHub's ecosystem support professional growth and organizational innovation.

Question Formats & What They Test

The GH-900 exam uses multiple question types to assess both conceptual understanding and practical decision-making in real GitHub scenarios.

  • Multiple choice: Test your knowledge of Git terminology, GitHub features, and standard workflows. Questions focus on definitions, feature behavior, and best practices.
  • Scenario-based items: Present realistic team situations, such as resolving merge conflicts, managing access for new contributors, or choosing the right branching strategy, and ask you to select the best approach.
  • Simulation-style tasks: Guide you through GitHub interface navigation, repository configuration, and workflow execution to verify hands-on capability.

Questions progress in difficulty and emphasize practical application, ensuring you can apply GitHub knowledge to actual development and team scenarios.

Preparation Guidance

Structure your study around the seven core topic areas, allocating time based on your current experience level. A balanced approach combines conceptual review with hands-on practice and mock testing to build confidence and speed.

  • Map Introduction to Git and GitHub, Working with GitHub Repositories, Collaboration Features, Modern Development, Project Management, Privacy, Security, and Administration, and Benefits of the GitHub Community to weekly study goals. Track progress and adjust pace as needed.
  • Work through practice question sets; review detailed explanations to identify and close knowledge gaps.
  • Connect features and concepts across real workflows, for example, how branching strategies support collaboration, how pull requests enable code review, and how security settings protect organizational assets.
  • Complete a timed mini-mock exam under realistic conditions to build pacing, reduce test anxiety, and identify final weak areas.
  • In your final week, focus on scenario-based questions and review any topics where you scored below target.

Explore other Microsoft certifications: view all Microsoft exams.

Get the PDF & Practice Test

Strengthen your preparation with up-to-date resources from validexamdumps.com. These materials align to GH-900 and cover practical scenarios with clear explanations.

  • Q&A PDF with explanations: Topic-mapped questions that clarify why correct options are right and others aren't.
  • Practice Test: Realistic items, timed and untimed modes, progress tracking, and detailed review to simulate exam conditions.
  • Focused coverage: Aligned to Introduction to Git and GitHub, Working with GitHub Repositories, Collaboration Features, Modern Development, Project Management, Privacy, Security, and Administration, and Benefits of the GitHub Community so you study what matters most.
  • Regular reviews: Content refreshes that reflect syllabus and product changes.

Visit the exam page to download the PDF, Online Practice Test, or get a Bundle Discount offer for both formats: GitHub Foundations.

Frequently Asked Questions

Which topics carry the most weight on the GH-900 exam?

Working with GitHub Repositories and Collaboration Features typically account for a significant portion of the exam. However, all seven topic areas are represented, so a well-rounded study plan is essential. Focus extra effort on hands-on repository tasks and pull request workflows, as these are foundational to daily GitHub use.

How do the seven topic areas connect in a real project workflow?

In practice, they form a complete cycle: you start with Git and GitHub fundamentals, create and manage repositories, collaborate through pull requests and code reviews, integrate modern CI/CD practices, organize work via project management tools, enforce security and access controls, and benefit from community contributions. Understanding these connections helps you see the exam as a cohesive skill set rather than isolated topics.

How much hands-on experience do I need, and which labs should I prioritize?

Hands-on experience significantly boosts exam performance and real-world readiness. Prioritize labs that cover cloning repositories, creating branches, opening pull requests, and merging changes. If possible, practice resolving merge conflicts, configuring repository settings, and using GitHub Actions in a CI/CD workflow. Even 2-3 hours of guided practice per week accelerates learning.

What common mistakes do candidates make on GH-900?

Many candidates confuse Git concepts (local operations) with GitHub features (cloud collaboration). Others underestimate the importance of security and administration topics, which appear more frequently than expected. Additionally, some rush through scenario-based questions without carefully reading all options. Slow down on these items and consider the full context before selecting your answer.

What is the best strategy for the final week before the exam?

Shift focus to scenario-based and simulation-style questions, as these most closely mirror exam conditions. Review any topics where your practice test scores fell short. Take one full-length timed mock exam 2-3 days before the real exam, then spend the final days doing light review and rest. Avoid cramming new material; instead, reinforce what you already know and build confidence.

Question No. 1

Which of the following is the first step in the GitHub flow?

Show Answer Hide Answer
Correct Answer: D

GitHub flow is a lightweight workflow used to safely introduce changes into a repository. The first step is to create a branch for your changes. A branch gives you an isolated workspace where you can develop a feature, fix a bug, or test an idea without directly affecting the main branch. After creating the branch, you make commits and push those changes. Then you open a pull request so others can review and discuss the work. Once the pull request is approved, it can be merged into the main branch. Deleting the branch happens only after the work has been merged and the branch is no longer needed. Therefore, branch creation comes first.


Question No. 2

Which Insights feature allows users to view repository activity including: pull requests, issues, and commit history?

Show Answer Hide Answer
Correct Answer: C

Question No. 3

Which of the following options is available as a default Discussion category?

Show Answer Hide Answer
Correct Answer: C

In GitHub Discussions, several default categories are provided to help organize conversations within a project. One of the default categories is Show and tell. This category is designed for users to showcase their work, share progress, or discuss achievements with the community. The other options listed (Bug report, Daily check-in, Security concern) are not default categories but could be custom categories created by the repository maintainers.

=================


Question No. 4

A centralized version control system is a system that:

Show Answer Hide Answer
Correct Answer: C

A centralized version control system stores the main project history in one central location, usually a server. Developers connect to that server to check out files, make changes, and submit updates. This differs from Git, which is distributed and allows every developer to have a full local copy of the repository history. In a centralized model, collaboration depends heavily on the availability of the central server. If the server is unavailable, developers may be limited in what they can do. GitHub Foundations emphasizes this distinction because GitHub is built around Git, a distributed version control system. Option C correctly describes centralized version control because the central server holds the authoritative project history.


Question No. 5

Who can be assigned to an Issue or pull request?

(Each answer presents a complete solution. Choose two.)

Show Answer Hide Answer
Correct Answer: B, D

In GitHub, issues and pull requests (PRs) are essential tools for managing work and collaboration in a project. Assigning individuals to these issues or PRs is a way to indicate responsibility for addressing the issue or completing the PR.

Anyone with write permissions to the repository:

Users who have write permissions to a repository can be assigned to issues and pull requests. Write permissions allow users to push changes to the repository, create branches, and modify issues and pull requests. Assigning them to an issue or PR ensures they are recognized as responsible for the task.

Anyone who has commented on the Issue or pull request:

GitHub allows you to assign issues or pull requests to users who have already engaged with the discussion by commenting on it. This feature is particularly useful for quickly assigning tasks to those who are already involved in the conversation.

Incorrect Options:

Option A is incorrect because having an enterprise GitHub account alone does not necessarily grant the ability to be assigned to issues or PRs. Permission to assign is based on repository-specific roles and permissions.

Option C is incorrect because not all personal GitHub accounts can be assigned to issues or PRs. The user needs either write permissions to the repository or must have commented on the issue or PR.


GitHub Docs: Assigning Issues and Pull Requests

GitHub Docs: Permission Levels for a Repository

This detailed explanation provides clarity on GitHub's assignment mechanics for issues and pull requests, reflecting the platform's collaborative nature.

=================