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

In a Git repository, a file can be in one of the following three valid states:

Committed : The file is saved in the local repository. It is part of the permanent history of the project.

Modified : The file has been changed but not yet staged or committed. It is in the working directory.

Staged : The file has been marked to be included in the next commit. It is in the staging area, ready to be committed.

These states represent the typical lifecycle of a file as it moves through the process of being edited, reviewed, and saved in Git.

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

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.

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

Creating a repository template in GitHub requires specific steps and permissions:

Creating a Repository Template:

Option A is correct because a user with Admin permissions can navigate to the repository ' s settings and enable the " Template Repository " option. This allows other users to generate new repositories from this template, which includes all branches, tags, and file history.

Other Options:

Option B is incorrect because " Maintain " permissions do not allow the creation of repository templates, and the option is not found in Organization settings but in the repository settings.

Option C is incorrect because the " Template Repository " option is in the repository settings, not in Organization settings.

Option D is incorrect because " Maintain " permissions do not grant the ability to create a repository template.

Innersource is a development practice where an organization adopts open-source development methodologies within its own internal environment. The primary goal of innersource is to break down silos and encourage collaboration across different teams within the organization.

Sharing Code Between Teams:

Option B is correct because innersource involves sharing code between teams within the organization, similar to how open-source communities share code across the public domain. This practice fosters collaboration, improves code quality, and allows for reuse of code, reducing duplication of efforts.

Incorrect Options:

Option A is incorrect because adopting open-source code into the organization is related to using open-source software, not specifically to innersource practices.

Option C is incorrect because removing open-source code from the organization is contrary to the principles of both open source and innersource.

Option D is incorrect because making all repositories publicly accessible refers to open source, not innersource. Innersource typically involves keeping code internal to the organization.

The " Pinned Repositories " section of a GitHub user profile displays repositories that were personally selected to be highlighted by the user. Users can choose which repositories they want to feature prominently on their profile, regardless of recent activity, star count, or organizational ownership.

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

A distributed version control system (DVCS) like Git is best described as a system that ensures each developer has their own local copy of the entire code repository, including the complete project history and metadata . This decentralized approach allows developers to work independently, with full access to the project ' s history and files, and later synchronize their changes with others. Unlike centralized systems, DVCS does not rely on a single central server, which provides greater flexibility and robustness in collaboration.

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

GitHub supports various syntax formats that align with Markdown and HTML conventions. Here ' s a breakdown of the provided options:

Comment Syntax:

Option C is correct. The syntax < !-- This is a comment -- > is used in Markdown files to insert comments. These comments will not be rendered in the final output, making them useful for adding notes or instructions within the code or documentation.

Incorrect Options:

Option A ( * This is a heading ) is incorrect because an asterisk ( * ) denotes an unordered list item, not a heading. A heading in Markdown is typically created with one or more hash symbols ( # ).

Option B ( This is a link ) is incorrect because this is plain text and not the syntax for creating a link. The correct syntax would be [This is a link](URL) .

Option D ( This is bolded text ) is incorrect because this is plain text, not the correct Markdown syntax for bold text, which should be **This is bolded text** or __This is bolded text__ .

Option E ( 1. This is an ordered list ) is incorrect as it does represent an ordered list item, but it was not the syntax format asked about in the question. The question specifically focuses on matching associated text with syntax, where only the comment option is correct.

In GitHub, an organization member is a user who has been added to an organization and is subject to the organization ' s base permissions and policies. An outside collaborator is a user who is not a member of the organization but has been granted access to one or more repositories within the organization.

Here’s the difference between an organization member and an outside collaborator:

Organization Members :

Members are subject to the organization ' s base permissions, which apply across all repositories within the organization. These permissions might include read, write, or admin access, depending on what has been set as the default.

Members consume paid licenses if the organization is on a paid plan.

Members are required to have two-factor authentication (2FA) if the organization enforces it.

Outside Collaborators :

Outside collaborators do not have organization-wide permissions. They only have access to specific repositories to which they have been granted permission. This means organization base permissions do not apply to them (making option A correct).

Outside collaborators do not consume paid licenses. They are only counted toward the license if they are made organization members.

Outside collaborators can be granted any level of permission, including the admin role on specific repositories.

Two-factor authentication (2FA) can be enforced for outside collaborators at the repository level, depending on the organization ' s security settings.

Given this information, option A is the correct answer: " Organization base permissions do not apply to outside collaborators. "

The feature you can use to merge proposed changes in a repository on GitHub is Pull requests . Pull requests are a core feature of GitHub, allowing developers to propose changes to a codebase, review code, discuss the changes, and eventually merge them into the main branch. This collaborative workflow ensures that code is reviewed and vetted before becoming part of the project.

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

When multiple README files exist in different locations within a GitHub repository, the README.md file located in the root directory of the repository will be displayed first by default. This file serves as the main documentation for the repository and is automatically rendered on the repository ' s home page.

Root Directory:

Option C is correct because the README.md file in the root directory is prioritized and displayed first on GitHub. This is the standard behavior for how GitHub presents documentation.

Incorrect Options:

Option A ( .github ) is incorrect because while a README.md file in the .github directory might be used for certain configurations, it is not the first to be displayed.

Option B ( /src ) is incorrect because the README.md in the src directory is not prioritized over the root.

Option D ( /docs ) is incorrect because documentation in the /docs folder is typically secondary to the root README.md .