[UPDATED Feb-2026] Best Value Available Preparation Guide for GH-900 Exam
1 Full GH-900 Practice Test and 77 Unique Questions, Get it Now!
Microsoft GH-900 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
NEW QUESTION # 21
Which of the following best describes a Codespace?
- A. An AI pair programmer that offers autocomplete-style suggestions
- B. A Visual Studio Code plug-in to manage local devcontainers
- C. A lightweight editing experience that runs entirely in your browser
- D. A development environment hosted in the cloud
Answer: D
Explanation:
A Codespace is a cloud-hosted development environment provided by GitHub. It allows developers to code in a fully-configured environment that can be accessed from any device with an internet connection. Codespaces integrate with Visual Studio Code, either through the desktop app or directly in the browser, providing a consistent development experience without the need to manually set up a local environment.
Cloud-Hosted Development Environment:
Option C is correct because GitHub Codespaces are essentially cloud-based environments that are pre-configured with the tools and dependencies needed for development. This allows developers to start coding immediately without the overhead of setting up a local environment.
Incorrect Options:
Option A is partially correct in that Codespaces can be accessed and used in a browser, but the defining feature is that it's a full development environment, not just a lightweight editor.
Option B is incorrect because this describes GitHub Copilot, not Codespaces.
Option D is incorrect because Codespaces is not a Visual Studio Code plug-in; it is a cloud-based service that integrates with Visual Studio Code.
Reference:
GitHub Docs: About GitHub Codespaces
NEW QUESTION # 22
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?
- A. Request to be added to the existing gist.
- B. Clone the gist.
- C. Fork the gist.
- D. Create a new gist and copy the content from the existing gist.
Answer: C
Explanation:
Forking a gist is the most efficient way to create a public gist based on another user's gist while maintaining the history of the original gist. When you fork a gist, you create a new gist in your own account that retains a link to the original, allowing you to track changes and contribute back if desired.
Forking a Gist:
Option A is correct because forking is a straightforward way to create your own copy of another user's gist while preserving the history and making it easy to track updates.
Incorrect Options:
Option B is incorrect because creating a new gist and copying the content would not preserve the history or link back to the original gist.
Option C is incorrect because cloning is typically associated with repositories, not gists, and is more complex than forking for this purpose.
Option D is incorrect because requesting to be added to the existing gist is not a standard GitHub feature.
Reference:
GitHub Docs: Forking Gists
NEW QUESTION # 23
What best describes Markdown?
- A. Scripting language
- B. Programming language
- C. Markup language
- D. Version control system
- E. Containerization solution
Answer: C
Explanation:
Markdown is a lightweight markup language with plain-text formatting syntax. It is designed to be easy to write and read in its raw form, and it can be converted into HTML and other formats. Markdown is commonly used for formatting readme files, writing messages in online discussion forums, and creating rich text documents.
Markup Language:
Option A is correct because Markdown is indeed a markup language. It is not a programming language, scripting language, version control system, or containerization solution.
Incorrect Options:
Option B is incorrect because Markdown is not a programming language; it does not involve control structures or variables.
Option C is incorrect because Markdown is not used for scripting or automation.
Option D is incorrect because Markdown does not manage version control.
Option E is incorrect because Markdown is not related to containerization technologies like Docker.
Reference:
GitHub Docs: Basic writing and formatting syntax
NEW QUESTION # 24
As a user, which of the following default labels is used to indicate that a maintainer needs assistance on an issue or pull request?
- A. Question
- B. Help wanted
- C. Enhancement
- D. Documentation
Answer: B
Explanation:
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.
Other Options:
Option A ("Enhancement") is incorrect because it indicates a request for a new feature or improvement rather than a call for help.
Option B ("Question") is incorrect because it is used to flag issues or pull requests that seek clarification or additional information, not necessarily requiring assistance.
Option D ("Documentation") is incorrect because it labels issues or PRs related to documentation, not for seeking help.
Reference:
GitHub Docs: Using Labels
NEW QUESTION # 25
What are two recommended ways of improving the discoverability of a repository?
(Each answer presents a complete solution. Choose two.)
- A. Register the repository with GitHub search.
- B. Add labels to categorize the repository.
- C. Create a README file describing the repository.
- D. Add topics to classify the repository.
Answer: C,D
Explanation:
Two recommended ways to improve the discoverability of a repository on GitHub are:
B . Create a README file describing the repository: A well-written README file provides essential information about the project, such as what it does, how to use it, and how to contribute. This is often the first thing potential users or contributors will see, making it critical for discoverability.
D . Add topics to classify the repository: Adding topics to your repository helps classify it under specific categories, making it easier for others to find it through GitHub's search and exploration features. Topics act like tags, helping to connect your project with users interested in similar subjects.
Registering a repository with GitHub search and adding labels are not applicable actions for improving discoverability in the broader sense.
NEW QUESTION # 26
Which of the following is the best GitHub feature for long-form documentation for a project?
- A. Pull Requests
- B. Insights
- C. Projects
- D. Wikis
Answer: D
Explanation:
GitHub offers a variety of features for different aspects of project management and documentation. For long-form documentation, the best feature is Wikis. Wikis in GitHub allow you to create detailed, structured documentation that is easy to navigate and edit. Each repository in GitHub can have its own Wiki, which acts as a space for collaborators to maintain project documentation, guides, manuals, or any other long-form content.
Wikis are specifically designed to host extensive documentation in a way that is easy to reference and edit over time. They support Markdown, allowing you to format your documentation effectively. Unlike the other options, Wikis are explicitly intended for the purpose of long-form content, making them the best choice for this use case.
NEW QUESTION # 27
Which of the following GitHub syntax formats is consistent with the associated text?
- A. * This is a heading
- B. <!-- This is a comment -->
- C. 1. This is an ordered list
- D. This is bolded text
- E. This is a link
Answer: B
Explanation:
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.
Reference:
GitHub Flavored Markdown (GFM)
GitHub Docs: Basic writing and formatting syntax
NEW QUESTION # 28
What is the difference between an organization member and an outside collaborator?
- A. Organization base permissions do not apply to outside collaborators.
- B. Outside collaborators cannot be given the admin role on a repository.
- C. Outside collaborators do not consume paid licenses.
- D. Two-factor authentication (2FA) is not required for outside collaborators.
Answer: A
Explanation:
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." Reference:
GitHub Documentation: Roles in an organization
GitHub Documentation: About outside collaborators
GitHub Documentation: Managing repository access for your organization
NEW QUESTION # 29
What should be done to locate an existing action that was provided by a GitHub-approved vendor?
(Each correct answer presents part of the solution. Choose two.)
- A. Add the vendor as an allowed Actions Source.
- B. Confirm that the action has a verification badge.
- C. Create a new workflow file.
- D. Search the GitHub Marketplace for Actions by the vendor.
- E. Search the vendor's website for a github.yaml index.
- F. Install the GitHub App that was provided by the vendor.
Answer: B,D
Explanation:
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
NEW QUESTION # 30
Which of the following are displayed in the "Pinned Repositories" section of a GitHub user profile?
- A. Repositories that were personally selected to be highlighted
- B. Repositories with the highest number of stars
- C. Repositories that are owned by organizations in which the user is a member
- D. Repositories with the most recent activity
Answer: A
Explanation:
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.
NEW QUESTION # 31
What folder is the definition files stored in when creating custom issue forms?
- A. .github/ISSUE_TEMPLATE
- B. .issues
- C. .issues/ISSUE_TEMPLATE
- D. .GitHub
Answer: A
Explanation:
When creating custom issue forms on GitHub, the definition files are stored in the .github/ISSUE_TEMPLATE folder. This directory is used to define issue templates and forms that help standardize the information collected when users open new issues in the repository. The .github folder is a special directory used for various repository configurations and workflows.
NEW QUESTION # 32
Where can you go to discover, browse, and install tools?
- A. Explore
- B. GitHub Apps
- C. GitHub Marketplace
- D. Organization settings
Answer: C
Explanation:
The GitHub Marketplace is the place where users can discover, browse, and install various tools and integrations that extend the functionality of GitHub. These tools can include CI/CD services, security checks, and other development utilities that enhance workflow automation and project management.
NEW QUESTION # 33
What is GitHub?
- A. A platform that focuses on facilitating the growth and sharing of code, specifically designed for new developers to hone their skills
- B. A proprietary software platform for nurturing creativity in developers and building a technology community
- C. A cloud-based hosting service for version control and collaboration, focused on creating a safe and collaborative environment for developers
- D. A centralized version control system designed for nurturing a community of developers and providing access to open source projects
Answer: C
Explanation:
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
NEW QUESTION # 34
Workflows can reference actions in:
(Each correct answer presents a complete solution. Choose three.)
- A. GitHub Packages.
- B. An enterprise marketplace.
- C. Any public repository.
- D. A published Docker container image on Docker Hub.
- E. The same repository as your workflow file.
Answer: C,D,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
NEW QUESTION # 35
What are the defining features of Git?
- A. Distributed version control, open source software, and being designed for handling projects of any size with efficiency
- B. Low-cost local branching, convenient staging areas, multiple workflows, and being designed for managing small projects
- C. Sequential version control, cloud-based hosting service, and being designed for collaboration on large projects
- D. Centralized version control, proprietary software, and being designed for small projects
Answer: A
Explanation:
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.
Incorrect Options:
Option B is incorrect because Git is not a sequential version control system, nor is it inherently tied to cloud-based services. GitHub, GitLab, and other platforms offer cloud hosting for Git repositories, but Git itself is a version control tool.
Option C is incorrect because Git is not limited to small projects; it is designed to scale efficiently, and the other features mentioned are only partial descriptions of Git's capabilities.
Option D is incorrect because Git is not a centralized version control system; it is distributed. Additionally, Git is open-source, not proprietary, and is used for projects of all sizes.
Reference:
Pro Git Book: What is Git?
Git Documentation: Distributed Version Control
GitHub Docs: Understanding the Git Workflow
NEW QUESTION # 36
What does a CODEOWNERS file do in a repository?
- A. Restricts who can edit specific files
- B. Defines access permissions for the repository
- C. Sets the reviewers for pull requests automatically
- D. Requires peer code review for code changes
Answer: C
Explanation:
The CODEOWNERS file in a GitHub repository is used to define individuals or teams that are responsible for specific parts of the codebase. When changes are made to files or directories that match the patterns specified in the CODEOWNERS file, GitHub automatically requests reviews from the listed code owners.
Setting Reviewers Automatically:
Option D is correct because the primary purpose of a CODEOWNERS file is to automatically set reviewers for pull requests that affect the specified files or directories. This ensures that the appropriate team members are notified and review the changes before they are merged.
Incorrect Options:
Option A is incorrect because the CODEOWNERS file does not restrict who can edit specific files; it only influences who is required to review changes.
Option B is partially related but not fully accurate because while CODEOWNERS does require certain reviews, it does not mandate peer review for all code changes.
Option C is incorrect because the CODEOWNERS file does not define access permissions for the repository; it deals with code review processes.
Reference:
GitHub Docs: About CODEOWNERS
GitHub Blog: Automatically Requesting Reviews with CODEOWNERS
NEW QUESTION # 37
What is the primary purpose of creating a security policy in a repository?
- A. To ensure that peer code review occurs before new changes are merged
- B. To describe how security vulnerabilities should be responsibly disclosed
- C. To define which types of secrets are blocked with push protection
- D. To customize the repository's Dependabot configuration
Answer: B
Explanation:
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.
Incorrect Options:
Option A is incorrect because ensuring peer code review is a best practice for code quality, but it is not the primary purpose of a security policy.
Option B is incorrect because push protection for secrets is managed through repository settings, not the security policy.
Option D is incorrect because customizing Dependabot configuration is related to dependency management, not directly to security policies.
Reference:
GitHub Docs: Adding a Security Policy to Your Repository
NEW QUESTION # 38
......
Get Instant Access to GH-900 Practice Exam Questions: https://www.actual4exams.com/GH-900-valid-dump.html
The Best GH-900 Exam Study Material Premium Files and Preparation Tool: https://drive.google.com/open?id=1JlGBt0mVa48DOsAf_L9TNCctGi5mrPeO