Exam Code: GH-900
Exam Name: GitHub Foundations
Price: $68.00 $58.88
Exam Questions: 144 Q&As
Last Updated: 2026-10-15
Prepare for the GH-900 GitHub Foundations exam with focused practice in version control, repositories, collaboration, modern development tools, project tracking, and security.
GitHub Foundations validates your understanding of the features and workflows that help people contribute, collaborate, and manage work on GitHub.
The exam suits developers, non-developers, and other GitHub users who want a foundation in the platform. Preparation should combine terminology with practical choices: where to record a task, how to propose a change, which development tool fits a situation, and how permissions affect collaboration.
New developers, project contributors, administrators, app makers, students, and team members who coordinate work through GitHub can benefit from this certification. You should be comfortable navigating a repository and following a basic contribution workflow.
Create a practice repository, write a README, open an issue, create a branch, commit a change, and submit a pull request. Then organize the work in a Project and explore repository permissions and development tools.
The current outline has seven domains. Published weights are ranges, so they should guide study priorities rather than be converted into exact question counts.
Explain version control, repositories, commits, branches, GitHub account types, and GitHub Flow. Recognize uses for Markdown, GitHub Desktop, and GitHub Mobile.
Understand repository files, templates, branches, file management, maintenance, and insights. Know when README, LICENSE, CONTRIBUTING, CODEOWNERS, and SECURITY files serve different needs.
Choose issues, pull requests, and discussions for the right interaction. Use assignments, templates, notifications, Gists, Wikis, and GitHub Pages to coordinate and share work.
Recognize GitHub Actions, Copilot capabilities and plans, Codespaces, dev containers, and github.dev. Pay attention to which tool supplies automation, AI assistance, editing, or a development environment.
Organize work with Projects, layouts, labels, milestones, workflows, assignees, and saved replies. Interpret project insights as a way to understand progress.
Review 2FA, passkeys, permissions, roles, teams, repository visibility, branch protection, Enterprise Managed Users, and organization-wide Copilot policies.
Understand open source, Sponsors, Marketplace, following activity, and InnerSource. Distinguish forks and templates when participating in or starting a project.
Git tracks versions; GitHub adds hosting and collaboration. A branch is a line of development within a repository, while a fork creates a repository under another owner. github.dev supports browser editing, while Codespaces supplies a development environment with compute and a terminal.
Days 1–2: Git, GitHub Flow, branches, and repository files. Day 3: issues, pull requests, discussions, and notifications. Day 4: Actions, Copilot, Codespaces, and github.dev. Day 5: Projects and security. Day 6: community and InnerSource. Use day 7 for mixed questions and repeating the workflows you missed.
A common source of wrong answers is choosing a familiar feature that solves a different problem. Ask whether the scenario needs change review, work tracking, documentation, automation, account protection, or an execution environment before selecting the tool.
These five study questions cover collaboration, Projects layouts, Git branches, repository insights, and templates. They are provided for practice and are not official examination items.
As a user, what feature can you use to merge proposed changes in a repository on GitHub?
Correct answer: B
Explanation: Pull requests provide the workflow for proposing, reviewing, and merging changes, subject to permissions and repository rules.
Common mistake: Confusing the record of a task with the workflow that merges its code changes.
Why the other options are wrong: A tracks tasks and bugs. C organizes work. D supports conversations; none is the change-merging feature.
What layouts are available for GitHub Projects? (Choose three.)
Correct answers: A, C, and D
Explanation: The three named layouts are Roadmap, Board, and Table. Board is a kanban-style view; Kanban is not a separate fourth layout.
Common mistake: Counting Kanban and Board as two different layout types.
Why the other options are wrong: B describes the style of the Board layout rather than an additional layout. E describes a collection of work, which can be displayed through the available layouts.
Which of the following best describes a branch in Git?
Correct answer: A
Explanation: A Git branch is a reference to a commit. As new commits are created on that branch, its reference advances, allowing a separate line of development without copying the repository.
Common mistake: Taking the informal description of an isolated workspace literally. A branch is not a physical copy of the codebase.
Why the other options are wrong: B describes copying files. C implies a separate copy rather than a commit reference. D describes a fork.
Where should a repository admin navigate to view pre-built visualizations from repository data?
Correct answer: C
Explanation: The repository Insights tab provides repository activity and related visualizations. Available reports can depend on the repository and plan.
Common mistake: Confusing repository Insights with charts configured inside GitHub Projects.
Why the other options are wrong: A contains configuration. B contains work items. D is not the repository tab used to access these reports.
How can a user create a repository template, and what permissions are required?
Correct answer: A
Explanation: A user with admin permissions can mark the repository as a template from its repository Settings. Others can then use the template to create a new repository with its starting structure and files.
Common mistake: Confusing organization settings with the settings of the individual repository.
Why the other options are wrong: B and C use the wrong settings location. D specifies Maintain rather than the required admin permissions.
Check the product revision date and coverage list. The January 2026 outline includes updated Copilot topics, account security, project features, and the distinction between github.dev and Codespaces.
No. A product's bank total describes the study items available in that package. The reviewed official pages do not publish a fixed GH-900 question count. Check the listing for the current bank size and your appointment for exam details.
Check the listing for a sample or request one. Look for clear feature distinctions, realistic scenarios, readable formatting, and explanations that address incorrect choices.
Review supported operating systems, browser requirements, activation limits, and offline access for your selected edition. PDF and testing-engine editions may have different requirements.
Confirm the update period and eligibility in the product terms. Updates should reflect changes to the exam outline and corrections to questions or explanations.
An exam voucher is included only when the listing explicitly says so. Practice material, training, and Pearson VUE registration are generally separate purchases.
Review the current digital-product terms before downloading or activating the package. Check the refund window and the procedure for reporting duplicate purchases or technical problems.
Build confidence choosing the right repository, collaboration, development, and security features for everyday tasks.
CertQuestionsBank is an independent preparation provider and is not affiliated with or endorsed by GitHub or Microsoft. Exam details and objectives can change. GitHub, Microsoft, and related marks belong to their respective owners.
Your email address will not be published. Required fields are marked *
All third-party certification names, exam codes, and trademarks belong to their respective owners. Certquestionsbank is independently operated and is not affiliated with, endorsed by, or authorized by any certification provider.
