Microsoft GH-900 Online Practice Questions and Exam Preparation

Microsoft GH-900 Online Questions & Answers

• Question 1:

  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:

  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 2:

  Which of the following can be performed within GitHub Desktop?

  A. Creating and managing issues
  B. Reviewing and approving pull requests
  C. Adding and cloning repositories
  D. Commenting on discussions
  E. Integrating with office suite software
  C. Adding and cloning repositories

  ---

  explanation:

  Explanation

  GitHub Desktop is a graphical interface that allows users to interact with GitHub repositories. It simplifies certain Git operations without the need for command-line usage.

  GitHub Desktop Capabilities:

  Option C is correct because GitHub Desktop allows users to add local repositories to their GitHub account, clone repositories from GitHub to their local machine, and manage repositories effectively.

  Incorrect Options:

  Option A is incorrect because GitHub Desktop does not support creating or managing issues directly; this is done through the GitHub web interface. Option B is incorrect because reviewing and approving pull requests is also managed

  through the GitHub web interface.

  Option D is incorrect because commenting on discussions is done on the GitHub platform, not through GitHub Desktop.

  Option E is incorrect because GitHub Desktop does not integrate with office suite software.

  References:

  GitHub Docs: GitHub Desktop Documentation

• Question 3:

  Which of the following is the best GitHub feature for long-form documentation for a project?

  A. Insights
  B. Pull Requests
  C. Projects
  D. Wikis
  D. Wikis

  ---

  explanation:

  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.

• Question 4:

  Which of the following options can a user do from a discussion post?

  A. Duplicate the discussion
  B. Archive the discussion
  C. Create an issue from the discussion
  D. Add the discussion to README
  C. Create an issue from the discussion

  ---

  explanation:

  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.

• Question 5:

  What best describes Markdown?

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

  ---

  explanation:

  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 6:

  When using Organizations, GitHub Teams is better than GitHub Free because it offers: A. Advanced tools and insights in private repositories.

  B. Authentication with SAML single sign-on and increased GitHub Actions minutes.

  C. Expanded storage and priority support.

  D. Increased GitHub Actions minutes and additional GitHub Packages storage.

  Correct Answer. B
  B

  ---

  explanation:

  Explanation

  GitHub Teams, as part of GitHub’s paid plans, offers additional features and capabilities compared to GitHub Free, particularly for organizations.

  GitHub Teams Benefits:

  Option B is correct because GitHub Teams provides advanced security features like SAML single sign-on for secure authentication, as well as increased minutes for running GitHub Actions, which are essential for continuous integration and

  deployment workflows.

  Incorrect Options:

  Option A is incorrect because private repositories and advanced tools are features available, but the key differentiator in this context is the SAML SSO and additional GitHub Actions minutes.

  Option C is incorrect because while expanded storage and priority support are valuable, SAML SSO and increased GitHub Actions minutes are more central to the differences between GitHub Free and GitHub Teams. Option D is partially

  correct, but since the question asks for the best reason, Option B provides the most critical features that differentiate GitHub Teams from GitHub Free.

  References:

  GitHub Docs: About GitHub Teams

• Question 7:

  What are advantages of GitHub Projects over GitHub Projects Classic? (Each answer presents a complete solution. Choose two.)

  A. GitHub Projects has multiple layout views.
  B. GitHub Projects has Insights.
  C. GitHub Projects are Copilot enabled.
  D. GitHub Projects can be connected to third-party tools.
  A. GitHub Projects has multiple layout views.
  B. GitHub Projects has Insights.

  ---

  explanation:

  Explanation

  GitHub Projects is a newer, more powerful version of project management within GitHub, offering enhanced features over the classic version.

  Multiple Layout Views:

  Option A is correct because GitHub Projects supports multiple views, such as board, table, and timeline views, allowing users to visualize their work in different ways according to their needs.

  Insights:

  Option B is correct because GitHub Projects provides insights and analytics, enabling teams to track progress and make data-driven decisions.

  Incorrect Options:

  Option C is incorrect because while GitHub Copilot is a tool for code suggestions, it is not directly integrated with GitHub Projects as a feature. Option D is incorrect because both GitHub Projects and GitHub Projects Classic can be connected

  to third-party tools, so it is not an exclusive advantage of the newer GitHub Projects.

  References: GitHub Docs: Managing Projects

• Question 8:

  Workflows can reference actions in: (Each correct answer presents a complete solution. Choose three.)

  A. Any public repository.
  B. The same repository as your workflow file.
  C. GitHub Packages.
  D. An enterprise marketplace.
  E. A published Docker container image on Docker Hub.
  A. Any public repository.
  B. The same repository as your workflow file.
  E. A published Docker container image on Docker Hub.

  ---

  explanation:

  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.

  References:

  GitHub Docs: Reusing Workflows

• Question 9:

  What are the two main reasons why one might fork a repository? (Each answer presents a complete solution. Choose two.)

  A. To create an issue or open a discussion
  B. To propose changes to the base repository
  C. To create a new repository based on an existing one
  D. 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

  ---

  explanation:

  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

• Question 10:

  How can a user create a repository template, and what permissions are required?

  A. With Admin permissions, navigate to Repository settings and select Template Repository.
  B. With Maintain permissions, navigate to Organization settings, select the repository, and choose Template Repository.
  C. With Admin permissions, navigate to Organization settings, select the repository, and choose Template Repository.
  D. With Maintain permissions, navigate to Repository settings and select Template Repository.
  A. With Admin permissions, navigate to Repository settings and select Template Repository.

  ---

  explanation:

  Explanation

  Creating a repository template in GitHub requires specific steps and permissions:

  Creating a Repository Template:

  Option A is correct because a user with Admin permissions can navigate to the repository's settings and enable the "Template Repository" option. This allows other users to generate new repositories from this template, which includes all

  branches, tags, and file history.

  Other Options:

  Option B is incorrect because "Maintain" permissions do not allow the creation of repository templates, and the option is not found in Organization settings but in the repository settings. Option C is incorrect because the "Template Repository"

  option is in the repository settings, not in Organization settings.

  Option D is incorrect because "Maintain" permissions do not grant the ability to create a repository template.

  References:

  GitHub Docs: Creating a Template Repository