Questions for the GH-900 were updated on : Nov 24 ,2025
What features are offered by Copilot for Business that are not offered by Copilot for individuals?
(Each answer presents a complete solution. Choose three.)
B, C, E
Explanation:
GitHub Copilot for Business offers several features that are tailored to the needs of organizations,
providing more control, security, and support compared to the individual version.
Organization-wide Policy Management:
Option B is correct because Copilot for Business allows organizations to manage policies across their
entire user base, providing control over how Copilot is used within the organization.
Blocking Suggestions Matching Public Code:
Option C is correct because Copilot for Business includes enhanced security features, such as
blocking code suggestions that match public code to prevent inadvertent use of unlicensed code.
Support for Organization or Enterprise GitHub Accounts:
Option E is correct because Copilot for Business supports integration with GitHub Enterprise
accounts, offering additional administrative controls and integration capabilities.
Incorrect Options:
Option A (multi-line function suggestions) is a feature available in both individual and business
versions, so it does not differentiate the business offering.
Option D (VPN proxy support via self-signed certificates) is not a primary differentiator of Copilot for
Business.
Option F (plugs directly into the editor) is true for both individual and business versions, so it is not
unique to Copilot for Business.
Reference:
GitHub Docs: GitHub Copilot for Business
The difference between GitHub Desktop and github.com is that Desktop:
D
Explanation:
GitHub Desktop is a standalone application that provides a graphical user interface (GUI) for
interacting with GitHub repositories, as opposed to the command-line or web-based interfaces
available on github.com.
Graphical User Interface:
Option D is correct because GitHub Desktop offers a GUI, making it easier for users to manage
repositories, perform commits, and handle other Git-related tasks without needing to use the
command line.
Incorrect Options:
Option A is partially correct in that GitHub Desktop is a standalone application, but the key difference
is the GUI.
Option B is incorrect because GitHub Desktop does not specifically enable integration with office
suite applications.
Option C is incorrect because GitHub Desktop is available on both Windows and macOS.
Option E is incorrect because GitHub Desktop is not a self-hosted version of GitHub; it is a client
application for accessing GitHub repositories.
Reference:
GitHub Docs: GitHub Desktop Documentation
If there are multiple README files, which of the following locations will be displayed first?
C
Explanation:
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.
Reference:
GitHub Docs: About READMEs
What are primary benefits of using GitHub issues templates?
(Each answer presents a complete solution. Choose two.)
A, B
Explanation:
The primary benefits of using GitHub issues templates include:
A . To automatically label or assign newly created issues: Issue templates can be configured to
automatically apply labels or assign users when the issue is created, helping to streamline triage and
management processes.
B . To provide an easy-to-fill-out form for creating new issues: Templates provide a standardized
format for submitting issues, ensuring that all necessary information is captured and reducing the
need for follow-up questions.
Coercing existing issues into a standard format or automatically creating new branches when issues
are created are not functions provided by GitHub issues templates.
Which of the following steps are part of the Codespaces lifecycle?
(Each answer presents a complete solution. Choose three.)
C, E, F
Explanation:
The Codespaces lifecycle on GitHub includes several key steps:
Create: This is the step where a new Codespace is initiated.
Rebuild: A Codespace can be rebuilt to ensure that the environment is up-to-date with the latest
code or configurations.
Delete: Once a Codespace is no longer needed, it can be deleted to free up resources.
Committing, cloning, or installing are typical Git operations but are not considered part of the
specific lifecycle steps for a GitHub Codespace.
From the list of projects for an organization, how can a user identify a GitHub Projects template?
C
Explanation:
In GitHub, when viewing the list of projects for an organization, a user can identify a GitHub Projects
template by selecting the Templates tab. This tab specifically lists available templates that can be
used to create new projects based on predefined structures and workflows.
Which of the following options can a user do from a discussion post?
C
Explanation:
From a discussion post on GitHub, a user can Create an issue from the discussion. This feature allows
users to turn a discussion into an actionable item by creating an issue directly from the discussion
thread. This is particularly useful when a conversation identifies a bug, task, or enhancement that
needs to be tracked in the repository.
Workflows can reference actions in:
(Each correct answer presents a complete solution. Choose three.)
A, B, E
Explanation:
As mentioned in the answer to Question no. 66, GitHub Actions workflows can reference actions
from a variety of sources:
Any Public Repository:
Option A is correct. Actions can be sourced from any public GitHub repository.
The Same Repository as Your Workflow File:
Option B is correct. Actions within the same repository as the workflow file can be referenced
directly.
A Published Docker Container Image on Docker Hub:
Option E is correct. Workflows can also use actions provided as Docker container images from Docker
Hub.
Incorrect Options:
Option C and D are not relevant for directly referencing actions in workflows.
Reference:
GitHub Docs: Reusing Workflows
What is the primary purpose of creating a new branch in the GitHub flow?
C
Explanation:
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
Workflows can reference actions in:
(Each correct answer presents a complete solution. Choose three.)
A, B, E
Explanation:
In GitHub Actions workflows, actions can be referenced from various sources depending on the
needs of the workflow.
Any Public Repository:
Option A is correct. Actions can be referenced from any public GitHub repository, allowing the reuse
of shared actions across multiple projects.
The Same Repository as Your Workflow File:
Option B is correct. Actions stored in the same repository as the workflow file can be referenced
directly, which is common for custom actions specific to that project.
A Published Docker Container Image on Docker Hub:
Option E is correct. Workflows can reference actions that are provided as Docker container images
hosted on Docker Hub, allowing integration of complex tools and environments.
Incorrect Options:
Option C (GitHub Packages) is incorrect as it is more commonly used for storing and managing
dependencies, not actions.
Option D (An enterprise marketplace) is incorrect because GitHub Actions are not directly referenced
from an enterprise marketplace but rather from public repositories or Docker images.
Reference:
GitHub Docs: Reusing Workflows
Which of the following are available statuses of a pull request?
(Each answer presents a complete solution. Choose four.)
A, B, D, F
Explanation:
Pull requests (PRs) on GitHub can have several statuses that indicate their current state in the
development and review process:
Draft:
Option A is correct. A pull request can be in a "Draft" status, indicating that it is a work in progress
and not yet ready for review.
Closed:
Option B is correct. A pull request can be "Closed" without being merged, which might happen if the
proposed changes are not needed or are incorporated differently.
Merged:
Option D is correct. A pull request that has been reviewed and approved can be "Merged" into the
target branch, indicating that the changes have been successfully incorporated.
Open:
Option F is correct. An "Open" pull request is one that is active and awaiting review or further action.
Incorrect Options:
Option C (Rebasing) is incorrect because "Rebasing" is not a status; it's an operation that can be
performed on branches.
Option E (Modified) is incorrect because there is no "Modified" status for pull requests.
Reference:
GitHub Docs: About Pull Requests
Which of the following two-factor authentication (2FA) methods can you use to secure a GitHub
account?
(Each answer presents a complete solution. Choose three.)
A, C, D
Explanation:
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.
As a GitHub user, where in the UI can you configure two-factor authentication (2FA) to further secure
your account?
D
Explanation:
As a GitHub user, you can configure two-factor authentication (2FA) to secure your account by
navigating to Settings -> Password and Authentication -> 2FA. This section in the GitHub user
interface allows you to set up and manage your 2FA methods, which provide an additional layer of
security beyond just your password.
How can a user highlight a post to the top of the Discussions page?
B
Explanation:
To highlight a post at the top of the Discussions page on GitHub, you can Pin the discussion. Pinning a
discussion ensures it remains prominently visible at the top of the list, making it easier for others to
find and participate in that discussion. This is particularly useful for important announcements or
frequently referenced topics.
Which of the following is a primary goal of GitHub's community?
C
Explanation:
GitHub's community is centered around enabling developers to collaborate and innovate together.
The platform provides tools and environments that foster open communication, sharing of ideas, and
collective problem-solving.
Facilitating Collaboration and Creativity:
Option C is correct because GitHub is designed to be a collaborative platform where developers can
work together on projects, share code, and contribute to open source initiatives, all in an
environment that encourages creativity.
Incorrect Options:
Option A is incorrect because GitHub is inclusive of developers of all skill levels, not just experienced
ones.
Option B is incorrect because GitHub is not about creating a competitive environment; rather, it
focuses on collaboration.
Option D is incorrect because while code quality is important, enforcing strict code quality standards
is not the primary goal of the GitHub community.
Reference:
GitHub Docs: Building a Strong Community