36 free GitHub GH-900 Foundations practice questions from the CertStash pack of 142, each with the correct answer and a full explanation. The rule is the same for every exam: ten free on the product page, 36 free here, all 142 in the pack, and each step includes the one before it.
Get all 142 questions (US$39) · Download the first 10 as a PDF
Question 1
Which of the following keywords are used to link a pull request to an issue? (Choose three.)
Show answer and explanation
Correct answer: A, B, E. fix; resolves; closed
GitHub links a pull request to an issue, and closes the issue when the pull request is merged, when the description uses one of the supported keywords: close, closes, closed, fix, fixes, fixed, resolve, resolves or resolved. Fix, resolves and closed are all on that list.
Why the other options are wrong
- C. Merge is a Git operation and is not a supported keyword for linking a pull request to an issue.
- D. Join is not a supported GitHub keyword for linking a pull request to an issue.
- F. Connects is not a supported GitHub keyword for linking a pull request to an issue.
Question 2
Which syntax is used for authoring saved replies?
Show answer and explanation
Correct answer: D. Markdown
GitHub saved replies are authored using Markdown syntax. Markdown is the lightweight markup language used throughout GitHub for formatting text in issues, pull requests, comments, and other textual content. This includes saved replies, which support the full range of Markdown formatting options.
Why the other options are wrong
- A. HTML is not the syntax used for GitHub saved replies.
- B. YAML is a configuration language, not used for authoring saved reply content.
- C. Markup is too generic; GitHub specifically uses Markdown, not generic markup.
Question 3
As a user, what feature can you use to merge proposed changes in a repository on GitHub?
Show answer and explanation
Correct answer: C. pull requests
Pull requests are the primary GitHub feature designed to propose and merge changes into a repository. They allow developers to submit changes, request reviews, discuss modifications, and ultimately merge the proposed changes into the target branch. Pull requests are the core mechanism for collaborative development and code integration on GitHub.
Why the other options are wrong
- A. Discussions are for conversational collaboration, not for merging changes.
- B. Projects are organizational tools for managing tasks and workflows, not for merging code.
- D. Issues are for tracking bugs and feature requests, not for directly merging code changes.
Question 4
If there are multiple README files, which of the following locations will be displayed first?
Show answer and explanation
Correct answer: D. .gitHub
When a repository contains more than one README file, GitHub chooses which one to display in a set order. It checks the .github directory first, then the repository root, and then the docs directory. The README in .github is therefore displayed first.
Why the other options are wrong
- A. The docs directory is checked last, after the .github directory and the root.
- B. The root README is only displayed when there is no README in the .github directory.
- C. GitHub does not look in the src directory when choosing which README to display.
Question 5
Why is branching a core concept in Git?
Show answer and explanation
Correct answer: C. Branching creates an isolated environment to try new ideas and make changes without affecting other branches.
Branching is a core Git concept because it creates isolated environments where developers can experiment with new features and make changes without affecting other branches, particularly the main branch. This isolation enables parallel development, experimentation, and safe code changes that can be reviewed and merged only when ready.
Why the other options are wrong
- A. Branching does not automate merging; merging is a separate manual or explicit operation.
- B. Branches are not physical copies on disk; they are lightweight references to commits in the same repository.
- D. Git uses directories and files for organization, not branching; branching is for managing code versions and development workflows.
Question 6
What is the difference between Git and GitHub?
Show answer and explanation
Correct answer: A. Git is a command-line tool for tracking file changes, while GitHub is a platform for collaborating on Git repositories.
Git is a distributed version control system implemented as a command-line tool that tracks changes to files and manages version history locally and across networks. GitHub is a cloud-based hosting platform built on Git that provides web-based collaboration features, pull requests, issue tracking, and social features for teams working with Git repositories.
Why the other options are wrong
- B. Git and GitHub are distinct tools with different purposes; they are not different names for the same thing.
- C. Git is a distributed version control system, not a cloud service; GitHub is the cloud platform.
- D. Git is a distributed system, not centralized; this reverses the actual relationship between the two.
Question 7
What type of operations has Git been optimized for?
Show answer and explanation
Correct answer: A. local file manipulation and offline work
Git has been optimized for local file manipulation and offline work. Its distributed architecture allows developers to perform most operations, including committing, branching, and merging, without requiring a network connection. This optimization enables efficient local development workflows and makes Git highly performant for individual contributor work.
Why the other options are wrong
- B. Git is not optimized for real-time editing; it is designed for discrete commits and version snapshots.
- C. Git is not cloud-dependent; it is designed to work offline and locally.
- D. Git is a general-purpose version control system, not specifically optimized for web development.
Question 8
Which version control system is GitHub built on top of?
Show answer and explanation
Correct answer: C. Git
GitHub is built on top of Git, the distributed version control system. GitHub uses Git as its underlying version control engine and provides a web-based interface and collaboration platform around Git repositories and operations.
Why the other options are wrong
- A. Subversion is a different version control system; GitHub uses Git, not Subversion.
- B. Mercurial is an alternative version control system; GitHub is Git-based, not Mercurial-based.
- D. Perforce is a centralized version control system; GitHub is built on the distributed Git system.
Question 9
Without using advanced search syntax, what are some of the available default filters when searching through issues? (Choose two.)
Show answer and explanation
Correct answer: C, E. your issues; everything assigned to you
GitHub's default issue filters without advanced syntax include 'your issues' (issues assigned to you or created by you) and 'everything assigned to you' (issues where you are the assignee). These are the standard filtering options available in the basic search interface. The other options require more specific search syntax or are not part of the default filter set.
Why the other options are wrong
- A. Project-specific filtering requires navigation to that project rather than being a default global filter.
- B. Team-based filtering is not a standard default filter without using advanced search syntax.
- D. Filtering by comments requires advanced search syntax and is not a default filter option.
Question 10
What are achievements on a GitHub user profile?
Show answer and explanation
Correct answer: C. special recognition for significant contributions and milestones
Achievements on a GitHub user profile are special recognitions awarded for significant contributions and milestones reached on the platform. They serve as badges or markers of notable activity such as opening pull requests, making contributions during specific events, or reaching community engagement milestones. They are not related to repository counts, star counts, or coding challenge completions.
Why the other options are wrong
- A. Total repositories owned is a statistic displayed on profiles but is not an achievement.
- B. Stars received is a metric that can be tracked but does not constitute GitHub achievements.
- D. Coding challenge trophies are not part of GitHub's achievement system.
What people say about the full GH-900 pack 4.8 from 6
New version with real questions and accurate answers for GH-900 exam is great. Wonderful, I passed.
Wonderful, the GH-900 exam dumps effectively simplified challenging topics, and I'm delighted with my 75% passing score. Thanks very much!
90% real questions, passed my GH-900 exam successfully.
Question 11
When making comments in GitHub, the supported text language is:
Show answer and explanation
Correct answer: B. Markdown.
GitHub supports Markdown as the text formatting language for comments, issues, pull requests, and other communication features. Markdown provides a simple, human-readable syntax for formatting text with headers, lists, links, code blocks, and other elements.
Why the other options are wrong
- A. JSON is a data format, not a text formatting language used in GitHub comments.
- C. JavaScript is a programming language, not a text markup language for comments.
- D. XML is a data markup language, not the supported text format for GitHub comments.
- E. CSS is a styling language for web pages, not a text formatting language used in GitHub comments.
Question 12
Which of the following statements most accurately describes secret gists?
Show answer and explanation
Correct answer: B. Anyone with the URL for the gist can view the gist.
Secret gists are not listed on the gist discovery page and are not indexed by search engines, but anyone who has the direct URL to the secret gist can view it. The gist is hidden from public discovery but accessible via the URL.
Why the other options are wrong
- A. Secret gists do not require explicit access assignment; anyone with the URL can view them.
- C. Secret gists do not require GitHub Enterprise; they are available to all GitHub users.
- D. Secret gists are specifically hidden from the gist Discover page, which is why they are considered secret.
Question 13
Which of the following statements most accurately describes who can access a private repository Wiki?
Show answer and explanation
Correct answer: D. Wikis can be viewed by the same people who have Read access to the repository.
In a private GitHub repository, the Wiki is accessible to any user who has Read access to the repository. Access permissions to the Wiki follow the same access control as the repository itself, meaning Read access grants Wiki viewing rights.
Why the other options are wrong
- A. Wikis are not restricted to repository admins alone; anyone with Read access can view them.
- B. Private repository Wikis are not public; they respect the repository's privacy settings.
- C. Wikis do not require explicit sharing with individual users beyond the standard repository access permissions.
Question 14
What should you append to the link https://github.com/github/docs/ to show who starred that repository?
Show answer and explanation
Correct answer: B. stargazers
To view who starred a GitHub repository, you append '/stargazers' to the repository URL. This is the standard GitHub path for displaying the list of users who have starred a repository.
Why the other options are wrong
- A. The path 'stars' is not the correct GitHub endpoint for viewing stargazers.
- C. The path 'starwatcher' is not a valid GitHub URL path for this purpose.
- D. The path 'starviewers' is not the correct GitHub endpoint for viewing who starred a repository.
Question 15
As a repository admin, which alerts can you see from the security tab of a repository? (Choose three.)
Show answer and explanation
Correct answer: C, D, E. Secret Scanning; Code Scanning; Dependabot
The security tab in a GitHub repository displays three primary alert types: Secret Scanning detects exposed credentials, Code Scanning identifies code vulnerabilities, and Dependabot alerts notify of vulnerable dependencies. These are the core security monitoring features available to repository administrators.
Why the other options are wrong
- A. Branch Protection settings are found in repository settings, not in the security tab's alerts.
- B. Push Protection Bypass alerts are not a standard alert type displayed in the security tab.
Question 16
How can a user choose to receive ongoing updates about a specific activity on GitHub.com?
Show answer and explanation
Correct answer: D. by customizing the types of notifications you will receive in the future
Users can customize the types of notifications they will receive in the future through GitHub's notification settings, allowing granular control over what activities trigger notifications and how they are delivered. Subscribing to all activity in a repository is not a selective approach to notifications. Account tier upgrades do not control notification preferences. Automatically watching repositories with push access is a default behavior, not a choice to receive ongoing updates about specific activities.
Why the other options are wrong
- A. Subscribing to all repository activity is too broad and not a customizable approach to specific activities.
- B. Paid accounts do not provide better notification control than free accounts.
- C. Auto-watching repositories is automatic behavior, not a deliberate choice to customize ongoing updates.
Question 17
What folder is the definition files stored in when creating custom issue forms?
Show answer and explanation
Correct answer: D. .github/ISSUE_TEMPLATE
Custom issue form definition files in GitHub are stored in the .github/ISSUE_TEMPLATE directory. This is the standard location within a GitHub repository where all issue template files are placed, allowing GitHub to recognize and offer these templates when creating new issues.
Why the other options are wrong
- A. The folder structure .issues/ISSUE_TEMPLATE does not exist in GitHub's standard repository structure.
- B. While .github is the correct parent directory, the issue templates must be in the ISSUE_TEMPLATE subfolder.
- C. The .issues folder is not a recognized GitHub directory; GitHub uses .github instead.
Question 18
Which of the following is a key characteristic of GitHub Projects?
Show answer and explanation
Correct answer: B. ability to create and customize multiple views
A key characteristic of GitHub Projects is the ability to create and customize multiple views of your project data, allowing teams to organize and visualize work in ways that suit their workflow, such as table, board, or roadmap views.
Why the other options are wrong
- A. Visualizing commit history is a feature of repository history or Git log, not GitHub Projects.
- C. GitHub Projects cannot import Gantt charts from Microsoft Project; it has its own native visualization capabilities.
- D. While GitHub Projects has field management features, the defining characteristic is the ability to create and customize multiple views.
Question 19
Which of the following best describes GitHub Pages?
Show answer and explanation
Correct answer: A. webpages hosted and published through GitHub repositories
GitHub Pages is a service that enables users to host and publish static websites directly from their GitHub repositories. It allows developers to create project websites, documentation sites, or personal blogs using HTML, CSS, and Jekyll.
Why the other options are wrong
- B. Pagination is an API concept for handling large result sets, unrelated to GitHub Pages.
- C. GitHub Pages is not a documentation guide; it is a hosting service for websites.
- D. While GitHub Pages can host documentation, it is broader than just long-form documentation hosting.
Question 20
Where can you go to discover, browse, and install tools?
Show answer and explanation
Correct answer: A. GitHub Marketplace
GitHub Marketplace is the central location where users can discover, browse, and install GitHub Apps, Actions, and other tools that extend GitHub's functionality and integrate with workflows.
Why the other options are wrong
- B. Explore is used to discover repositories and code, not tools and apps.
- C. GitHub Apps is where you manage already-installed apps, not the primary discovery location.
- D. Organization settings is for managing organizational configuration, not discovering and installing tools.
Question 21
While maintaining the gist history, which of the following is the most efficient way to create a public gist based on another user’s gist?
Show answer and explanation
Correct answer: B. Fork the gist.
Forking a gist is the most efficient way to create a public gist based on another user's gist while maintaining the history and relationship to the original. Forking preserves the commit history and creates a connected copy that acknowledges the source.
Why the other options are wrong
- A. Requesting to be added to the existing gist does not create a new public gist; it only grants editing access to the original.
- C. Creating a new gist and copying content loses the gist history and does not maintain the relationship to the original.
- D. Cloning a gist is a local operation that creates a copy on your computer; it does not create a new public gist on GitHub.
Question 22
What is the primary goal of GitHub in terms of integrating tools and providing an ecosystem?
Show answer and explanation
Correct answer: A. to bring developers’ preferred tools together in one place
GitHub's primary goal in integrating tools is to bring developers' preferred tools together in one place, creating a unified platform where developers can use familiar and best-in-class tools without friction. This integration-focused approach allows developers to choose their favorite tools while maintaining seamless workflows within GitHub. Option D represents a more restrictive standardization approach that contradicts GitHub's philosophy of flexibility and choice.
Why the other options are wrong
- B. While GitHub does offer diverse tools, the primary goal is integration of external tools rather than offering its own specific set.
- C. GitHub does not focus on developing proprietary tools or enforcing opinionated integrations; it embraces existing tools.
- D. GitHub aims for integration and flexibility, not standardization; it respects developer choice.
Question 23
Which of the following best describes GitHub flow?
Show answer and explanation
Correct answer: C. a lightweight workflow that allows for safe experimentation with new ideas and collaboration on projects through branching, pull requests, and merging
GitHub flow is a lightweight and flexible branching workflow that emphasizes safe experimentation through feature branches, pull requests for collaboration and review, and merging changes back to the main branch. It allows teams to deploy frequently while maintaining code quality.
Why the other options are wrong
- A. GitHub flow is not strict and does not enforce linear development; it allows parallel feature development on branches.
- B. GitHub flow primarily uses a single main branch and feature branches, not multiple primary branches like Git Flow.
- D. This describes a release branching strategy, which is different from the core GitHub flow model.
Question 24
What qualifier finds issues that mention a certain user?
Show answer and explanation
Correct answer: B. mentions:
The 'mentions:' qualifier is used in GitHub's search syntax to find issues that mention a specific user. For example, 'mentions:octocat' would return issues where the user 'octocat' is mentioned. This is the correct syntax for this type of search in GitHub's advanced search functionality.
Why the other options are wrong
- A. The 'threads:' qualifier does not exist for finding user mentions in GitHub search.
- C. The 'mentioned:' qualifier is not the correct syntax; the proper form is 'mentions:'.
- D. The '@mentioned:' format is not a valid GitHub search qualifier.
Question 25
Which of the following describes a branch in Git?
Show answer and explanation
Correct answer: A. a pointer to an identical snapshot of the project at a specific point in time
A branch in Git is a pointer to a specific commit, which represents an identical snapshot of the project at that point in time. Branches allow developers to work on separate lines of development independently. When you create a branch, you're creating a lightweight reference to a commit, not duplicating the entire codebase. The branch can diverge from other branches as new commits are made to it.
Why the other options are wrong
- B. A branch is not a new repository; it is a separate line of development within the same repository.
- C. A branch is not a separate copy of the codebase; it is a pointer and reference structure that shares the underlying repository data.
- D. A branch is not a physical copy stored on disk; it is a logical reference within the Git system.
Question 26
Which of the following attributes are on the Milestone page? (Choose two.)
Show answer and explanation
Correct answer: A, B. a list of the open and closed issues associated with the milestone; each milestone’s completion percentage
The Milestone page displays a list of open and closed issues associated with that milestone, allowing users to track progress. Each milestone also shows a completion percentage, typically displayed as a progress bar showing what fraction of associated issues have been closed. GitHub Actions workflows are not displayed on the Milestone page itself, and Projects are managed separately from milestones rather than being tagged to them.
Why the other options are wrong
- C. GitHub Action workflows are not displayed or executed from the Milestone page.
- D. GitHub Projects are not tagged to milestones; they are separate organizational features.
Question 27
What template types are available when creating an issue template? (Choose three.)
Show answer and explanation
Correct answer: A, C, D. Feature request; Custom template; Bug report
GitHub provides three primary issue template types: Feature request for proposing new functionality, Custom template for user-defined templates, and Bug report for reporting defects. These templates help standardize issue creation and ensure necessary information is captured.
Why the other options are wrong
- B. There is no 'Standard template' option among GitHub's issue template types.
- E. Security notification is not a built-in issue template type in GitHub; security concerns are typically handled through security advisories.
Question 28
Which of the following can be performed within GitHub Desktop?
Show answer and explanation
Correct answer: B. adding and cloning repositories
GitHub Desktop is a desktop application that allows users to add and clone repositories from GitHub to their local machines, making it easy to manage repositories without using command-line Git tools.
Why the other options are wrong
- A. GitHub Desktop does not integrate with office suite software.
- C. Creating and managing issues is performed on github.com, not within GitHub Desktop.
- D. Commenting on discussions requires the web interface, not GitHub Desktop.
- E. While GitHub Desktop handles pull requests locally, it does not perform code review and approval functions.
Question 29
What command should you type to create and switch over to a new branch?
Show answer and explanation
Correct answer: B. git checkout -b newBranchName
The command 'git checkout -b newBranchName' creates a new branch and immediately switches to it in one operation. The '-b' flag is the standard Git option for creating and checking out a new branch simultaneously.
Why the other options are wrong
- A. The '-n' flag is not a valid Git option; it does not create a branch.
- C. This command only switches to an existing branch and will fail if the branch does not already exist.
- D. This command creates a new branch but does not switch to it; an additional checkout command would be required.
Question 30
Which GitHub tools or features is best to quickly modify a batch of files in a repository?
Show answer and explanation
Correct answer: A. Use github.dev from a web browser.
The github.dev web-based editor allows users to quickly browse, edit, and modify multiple files in a repository directly from the browser without installation or setup. It is accessed by pressing the period key or navigating to github.dev, providing the fastest path for rapid batch file modifications.
Why the other options are wrong
- B. The git CLI requires local installation and configuration, making it slower for quick modifications compared to a browser-based editor.
- C. Creating a new Codespace involves setup and initialization time, making it less efficient for quick batch modifications than the immediate github.dev editor.
- D. GitHub Desktop requires installation and is designed for comprehensive version control workflows rather than quick, simple file modifications.
- E. GitHub Mobile is designed for reviewing and managing pull requests and issues on mobile devices, not for efficiently editing batches of repository files.
Question 31
Who can be assigned to an issue or pull request? (Choose two.)
Show answer and explanation
Correct answer: A, D. anyone with write permissions to the repository; anyone who has commented on the issue or pull request
GitHub lets you assign issues and pull requests to yourself, to anyone who has commented on the issue or pull request, to anyone with write permissions to the repository, and to organization members with read permissions. Write permission and having commented are both valid routes to being assigned.
Why the other options are wrong
- B. Having an enterprise account does not by itself make a user assignable to an issue or pull request in a repository.
- C. Having a personal GitHub account alone is not enough; the user needs write access, a comment on the item, or organization membership.
Question 32
How can a user create a repository template, and what permissions are required?
Show answer and explanation
Correct answer: A. With Admin permissions, navigate to Repository settings and select Template Repository.
To create a repository template, a user with Admin permissions must navigate to the repository settings and select the Template Repository option. This allows others to generate new repositories based on the template structure and contents.
Why the other options are wrong
- B. Organization settings is not the location for creating template repositories; it must be done in repository settings.
- C. While Maintain permissions allow significant repository management, only Admin permissions can create template repositories.
- D. Maintain permissions are insufficient; Admin permissions are required to create a template repository.
Question 33
Where should a repository admin navigate to view pre-built visualizations from repository data?
Show answer and explanation
Correct answer: A. Insights
The Insights section of a repository provides pre-built visualizations and analytics about repository data, including traffic, commits, contributors, network graphs, and other metrics that help repository admins understand project activity and trends.
Why the other options are wrong
- B. Issues is where tracked tasks and bug reports are managed, not where visualizations are viewed.
- C. Settings contains repository configuration options, not data visualizations.
- D. Charts is not a standard GitHub navigation option for viewing repository analytics.
Question 34
Which of the following is always true about the feature preview phases Alpha and Beta?
Show answer and explanation
Correct answer: A. Alpha features are not available to the public.
Alpha features are not available to the public and are restricted to a limited set of testers or organizations. This is the defining characteristic of the Alpha phase in GitHub's feature preview lifecycle.
Why the other options are wrong
- B. Beta features do not guarantee technical support; they are still in preview and support levels may be limited compared to general availability features.
- C. Neither Alpha nor Beta features provide Service Level Agreements (SLAs); these commitments only apply to generally available features.
- D. Alpha features are not always documented; they may have minimal or limited documentation as they are still under development and testing.
Question 35
A distributed version control system is best described as a system that:
Show answer and explanation
Correct answer: A. ensures each developer has their own local copy of the entire code repository, including the complete project history and metadata.
A distributed version control system is characterized by each developer maintaining their own complete local copy of the entire repository, including all project history and metadata. This contrasts with centralized systems where a single server holds the authoritative version. The distributed approach enables developers to work offline, maintain full history locally, and collaborate without requiring constant server access.
Why the other options are wrong
- B. This describes a cloud-based centralized system, not a distributed system.
- C. This describes a centralized version control system with a central server holding the project history.
- D. This describes manual version management without proper version control systems.
Question 36
What is a Git remote?
Show answer and explanation
Correct answer: B. a reference to a repository that is hosted in a separate location
A Git remote is a reference to a repository hosted in a separate location, typically on a server like GitHub. It allows developers to push and pull changes between their local repository and the remote repository. The remote serves as a centralized point for collaboration and backup. The other options describe local copies, branches, or testing repositories rather than the concept of a remote.
Why the other options are wrong
- A. A local copy stored on a user's machine is the local repository, not a remote.
- C. A branch is a separate line of development within a repository, not a remote.
- D. A separate testing repository is not what a Git remote is; a remote is simply a reference to an external repository.
That was 36 of 142.
The full GitHub GH-900 Foundations pack has all 142 questions, each with the answer, the explanation and why the other options are wrong, plus a questions-only copy for timed runs. US$39, paid once, with free monthly updates and a pass-or-your-money-back guarantee.
Not ready yet? Get the first 63 free as one PDF by email. Get the Half Pack →