[Mar 23, 2026] Free GitHub Administrator GH-900 Exam Question [Q42-Q56]

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.

Key Features of GitHub Flow
* Main Branch (main): This branch always contains deployable, production-ready code.
* Feature Branches: Developers create a new branch for each feature or bug fix. Once work on a feature is completed, a pull request (PR) is opened for review and merging into the main branch.
*-> Pull Requests: Once the feature branch is complete, a pull request is created to merge it into the main branch. The PR is reviewed and, once approved, is merged into main.
Reference:
https://www.geeksforgeeks.org/git/git-flow-vs-github-flow/

To locate an existing GitHub Action provided by a GitHub-approved vendor, you can use the following methods:
Verification Badge:
Option C is correct because actions provided by GitHub-approved vendors will typically have a verification badge. This badge indicates that the action is from a trusted source, giving users confidence in its security and reliability.
Search the GitHub Marketplace:
Option F is correct because GitHub Marketplace is the official location to find and install actions, including those provided by third-party vendors. You can search for actions by the vendor’s name to find the specific one you need.
Incorrect Options:
Option A is not necessary to locate an existing action; creating a workflow file is for implementing the action, not locating it.
Option B is incorrect because searching the vendor’s website for a github.yaml index is not a standard practice for finding actions.
Option D is incorrect because installing a GitHub App is unrelated to finding an existing action.
Option E is incorrect because adding a vendor as an allowed Actions Source is a configuration step for using the action, not for locating it.
Reference:
GitHub Marketplace: Verified Actions

GitHub Projects offers different layout options to help teams organize and visualize their work, including Table, Board, and Timeline. The Table view presents structured data like a spreadsheet, the Board layout uses a Kanban-style interface for task management, and the Timeline layout helps track progress over time.
Option A is CORRECT because GitHub Projects supports three main layout options:
Table (a high-density spreadsheet-style layout)
Board (a Kanban-style task board)
Timeline (a roadmap-style view useful for planning over time)
References:
https://docs.github.com/en/issues/planning-and-tracking-with-projects/customizing-views-in-your- project/changing-the-layout-of-a-view
https://github.blog/developer-skills/github/getting-started-with-project-planning-on-github/

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.
Reference:
GitHub Docs: GitHub Flow

The primary purpose of creating a security policy in a GitHub repository is to guide users and contributors on how to report security vulnerabilities in a responsible and secure manner. This policy outlines the preferred method of communication, timelines, and any other pertinent information related to handling security issues.
Security Policy:
Option C is correct because a security policy provides guidelines for responsibly disclosing security vulnerabilities. This helps maintainers respond to and address security concerns promptly and securely, thereby protecting the project and its users.

GitHub is a cloud-based platform that provides hosting for software development and version control using Git. It offers tools for collaboration, project management, and security to create a safe and productive environment for developers.
GitHub Overview:
Option B is correct because GitHub is primarily known as a cloud-based hosting service for Git repositories, offering a collaborative environment where developers can work together on projects, manage version control, and implement security practices.
Incorrect Options:
Option A is incorrect because GitHub is not proprietary in the sense of being closed off from version control standards; it is widely recognized as an open platform for collaboration.
Option C is incorrect because, while GitHub is accessible to new developers, it is designed for developers of all skill levels and not specifically tailored for beginners.
Option D is incorrect because GitHub is not a centralized version control system; it supports Git, which is distributed.
Reference:
GitHub Docs: About GitHub

Git is a widely-used version control system that has several defining features:
Distributed Version Control:
Git is a distributed version control system, meaning that every developer has a full copy of the entire repository, including its history, on their local machine. This enables greater flexibility, as work can be done offline and each user has access to the full project history.
Open Source Software:
Git is open-source, meaning its source code is freely available for use, modification, and distribution. This fosters a large community of users and contributors who continuously improve the software.
Efficiency with Large Projects:
Git is designed to handle projects of any size with speed and efficiency. It can manage large codebases and many contributors without significant performance degradation, making it suitable for everything from small personal projects to large, complex software systems.

In GitHub, labels are used to categorize issues and pull requests, and certain default labels are provided to help manage tasks:
Help Wanted Label:
Option C is correct. The “Help wanted” label is used to indicate that the maintainer of the repository needs assistance on a particular issue or pull request. This label helps in attracting contributors who might be interested in helping with specific tasks.

Commits and pull requests (PRs) are fundamental concepts in Git and GitHub workflows, particularly in collaborative software development.
Commits:
Commits are individual changes or updates made to the codebase. Each commit is identified by a unique SHA-1 hash and typically includes a commit message describing the changes.
Commits are made to a specific branch in the repository. The branch could be the main branch, or more commonly, a feature branch created for specific work or a feature.
Pull Requests (PRs):
A pull request is a mechanism for developers to notify team members that a branch is ready to be merged into another branch, usually the main branch.
PRs are used to review code, discuss changes, and make improvements before the branch is merged into the target branch.
Relationship Between Commits and PRs:
Option A is correct because commits are made on a branch, and this branch can have a pull request associated with it. The pull request tracks the branch’s commits and allows for code review before merging into the target branch.
Commits can be added to the branch both before and after the pull request is created. Any new commits pushed to the branch are automatically included in the pull request.

Viewing who has starred a repository
You can view everyone who has starred a public repository or a private repository you have access to.
To view everyone who has starred a repository, add /stargazers to the end of the URL of a repository. For example, to view stargazers for the github/docs repository, visit
https://github.com/github/docs/stargazers.
Reference:
https://docs.github.com/en/get-started/exploring-projects-on-github/saving-repositories-with-stars

The following two-factor authentication (2FA) methods can be used to secure a GitHub account:
A . Authenticator app: You can use an authenticator app (like Google Authenticator or Authy) to generate time-based one-time passwords (TOTP) for logging in.
C . GitHub mobile: The GitHub mobile app can also be used to receive 2FA codes, adding convenience for users who prefer to manage everything from their mobile devices.
D . Security keys: Physical security keys (such as YubiKeys) can be used as a strong form of 2FA, requiring physical access to the key to authenticate.
Security questions and Single sign-on (SSO) are not considered 2FA methods in the context of GitHub account security.

After 30 minutes of inactivity, a GitHub Codespace will time out. This is designed to conserve resources when the Codespace is not being actively used. The session will be paused, and you’ll need to reconnect to resume your work. However, the Codespace is not deleted, and any unsaved changes might not be lost but should be committed or saved to prevent data loss.

Commits and pull requests (PRs) are fundamental concepts in Git and GitHub workflows, particularly in collaborative software development.
Commits:
Commits are individual changes or updates made to the codebase. Each commit is identified by a unique SHA-1 hash and typically includes a commit message describing the changes.
Commits are made to a specific branch in the repository. The branch could be the main branch, or more commonly, a feature branch created for specific work or a feature.
Pull Requests (PRs):
A pull request is a mechanism for developers to notify team members that a branch is ready to be merged into another branch, usually the main branch.
PRs are used to review code, discuss changes, and make improvements before the branch is merged into the target branch.
Relationship Between Commits and PRs:
Option A is correct because commits are made on a branch, and this branch can have a pull request associated with it. The pull request tracks the branch’s commits and allows for code review before merging into the target branch.
Commits can be added to the branch both before and after the pull request is created. Any new commits pushed to the branch are automatically included in the pull request.
Incorrect Options:
Option B is incorrect because commits can be made both before and after a pull request is created.
Option C is incorrect because it suggests that commits can only be made before a pull request is created, which is not true.
Option D is incorrect because commits are not made on a pull request; they are made on a branch. The pull request links a branch to another branch (e.g., feature branch to the main branch).
Reference:
GitHub Documentation: About Pull Requests
GitHub Docs: Understanding the GitHub Flow
Git Documentation: Git Basics – Getting a Git Repository