[Sep-2026 Newly Released] GH-900 Exam Questions For You To Pass
Microsoft GH-900 Exam: Basic Questions With Answers
Microsoft GH-900 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
NEW QUESTION # 23
You are working on a collaborative software project and want to ensure that your code is automatically built and tested every time a contributor opens a pull request. A teammate suggests using GitHub Actions for this purpose. Which of the following best describes the purpose of GitHub Actions?
- A. A built-in GitHub feature for managing repository access, contributors, and permissions
- B. A documentation system within GitHub where teams can write internal wikis and tutorials
- C. A CI/CD platform within GitHub that lets you automate workflows for building, testing, and deploying coderight
- D. A tool used to write issues and assign them automatically to contributors using labels
Answer: C
Explanation:
GitHub Actions is a CI/CD platform within GitHub that lets you automate workflows for building, testing, and deploying code. It enables teams to set up automated processes that run whenever certain events occur, such as opening a pull request. This ensures that code changes are tested and built consistently before merging, improving reliability and streamlining collaboration.
Option C is CORRECT because GitHub Actions is a CI/CD automation platform built into GitHub that lets you create workflows to build, test, and deploy your code automatically based on repository events such as pushes or pull requests.
Reference:
https://docs.github.com/en/actions/learn-github-actions/understanding-github-actions
NEW QUESTION # 24
Where can you go to discover, browse, and install tools?
- A. GitHub Apps
- B. Organization settings
- C. GitHub Marketplace
- D. Explore
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 # 25
Which three of the following actions will automatically subscribe you to a conversation on GitHub? Each answer presents a complete solution.
- A. Opening a pull request
- B. Being at-mentioned in a thread
- C. Commenting on an issue or pull request
- D. Changing the repository visibility
- E. Deleting a branch
Answer: A,B,C
Explanation:
GitHub automatically subscribes users to conversations when their direct involvement indicates they may need future notifications. Being at-mentioned in a thread subscribes the mentioned user because GitHub treats the mention as a direct request for attention. Opening a pull request also subscribes the author because they own the proposed change and need updates about reviews, comments, checks, and merge activity. Commenting on an issue or pull request subscribes the commenter because they have participated in the conversation and may need follow-up notifications. Deleting a branch does not represent participation in a specific conversation, and changing repository visibility is an administrative repository action rather than a conversation-level activity. Automatic subscriptions help users stay informed about discussions relevant to them.
NEW QUESTION # 26
You are collaborating on a large open-source project hosted on GitHub. To stay informed about discussions and progress, you want to be notified whenever someone mentions your username or assigns you an issue. You're also planning to showcase your project through a website using GitHub Pages. Which of the following actions or features would help you manage notifications effectively and publicize your project? (Choose three.)
- A. Use the mentions: qualifier to find threads where you are mentionedright
- B. Enable GitHub Actions to send email notifications for every commit
- C. Use GitHub Pages to host a static website directly from a repositoryright
- D. Subscribe to an individual issue, pull request, or gist to receive updatesright
Answer: A,C,D
Explanation:
To effectively manage notifications and showcase your project, you can use the mentions:
qualifier to find discussions where you're mentioned, subscribe to specific issues or pull requests to receive updates, and leverage GitHub Pages to host a static website that highlights your work.
Option A is CORRECT because this helps you quickly locate discussions in which your username was mentioned, so you can stay informed.
Option C is CORRECT because GitHub allows users to subscribe to specific issues, pull requests, or gists so that they receive notifications related to those conversations.
Option D is CORRECT because this feature allows you to showcase your project publicly, making it accessible to a wider audience through a hosted website.
References:
https://learn.microsoft.com/en-us/training/modules/introduction-to-github/5-platform-management
https://docs.github.com/en/pages/getting-started-with-github-pages/what-is-github-pages
NEW QUESTION # 27
What are primary benefits of using GitHub issues templates? (Choose two.)
- A. To automatically label or assign newly created issues
- B. To provide an easy-to-fill-out form for creating new issues
- C. To automatically create new branches when issues are created
- D. To easily coerce existing issues into a standard format
Answer: 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.
NEW QUESTION # 28
What command should you type to create and switch over to a new branch?
- A. git checkout -n newBranchName
- B. git branch newBranchName
- C. git checkout newBranchName
- D. git checkout -b newBranchName
Answer: D
Explanation:
git checkout -b <new-branch>
Create a new branch named <new-branch>, start it at <start-point>, and check the resulting branch out; Incorrect:
[Not C] git checkout [<branch>]
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing HEAD at the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the <branch>.
Reference:
https://git-scm.com/docs/git-checkout
NEW QUESTION # 29
What is the minimum access needed to contribute to a repository?
- A. Write
- B. Maintain
- C. Triage
- D. Read
Answer: A
Explanation:
To contribute to a GitHub repository, a user typically needs to be able to create branches, push changes, and open pull requests. These actions require Write access, which is the minimum level of access needed to contribute code directly to a repository.
Write Access:
Option D is correct because "Write" access allows users to contribute to the repository by pushing changes, creating branches, and opening pull requests. This is the minimum required access level for contributing code.
NEW QUESTION # 30
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. Security questions
- B. Authenticator app
- C. Security keys
- D. Single sign-on
- E. GitHub mobile
Answer: B,C,E
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.
NEW QUESTION # 31
A centralized version control system is a system that:
- A. relies on a central server to store the entire project history and allows developers to check out files for editing.
- B. ensures each developer has their own local copy of the central code repository, including the complete project history and metadata.
- C. requires developers to manually track and manage different versions of their files using naming conventions and manual backups.
- D. stores project files on a cloud-based server and allows multiple developers to collaborate on the same files simultaneously.
Answer: A
Explanation:
A centralized version control system stores the main project history in one central location, usually a server. Developers connect to that server to check out files, make changes, and submit updates. This differs from Git, which is distributed and allows every developer to have a full local copy of the repository history. In a centralized model, collaboration depends heavily on the availability of the central server. If the server is unavailable, developers may be limited in what they can do. GitHub Foundations emphasizes this distinction because GitHub is built around Git, a distributed version control system. Option C correctly describes centralized version control because the central server holds the authoritative project history.
NEW QUESTION # 32
What are the two main reasons why one might fork a repository? (Choose two.)
- A. To create a new branch to develop a new feature
- B. To propose changes to the base repository
- C. To create a new repository based on an existing one
- D. To create an issue or open a discussion
Answer: B,C
Explanation:
Forking a repository on GitHub is a common practice, especially when contributing to open- source projects or when you want to build on existing work. Here are the two main reasons for forking a repository:
B). To propose changes to the base repository:
One of the primary reasons for forking a repository is to make changes or improvements that you can later propose to the original repository (often called the "upstream" repository). This is typically done through a pull request. By forking the repository, you get your own copy of the project where you can freely experiment, make changes, and then propose those changes back to the original project.
C). To create a new repository based on an existing one:
Forking is also used to create a new repository that is a copy of an existing one. This allows you to work on the project independently of the original repository, effectively creating a new direction for the project or using it as a starting point for a different purpose. This is particularly useful for customization, experimentation, or when you want to build something different while still leveraging the existing codebase.
NEW QUESTION # 33
Which of the following outcomes can be achieved with a branch protection rule?
- A. Require two-factor authentication (2FA) by code contributors.
- B. Restrict who can view the branch.
- C. Require approval before merging changes.
- D. Block code pushes that contain hardcoded secrets.
Answer: C
NEW QUESTION # 34
From the list of projects for an organization, how can a user identify a GitHub Projects template?
- A. Check the "show template" checkbox.
- B. View the contents in the .github/projects folder.
- C. Use the is:template filter in the search text box.
- D. Select the Templates label.
Answer: C
Explanation:
Users can identify and filter GitHub Projects templates by using the is:template search filter in the organization's project list, which displays only projects designated as templates.
NEW QUESTION # 35
What best describes Markdown?
- A. Markup language
- B. Programming language
- C. Containerization solution
- D. Version control system
- E. Scripting language
Answer: A
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.
References:
GitHub Docs: Basic writing and formatting syntax
NEW QUESTION # 36
When making comments in GitHub, the supported text language is:
- A. JSON.
- B. XML.
- C. JavaScript.
- D. CSS.
- E. Markdown.
Answer: E
Explanation:
Markdown is an easy-to-read, easy-to-write language for formatting plain text. You can use Markdown syntax, along with some additional HTML tags, to format your writing on GitHub, in places like repository READMEs and comments on pull requests and issues.
Reference:
https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and- formatting-on-github/quickstart-for-writing-on-github
NEW QUESTION # 37
You've made changes in a branch called feature-update and now want to merge it into the main branch of the same repository. What is the correct base and compare setup when opening a pull request?
- A. Base: main, Compare: feature-updateright
- B. Base: develop, Compare: main
- C. Base: main, Compare: main
- D. Base: feature-update, Compare: main
Answer: A
Explanation:
The base branch is where the changes will be merged into (usually main), and the compare branch is where the changes are coming from (feature-update).
Option A is CORRECT because when creating a pull request, the base branch is the one you want to merge your changes into (in this case, main), and the compare branch is the one that contains the new changes (in this case, feature-update).
References:
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to- your-work-with-pull-requests/creating-a-pull-request
https://docs.github.com/en/repositories/creating-and-managing-repositories/about-repositories
NEW QUESTION # 38
Where can a user manually link a pull request to an issue?
- A. in the right sidebar of the pull request, under " Assignees "
- B. in the description of the issue
- C. in the right sidebar of the pull request, under " Development "
- D. in the comment section of the issue
Answer: C
NEW QUESTION # 39
What type of operations has Git been optimized for?
- A. local file manipulation and offline work
- B. web development and browser-based coding
- C. remote collaboration and real-time editing
- D. cloud-based operations and synchronization
Answer: A
NEW QUESTION # 40
How are commits related to pull requests?
- A. Commits can only be made before a pull request is created.
- B. Commits can only be made after a pull request is created.
- C. Commits are made on a pull request that can have a linked branch.
- D. Commits are made on a branch that can have a linked pull request.
Answer: D
Explanation:
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).
References:
GitHub Documentation: About Pull Requests
GitHub Docs: Understanding the GitHub Flow
Git Documentation: Git Basics - Getting a Git Repository
NEW QUESTION # 41
What are the two main reasons why one might fork a repository?
(Each answer presents a complete solution. Choose two.)
- A. To create a new branch to develop a new feature
- B. To propose changes to the base repository
- C. To create a new repository based on an existing one
- D. To create an issue or open a discussion
Answer: B,C
Explanation:
Forking a repository on GitHub is a common practice, especially when contributing to open-source projects or when you want to build on existing work. Here are the two main reasons for forking a repository:
* B. To propose changes to the base repository :
* One of the primary reasons for forking a repository is to make changes or improvements that you can later propose to the original repository (often called the " upstream " repository). This is typically done through a pull request. By forking the repository, you get your own copy of the project where you can freely experiment, make changes, and then propose those changes back to the original project.
* C. To create a new repository based on an existing one :
* Forking is also used to create a new repository that is a copy of an existing one. This allows you to work on the project independently of the original repository, effectively creating a new direction for the project or using it as a starting point for a different purpose. This is particularly useful for customization, experimentation, or when you want to build something different while still leveraging the existing codebase.
Explanation of Other Options :
* A. To create an issue or open a discussion :
* This is incorrect because creating an issue or opening a discussion can be done directly on the original repository without needing to fork it. Forking is unnecessary for these actions.
* D. To create a new branch to develop a new feature :
* While creating a new branch is related to development, it does not require a fork. Branches are typically created within the same repository to work on new features. Forking is used when you need an entirely separate copy of the repository.
Given this information, the correct answers are B and C .
References:
GitHub Documentation: Fork a repo
GitHub Documentation: About forks
NEW QUESTION # 42
What are some scenarios that can automatically subscribe you to conversations on GitHub?
(Choose three.)
- A. Opening a pull request or issue
- B. Commenting on a thread
- C. Being assigned to an issue or pull request
- D. Being added as a repo admin
- E. Pushing a commit to the default branch
Answer: A,B,C
Explanation:
On GitHub, certain actions automatically subscribe you to conversations so that you receive notifications about further activity in that thread.
Opening a Pull Request or Issue:
Option C is correct because when you open a pull request or issue, you are automatically subscribed to the conversation and will receive notifications for any updates.
Commenting on a Thread:
Option D is correct because commenting on an issue or pull request automatically subscribes you to that thread, ensuring you are notified of further comments or changes.
Being Assigned to an Issue or Pull Request:
Option E is correct because when you are assigned to an issue or pull request, you are automatically subscribed to notifications related to it.
NEW QUESTION # 43
......
New 2026 Realistic Free Microsoft GH-900 Exam Dump Questions and Answer: https://braindumps.exam4tests.com/GH-900-pdf-braindumps.html