PracticeVideosBlogFlashcardsEspañol
All Practice Exams

Free Practice Questions for GitHub Foundations

Exam-style questions and explanations by OpenExamPrep.

✓ No registration✓ No credit card
Exam pass rate: ~80%
133+ Questions
100% Free

Loading practice questions...

Same family resources

Explore More GitHub Certifications

Continue into nearby exams from the same family. Each card keeps practice questions, study guides, flashcards, videos, and articles in one place.

GitHub Actions Certification

Practice QuestionsStudy Guide1 blog

GitHub Certified: Agentic AI Developer (GH-600)

Practice QuestionsStudy GuideCheat SheetFlashcards

GitHub Administration (GH-100)

Practice Questions

GitHub Advanced Security (GHAS) Certification

Practice Questions

GitHub Copilot Certification

Practice Questions

More From This Family

Videos and articles for deeper review.

VideoGitHub Foundations Exam Guide 2026: GH-900 Prep That Uses GitHubThis examArticleGitHub Foundations Exam Guide 2026: GH-900 Prep That Uses GitHub7 min readArticleGitHub Actions Certification Guide 2026: GH-200 Exam14 min read
Exam Review

Key Facts: GitHub Foundations Exam

75

Scored Questions

GitHub

70%

Passing Score

GitHub

120 min

Exam Duration

GitHub

$99

Exam Fee

GitHub

3 years

Validity

GitHub

30%

Collaboration Domain

Largest domain

The GitHub Foundations exam has 75 scored questions (plus ~10-15 pretest) in 120 minutes with a passing score of 70%. Key domains: Collaboration Features (30%), Introduction to Git and GitHub (22%), Project Management and Security (15%), Modern Development (13%), and Community/Open Source (12%). No prerequisites required. $99 exam fee. Certification valid for 3 years. Available online proctored.

Sample GitHub Foundations Practice Questions

Try these sample questions to review concepts for the GitHub Foundations exam. Each question includes a detailed explanation. Start the interactive quiz above for the full 133+ question experience with AI tutoring.

1What is a Git repository?
A.A cloud-based file storage service
B.A data structure that stores the history of a project including all files, commits, and branches
C.A type of database for storing user credentials
D.A tool for deploying applications to production
Explanation: A Git repository is a data structure that tracks the complete history of a project, including all files, commits, branches, and metadata. It can exist locally on a developer's machine or remotely on a platform like GitHub. The repository stores snapshots of changes over time, enabling version control. Exam tip: Understand that a repository contains the entire history, not just the current state.
2Which command creates a new branch in Git?
A.git new branch-name
B.git branch branch-name
C.git create branch-name
D.git init branch-name
Explanation: The command 'git branch branch-name' creates a new branch in Git. This creates a pointer to the current commit but does not switch to the new branch. To create and switch in one command, use 'git checkout -b branch-name' or 'git switch -c branch-name'. Exam tip: 'git branch' without arguments lists existing branches; with a name argument it creates one.
3What is the purpose of a pull request on GitHub?
A.To download code from a remote repository
B.To propose changes and request that they be reviewed and merged into a branch
C.To pull the latest changes from a remote branch
D.To request access to a private repository
Explanation: A pull request (PR) on GitHub is a mechanism for proposing changes from one branch to another. It enables code review, discussion, and collaboration before changes are merged. Pull requests can include reviewers, labels, milestones, and linked issues. They are central to GitHub's collaborative workflow. Exam tip: Pull requests are not the same as 'git pull' — PRs are a GitHub feature for code review and collaboration.
4What does 'git clone' do?
A.Creates an empty repository on GitHub
B.Creates a local copy of a remote repository including all branches and history
C.Copies only the latest commit from a remote repository
D.Merges two repositories together
Explanation: 'git clone' creates a complete local copy of a remote repository, including all files, branches, commits, and history. It automatically sets up the remote origin and checks out the default branch. This is different from downloading a ZIP, which doesn't include Git history. Exam tip: Cloning preserves the full repository history and sets up the remote tracking automatically.
5Which GitHub feature allows you to automate workflows such as CI/CD pipelines?
A.GitHub Pages
B.GitHub Actions
C.GitHub Packages
D.GitHub Discussions
Explanation: GitHub Actions is GitHub's built-in CI/CD and automation platform. It allows you to create workflows triggered by events (push, pull request, schedule, etc.) using YAML configuration files stored in the .github/workflows directory. Actions can build, test, deploy code, and automate any task. Exam tip: GitHub Actions workflows are defined in YAML files and consist of jobs that run on runners (GitHub-hosted or self-hosted).
6What is the difference between 'git fetch' and 'git pull'?
A.They are identical commands
B.'git fetch' downloads changes but does not merge them; 'git pull' downloads and merges changes
C.'git fetch' uploads changes; 'git pull' downloads changes
D.'git fetch' works with tags only; 'git pull' works with branches only
Explanation: 'git fetch' downloads commits, files, and references from a remote repository but does not merge them into your working branch. 'git pull' is effectively 'git fetch' followed by 'git merge' — it downloads and integrates the changes. Using fetch first allows you to review changes before merging. Exam tip: 'git pull' = 'git fetch' + 'git merge'. Use fetch when you want to inspect changes before integrating them.
7What is a GitHub Issue?
A.A bug in GitHub's platform
B.A feature for tracking tasks, bugs, feature requests, and discussions related to a repository
C.A type of Git conflict that needs resolution
D.A security vulnerability report
Explanation: GitHub Issues is a tracking tool for tasks, bugs, enhancements, and other items related to a repository. Issues can be assigned to users, labeled, added to milestones and projects, and linked to pull requests. They serve as the primary project management and communication tool within GitHub repositories. Exam tip: Issues can be closed automatically by referencing them in commit messages or pull requests using keywords like 'closes #123'.
8What is a merge conflict in Git?
A.An error that occurs when cloning a repository
B.A situation where Git cannot automatically merge changes because the same lines were modified in different branches
C.A conflict between local and remote repository settings
D.An error in the .gitignore file
Explanation: A merge conflict occurs when Git cannot automatically reconcile differences between two branches being merged — typically when the same lines of a file were modified differently in each branch. Git marks the conflicting sections in the file, and the developer must manually resolve them by choosing which changes to keep. Exam tip: Conflict markers (<<<<<<, ======, >>>>>>) indicate the conflicting sections. After resolving, stage the file and complete the merge.
9What is the purpose of the .gitignore file?
A.To list files that should be deleted from the repository
B.To specify files and directories that Git should not track
C.To configure Git user settings
D.To define branch protection rules
Explanation: The .gitignore file tells Git which files and directories to exclude from version control. Common entries include build artifacts, dependency directories (node_modules), IDE configuration files, and sensitive data (.env files). Patterns in .gitignore support wildcards and directory matching. Exam tip: Files already tracked by Git are not affected by adding them to .gitignore — use 'git rm --cached' to untrack them first.
10Which GitHub plan provides free unlimited public AND private repositories with unlimited collaborators?
A.GitHub Free for personal accounts
B.GitHub Team
C.GitHub Enterprise
D.GitHub Pro
Explanation: GitHub Free for personal accounts provides unlimited public and private repositories. Private repositories on the free plan can have unlimited collaborators (this was updated in 2020 — previously limited to 3). The free plan includes 500 MB of GitHub Packages storage, 2,000 GitHub Actions minutes per month, and community support. Exam tip: GitHub Free is very generous — know what's included vs. what requires a paid plan.

About the GitHub Foundations Exam

The GitHub Foundations Certification validates foundational knowledge of Git version control, GitHub collaboration features, and the GitHub ecosystem. Launched in 2024, it covers repositories, pull requests, GitHub Actions, Copilot, security features, and open source practices. It is GitHub's entry-level certification and requires no prior experience.

Exam sponsor: GitHub / PSI. The requirements and fees below concern the certification or admission exam, separate from our free practice resources.

Questions

75 questions

Time Limit

120 minutes (2 hours)

Passing Score

70%

Exam / Certification Fees

$99

Exam sponsor website

Reported exam pass rate: ~80%. for well-prepared candidates (industry estimate) This describes exam candidates, not OpenExamPrep users or results from using our resources. Exam sponsor website

Fees, eligibility, and exam policies can change. Confirm them with the exam sponsor before applying or paying.

Our practice resources: topics covered

We aim to reflect publicly available exam outlines and topic information in our study resources. Coverage, format, and difficulty may differ from the actual exam, and we cannot guarantee that every detail is accurate or current. Confirm exam requirements, fees, and policies with the official exam sponsor.

22%

Introduction to Git and GitHub

Git basics, repositories, commits, branches, version control concepts, and the GitHub ecosystem

8%

Working with GitHub Repositories

Creating repos, managing files, settings, templates, visibility, README, and license files

30%

Collaboration Features

Pull requests, issues, code review, branch protection, GitHub flow, labels, milestones, and projects

13%

Modern Development

GitHub Actions, Copilot, Codespaces, Packages, and CI/CD workflows

15%

Project Management and Security

GitHub Projects, Dependabot, secret scanning, code scanning, 2FA, and audit logs

12%

Community and Open Source

Open source licensing, contributing workflows, inner source, GitHub Sponsors, and community health files

Preparing for the GitHub Foundations Exam

What You Need to Know

  • Passing score: 70%
  • Exam length: 75 questions
  • Time limit: 120 minutes (2 hours)
  • Exam / certification fees: $99 Official sources

Using Our Practice Resources

  • Work through all 133 available questions
  • Review every answer and explanation
  • Track weak areas and revisit them
  • Use our AI tutor for tough concepts

GitHub Foundations: Suggested Study Strategy

1Focus on Collaboration Features (30%) — master pull requests, code review, issues, GitHub flow, and branch protection
2Create a GitHub account and practice hands-on — create repos, branches, PRs, and issues to build muscle memory
3Learn GitHub Actions basics — know workflow triggers, YAML structure, jobs, steps, runners, and secrets
4Understand open source licensing differences — MIT (permissive), Apache (patent), GPL (copyleft)
5Know GitHub security features — Dependabot, secret scanning, code scanning, 2FA, and the dependency graph

Frequently Asked Questions

What is the GitHub Foundations certification?

The GitHub Foundations certification validates foundational knowledge of Git, GitHub collaboration features, and the GitHub ecosystem. Launched in 2024, it is GitHub's entry-level certification covering repositories, pull requests, GitHub Actions, Copilot, security features, and open source practices. No prior experience is required.

How many questions are on the GitHub Foundations exam?

The exam has approximately 75 scored questions plus 10-15 unscored pretest questions, for a total of about 85-90 questions in 120 minutes. The passing score is 70%. Questions are multiple-choice and test conceptual understanding of Git and GitHub features.

What is the largest domain on the GitHub Foundations exam?

Collaboration Features is the largest domain at 30% of the exam. It covers pull requests, issues, code review, GitHub flow, branch protection rules, CODEOWNERS, labels, milestones, and GitHub Projects. Focus your study time here along with Git/GitHub Basics (22%).

How should I prepare for the GitHub Foundations exam?

Plan for 20-40 hours of study over 1-3 weeks. Use the free GitHub Skills courses and Microsoft Learn paths as your primary study materials. Create a GitHub account and practice the features hands-on. Focus on Collaboration Features (30%) and Git/GitHub Basics (22%). Complete 100+ practice questions and aim for 80%+ before scheduling.

Is the GitHub Foundations certification worth it?

Yes — GitHub is the world's largest development platform with 100M+ developers. The certification validates skills employers look for in DevOps, software development, and technical roles. At $99 it is affordable, requires no prerequisites, and complements cloud certifications (AWS, Azure). The certification is valid for 3 years.

What are the prerequisites for the GitHub Foundations exam?

There are no prerequisites — anyone can take the exam regardless of education or experience level. It is designed as an entry-level certification. GitHub recommends familiarity with Git basics and having used GitHub, but this is not required. Free learning resources are available on GitHub Skills and Microsoft Learn.