Microsoft GH-900 Online Practice Questions and Exam Preparation

Microsoft GH-900 Online Questions & Answers

• Question 1:

  What features are offered by Copilot for Business that are not offered by Copilot for individuals? (Each answer presents a complete solution. Choose three.)

  A. Offers multi-line function suggestions
  B. Organization-wide policy management
  C. Blocks suggestions matching public code
  D. VPN proxy support via self-signed certificates
  E. Support for organization or enterprise GitHub accounts
  F. Plugs directly into the editor
  B. Organization-wide policy management
  C. Blocks suggestions matching public code
  E. Support for organization or enterprise GitHub accounts

  ---

  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.

  References:

  GitHub Docs: GitHub Copilot for Business

• Question 2:

  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. Fork the gist.
  B. Create a new gist and copy the content from the existing gist.
  C. Clone the gist.
  D. Request to be added to the existing gist.
  A. Fork the gist.

  ---

  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.

  References:

  GitHub Docs: Forking Gists

• Question 3:

  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. Create a new workflow file.
  B. Search the vendor’s website for a github.yaml index.
  C. Confirm that the action has a verification badge.
  D. Install the GitHub App that was provided by the vendor.
  E. Add the vendor as an allowed Actions Source.
  F. Search the GitHub Marketplace for Actions by the vendor.
  C. Confirm that the action has a verification badge.
  F. Search the GitHub Marketplace for Actions by the vendor.

  ---

  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.

  References:

  GitHub Marketplace: Verified Actions

• Question 4:

  What best describes Markdown?

  A. Markup language
  B. Programming language
  C. Scripting language
  D. Version control system
  E. Containerization solution
  A. Markup language

  ---

  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

• Question 5:

  What is the purpose of GitHub Sponsors?

  A. It funds the most popular open source projects based on stars.
  B. It provides a channel for GitHub to support open source projects.
  C. It offers a way for companies to purchase software on GitHub.
  D. It allows the developer community to financially support open source projects.
  D. It allows the developer community to financially support open source projects.

  ---

  Explanation

  GitHub Sponsors is a program designed to provide a platform for developers and companies to financially support open-source projects and their maintainers.

  Financial Support for Open Source Projects:

  Option D is correct because the main purpose of GitHub Sponsors is to allow members of the developer community, including individuals and organizations, to financially support open-source projects and maintainers. This helps sustain

  open-source development by providing developers with the resources they need to continue their work.

  Incorrect Options:

  Option A is incorrect because GitHub Sponsors is not based on project popularity (e.g., stars); it is based on voluntary contributions. Option B is incorrect because while GitHub provides the platform, the purpose of GitHub Sponsors is not for

  GitHub itself to fund projects, but to enable the broader community to do so.

  Option C is incorrect because GitHub Sponsors is not a marketplace for purchasing software but a platform for supporting developers.

  References:

  GitHub Docs: GitHub Sponsors

• Question 6:

  Which of the following steps are part of the Codespaces lifecycle? (Each answer presents a complete solution. Choose three.)

  A. Commit
  B. Clone
  C. Rebuild
  D. Rollback
  E. Delete
  F. Create
  G. Install
  C. Rebuild
  E. Delete
  F. Create

  ---

  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.

• Question 7:

  An employee needs to find all issues within organization “Avocado" containing text "404 error" and a "guacamole" label. Which of the following steps would be best to search for these results?

  A. Enter query org:Avocado is:issue label:guacamole "404 error" in the search bar.
  B. Go to "Avocado" organization. Select Issues under a repository. Filter issues with a "guacamole" label.
  C. Enter query org:Avocado label:guacamole "404 error" in the search bar. Select "Issues" in the Filter by section.
  D. Go to the Avocado organization settings. Select Repository defaults under Repository. Scroll to Repository labels and select the 'guacamole' label.
  A. Enter query org:Avocado is:issue label:guacamole "404 error" in the search bar.

  ---

  Explanation

  GitHub provides a powerful search syntax to filter and find specific issues across repositories in an organization.

  Search Query Syntax:

  Option A is correct because the query org:Avocado is:issue label:guacamole "404 error" is the best way to search for all issues within the "Avocado" organization that contain the text "404 error" and are labeled with "guacamole". This query is

  precise and leverages GitHub’s advanced search capabilities.

  Incorrect Options:

  Option B is incorrect because it requires manual filtering in a specific repository rather than searching across the entire organization. Option C is incorrect because selecting "Issues" in the filter by section is redundant when using the query

  is:issue.

  Option D is incorrect because accessing organization settings to look for repository labels is not relevant to searching for issues.

  References:

  GitHub Docs: Searching Issues and Pull Requests

• Question 8:

  Which of the following are available statuses of a pull request? (Each answer presents a complete solution. Choose four.)

  A. Draft
  B. Closed
  C. Rebasing
  D. Merged
  E. Modified
  F. Open
  A. Draft
  B. Closed
  D. Merged
  F. Open

  ---

  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.

  References:

  GitHub Docs: About Pull Requests

• Question 9:

  What is the primary purpose of creating a new branch in the GitHub flow?

  A. To create a backup of the main branch
  B. To capture information about an issue
  C. To experiment with new features or fixes
  D. To incorporate changes from a review
  C. To experiment with new features or fixes

  ---

  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.

  References:

  GitHub Docs: GitHub Flow

• Question 10:

  What is a gist?

  A. GitHub app
  B. Git repository
  C. Markdown document
  D. GitHub Pages site
  B. Git repository

  ---

  Explanation

  A gist on GitHub is essentially a Git repository, albeit a simplified one, designed for sharing snippets of code, notes, or other text content. Gists support version control and can be public or secret.

  Gist as a Git Repository:

  Option B is correct because each gist is a Git repository, meaning you can clone it, commit changes, and even fork it, just like any other Git repository.

  Incorrect Options:

  Option A is incorrect because a gist is not an app; it’s a feature of GitHub that provides a simplified repository.

  Option C is incorrect because while a gist may contain Markdown documents, it is fundamentally a repository that can hold various file types.

  Option D is incorrect because GitHub Pages is a separate service for hosting websites, not related to gists.

  References: GitHub Docs: About Gists