GitHub Foundations GH-900 Practice Test & Mock Exam

Last revised: June 29, 2026

Practice GitHub Foundations (GitHub Foundations GH-900) in IT Mastery with focused sample pages, topic drills, timed mock exams, detailed explanations, and the current question bank.

Use IT Mastery for interactive practice with timed mocks, topic drills, progress tracking, and detailed explanations across web and mobile. Focused topic pages and the static diagnostic page preview how this exam handles Git basics, repositories, pull requests, issues, collaboration workflows, project management, security, administration, and community concepts.

Practice preview and focused pages

Use this page to start the web app and choose the right public preview before longer mixed practice. For sample exam questions, use the focused topic pages, quick review, and free-practice page in this exam section; the interactive app remains the primary practice path.

  • Focused topic pages: drill focused topics including Modern Development; Collaborate Using Github; and other domains with explanations.
  • Quick review: Git, GitHub collaboration, repositories, pull requests, GitHub Actions, security, and project workflows before question-bank practice.
  • Free practice exam: Try 50 free GitHub Foundations (GitHub Foundations GH-900) questions across the exam domains, with explanations, then continue with IT Mastery practice.

What this GH-900 practice page gives you

  • a direct web entry for GitHub Foundations practice in IT Mastery
  • focused topic pages and free-practice coverage for previewing question style
  • Git, repository, pull request, issue, project, security, and collaboration workflow drills
  • a clear web preview path for previewing question style before deeper practice
  • the same IT Mastery account across web and mobile

GitHub Foundations snapshot

  • Vendor: GitHub
  • Credential name: GitHub Foundations
  • Microsoft Learn study-guide code: GH-900
  • Level shown by Microsoft Learn: Beginner
  • Exam time shown by Microsoft Learn: 100 minutes
  • IT Mastery practice modes: topic drills, mixed sets, timed mocks, detailed explanations, and progress tracking
  • Current IT Mastery status: live practice available

Topic coverage for Foundations practice

AreaWhat to practise
Git and GitHub basicsversion control, commits, branches, repositories, remotes, and core GitHub vocabulary
Repositoriesrepository structure, issues, pull requests, discussions, releases, and visibility
Collaborationforks, branches, reviews, comments, merge behavior, and contribution workflows
Modern developmentproject boards, GitHub Pages, packages, Codespaces awareness, and community workflows
Privacy, security, and administrationaccount security, repository permissions, organizations, and basic governance

GitHub collaboration flow

Most GitHub Foundations questions test whether you understand the basic path from local work to shared review. Keep this workflow straight before memorizing isolated terms.

    flowchart LR
	  Clone["Clone or open repo"] --> Branch["Create branch"]
	  Branch --> Commit["Commit changes"]
	  Commit --> Push["Push branch"]
	  Push --> PullRequest["Open pull request"]
	  PullRequest --> Review["Review and checks"]
	  Review --> Merge["Merge"]
	  Merge --> Release["Release or deploy"]

Foundations exhibit patterns to practise

GitHub Foundations questions usually use small, practical exhibits: a repository screen, pull request state, issue thread, branch list, or workflow check result. Start by identifying the GitHub object in the exhibit, then choose the action that matches the normal collaboration workflow.

Exhibit typeWhat to recognize
Repository file listthe repository is the project container for code, history, issues, pull requests, and releases
Branch listwork can be isolated before merging into the default branch
Pull request statusreview comments, checks, conflicts, and approvals affect merge readiness
Issue threaddiscussion, bug reporting, and task tracking can happen before code changes
Fork noticeexternal contributors can propose changes without direct write access
Release pagea versioned package can include notes, tags, and downloadable assets

Example pull request exhibit:

Pull request: Add password reset email template
Checks: 1 failing
Review: changes requested
Merge button: disabled

Best reading: the pull request is not ready to merge. The contributor should address the failing check and review feedback, then request review again.

Example issue exhibit:

Issue title: Login page returns 500 for locked accounts
Labels: bug, needs-triage
Assignee: unassigned
Linked pull request: none

Best reading: this is an issue, not a code change yet. The next step is triage, reproduction, assignment, or discussion before a pull request is opened.

Example branch exhibit:

BranchMeaning
maindefault branch used for reviewed work
feature/reset-emailisolated feature work before review
hotfix/login-errorfocused fix branch that should still go through the repository’s review rules

GH-900 decision filters

Use these filters when the answer is about normal GitHub workflow rather than memorized vocabulary:

  • Object type: identify whether the scenario is about a repository, branch, commit, issue, pull request, release, discussion, project, or organization.
  • Collaboration step: decide whether the next action is branch, commit, push, open pull request, review, fix checks, merge, release, or close issue.
  • Permission boundary: distinguish read, triage, write, maintain, admin, organization membership, fork access, and external contributor patterns.
  • Security baseline: watch for account security, 2FA, secret exposure, branch protection, required checks, and repository visibility.
  • Community signal: separate issues, discussions, pull requests, README guidance, codes of conduct, and contribution instructions.

Final 7-day GH-900 practice sequence

DayPractice focus
7Open the web app for a timed mixed set, then use the public diagnostic page if you need to tag misses by Git, repository, collaboration, security, or community topic.
6Drill Git basics, commits, branches, remotes, repositories, forks, and GitHub vocabulary.
5Drill pull requests, reviews, checks, merge behavior, conflicts, issues, and discussions.
4Drill project management, releases, packages, Codespaces awareness, GitHub Pages, and modern development basics.
3Drill privacy, security, repository visibility, permissions, organizations, and administration basics.
2Complete a timed mixed set and explain the GitHub object or workflow step behind each miss.
1Review weak workflow terms; avoid memorizing isolated interface labels without context.

When GH-900 practice is enough

If several unseen mixed attempts are above roughly 75% and you can explain the GitHub object, permission boundary, or collaboration step behind your misses, you are likely ready. Further practice should improve workflow fluency, not simply repeat definitions.

Free study resources

Use this IT Mastery page for live practice, topic drills, timed mocks, explanations, and app access.

Web preview and premium practice

  • Web/public preview: focused sample-question pages plus the web app entry so you can validate the question style and explanation depth.
  • Premium: interactive web-app practice with focused drills, mixed sets, timed mock exams, detailed explanations, and progress tracking across web and mobile.

Mini Glossary

  • Branch: A movable line of development in Git history.
  • Commit: A recorded snapshot of repository changes.
  • Fork: A personal or organization-owned copy of another repository.
  • Issue: A GitHub item for tracking bugs, requests, tasks, or discussion.
  • Pull request: A request to review and merge proposed changes.
  • Repository: The main GitHub project container for code and collaboration.
  • Release: A versioned package of project history, notes, and optional assets.
  • Remote: A Git repository location that local Git can fetch from or push to.

Official sources

In this section

GH-500
Browse Certification Practice Tests by Exam Family