GH-900 Microsoft GitHub Foundations Free Practice Exam Questions (2026 Updated)

Saved replies in GitHub are a feature that allows users to create and save templates of commonly used responses for issues and pull requests. This feature can significantly enhance productivity and ensure consistent communication.

Saved Replies Are Tied to a User ' s Personal Account:

Option A is correct because saved replies are specific to a user ' s GitHub account, meaning they are accessible to the user across all repositories they have access to.

Saved Replies Allow Reusable Responses:

Option C is correct because the primary purpose of saved replies is to allow users to create reusable responses for issues and pull requests, saving time and ensuring consistency.

Incorrect Options:

Option B is incorrect because saved replies are not allocated at the enterprise level; they are specific to individual user accounts.

Option D is incorrect because saved replies do not send auto notifications; they are manually inserted by the user when responding to issues or pull requests.

The GitHub Command Palette provides quick keyboard-based access to navigation, commands, repositories, issues, pull requests, projects, and other GitHub areas. On GitHub.com, Windows and Linux users can open the Command Palette by pressing Ctrl+K. This shortcut helps users move faster through GitHub without relying only on menus or page navigation. Ctrl+S is commonly associated with saving in many applications, not opening the GitHub Command Palette. Shift+Enter is generally used for line breaks or text-entry behavior in many interfaces. Alt+P is not the standard GitHub.com shortcut for this feature. Knowing Command Palette shortcuts is useful for the GitHub Foundations exam because it tests productivity features available directly in the GitHub web interface.

In GitHub Flow, creating a new branch is a key step in the development process that allows for isolated development of new features or fixes without affecting the main codebase.

Experimenting with New Features or Fixes:

Option C is correct. The primary purpose of creating a new branch in the GitHub flow is to provide a safe space to experiment with new features or fixes. This allows developers to work on changes independently and only merge them into the main branch after they have been reviewed and approved.

Incorrect Options:

Option A (To create a backup of the main branch) is incorrect because branches are not typically used for backups; they are for active development.

Option B (To capture information about an issue) is incorrect because issues are tracked separately; branches are for code changes.

Option D (To incorporate changes from a review) is incorrect because incorporating changes is done during the pull request process, not when creating a branch.

GitHub Copilot is described as an AI pair programmer that offers autocomplete-style suggestions. It is a tool integrated into development environments like Visual Studio Code that helps developers by providing code suggestions as they type. Copilot can suggest entire lines or blocks of code based on the context of what you’re writing, making it a valuable assistant in coding, but not a replacement for developers.

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

A GitHub repository serves as a collaborative space where developers can share and manage code files, track changes, and store revision history. It is much more than just a folder or simple tool; it is a comprehensive version control system that allows teams to collaborate effectively on codebases. Repositories enable developers to work together, manage contributions, review code, and maintain a complete history of every change made to the project.

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

GitHub Projects supports various layouts to help teams organize and visualize their work. The available layouts include:

B. Kanban: This is a visual task management tool where tasks are represented as cards and moved across columns that represent different stages of work.

C. Board: This layout is similar to Kanban but can be more flexible, allowing users to set up boards in various ways to suit their workflow needs.

D. Table: The Table layout allows you to view your tasks in a spreadsheet-like format, making it easy to manage and edit large amounts of data at once.

Roadmap and Backlog are not standard layouts provided by GitHub Projects. While these terms might be relevant in other project management contexts, GitHub Projects specifically offers Kanban, Board, and Table layouts.

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

GitHub Actions are automated workflows that can be triggered by various events on GitHub. Some common events that trigger workflows include pushes to a repository, creation of issues, and comments on discussion posts.

Triggering GitHub Actions:

Option D (Pushing to a GitHub repository) is correct because this is one of the most common triggers for CI/CD workflows.

Option F (Creating an Issue) is correct because issues are commonly used as triggers for workflows, such as automatically assigning a label or notifying a team.

Option A (Adding a comment to a discussion post) is correct because actions can be triggered by activity on discussion posts, including comments.

Incorrect Options:

Option B (Creating a new repository) is incorrect because this action typically does not trigger workflows within a specific repository.

Option C (Committing a change to a local git repository) is incorrect because GitHub Actions are triggered by events on the GitHub platform, not by local commits.

Option E (Disabling a GitHub runner) is incorrect because it is related to the environment where actions are executed, not a trigger for workflows.

For private repositories on GitHub, the Wiki is accessible to anyone who has Read access to the repository. This means that if you can view the code and files in the repository, you can also view its Wiki. This makes Wikis a useful tool for documenting projects in a way that is available to all collaborators without requiring special permissions beyond those needed to access the repository itself.

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

GitHub provides several pre-defined repository roles that determine the level of access and permissions a user has within a repository. The roles that are included by default are:

Triage : Allows users to manage issues and pull requests without write access to the code.

Maintain : Provides more extensive access, including managing settings, but without full administrative control.

Write : Grants permission to push changes and manage issues and pull requests.

Roles like " Security " and " Delete " are not standard pre-defined roles, and " View " is generally referred to as " Read " in GitHub ' s permission structure.

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

GitHub Teams, as part of GitHub’s paid plans, offers additional features and capabilities compared to GitHub Free, particularly for organizations.

GitHub Teams Benefits:

Option B is correct because GitHub Teams provides advanced security features like SAML single sign-on for secure authentication, as well as increased minutes for run ning GitHub Actions, which are essential for continuous integration and deployment workflows.

Incorrect Options:

Option A is incorrect because private repositories and advanced tools are features available, but the key differentiator in this context is the SAML SSO and additional GitHub Actions minutes.

Option C is incorrect because while expanded storage and priority support are valuable, SAML SSO and increased GitHub Actions minutes are more central to the differences between GitHub Free and GitHub Teams.

Option D is partially correct, but since the question asks for the best reason, Option B provides the most critical features that differentiate GitHub Teams from GitHub Free.

InnerSource applies open source collaboration practices inside an organization while keeping the work internal. Its primary goal is to make company projects more visible to employees and reduce friction when teams contribute across boundaries. Instead of every team working in isolation, InnerSource encourages shared ownership, discoverable repositories, clear contribution guidelines, issues, pull requests, and code reviews. This helps employees reuse existing solutions, avoid duplicated work, and collaborate more efficiently. Unlike open source, InnerSource does not require making repositories public or accepting outside contributors. It also does not remove the need for pull requests; pull requests are often central to the contribution process. The key difference is that InnerSource focuses on internal collaboration using open source-style practices.