Microsoft GH-900 Online Practice Questions and Exam Preparation

Microsoft GH-900 Online Questions & Answers

• Question 61:

  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

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

  Which of the following can be performed within GitHub Mobile?

  A. Utilizing the mobile device as a self-hosted runner
  B. Managing enterprise and organization settings
  C. Chat with other GitHub Mobile users via voice calling
  D. Forking and cloning repositories
  E. Managing notifications from github.com
  E. Managing notifications from github.com

  ---

  Explanation

  GitHub Mobile provides a streamlined experience for managing your GitHub notifications and participating in discussions, but it does not offer full functionality compared to the desktop or web interface.

  Managing Notifications:

  Option E is correct because GitHub Mobile allows users to manage notifications, keeping them up to date with their repositories, issues, pull requests, and other activities on GitHub.

  Incorrect Options:

  Option A is incorrect because GitHub Mobile cannot be used as a self-hosted runner.

  Option B is incorrect because managing enterprise and organization settings is not supported in GitHub Mobile.

  Option C is incorrect because GitHub Mobile does not offer a chat or voice calling feature.

  Option D is incorrect because forking and cloning repositories are not actions available in GitHub Mobile.

  References:

  GitHub Docs: GitHub Mobile

• Question 63:

  Which of the following best describes cloning a repository?

  A. It creates a copy of the repository on GitHub.com.
  B. It retrieves code updates from the remote repository.
  C. It creates a copy of the repository on your local machine.
  D. It imports your source code into a new repository.
  C. It creates a copy of the repository on your local machine.

  ---

  Explanation

  Cloning a repository in GitHub refers to creating a copy of the repository on your local machine. This allows you to work on the project offline, make changes, and later push those changes back to the remote repository. It does not involve creating a copy on GitHub.com (which would be forking), retrieving updates (which would be pulling), or importing source code into a new repository (which is done differently).

• Question 64:

  If there are multiple README files, which of the following locations will be displayed first?

  A. .github
  B. /src
  C. Root
  D. /docs
  C. Root

  ---

  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.

  References:

  GitHub Docs: About READMEs

• Question 65:

  New open source contributors can receive funding from GitHub sponsors:

  A. Using PayPal as a payment processor.
  B. Equal to 95% of the contribution value.
  C. By including GitHub matching funds.
  D. After setting up a sponsored developer profile.
  D. After setting up a sponsored developer profile.

  ---

  Explanation

  GitHub Sponsors allows developers and organizations to financially support open-source contributors directly on the GitHub platform.

  Setting Up a Sponsored Developer Profile:

  Option D is correct because before a contributor can receive funding through GitHub Sponsors,they need

• Question 66:

  What are some scenarios that can automatically subscribe you to conversations on GitHub? (Each answer presents a complete solution. Choose three.)

  A. Pushing a commit to the default branch
  B. Being added as a repo admin
  C. Opening a pull request or issue
  D. Commenting on a thread
  E. Being assigned to an issue or pull request
  C. Opening a pull request or issue
  D. Commenting on a thread
  E. Being assigned to an issue or pull request

  ---

  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.

  Incorrect Options:

  Option A is incorrect because pushing a commit to the default branch does not automatically subscribe you to conversations. Option B is incorrect because being added as a repo admin does not automatically subscribe you to specific

  conversations unless you engage with them.

  References: GitHub Docs: Subscribing to Notifications

• Question 67:

  GitHub Actions workflows can be directly triggered by which of the following events? (Each answer presents a complete solution. Choose three.)

  A. Adding a comment to a discussion post
  B. Creating a new repository
  C. Committing a change to a local git repository
  D. Pushing to a GitHub repository
  E. Disabling a GitHub runner
  F. Creating an Issue
  A. Adding a comment to a discussion post
  D. Pushing to a GitHub repository
  F. Creating an Issue

  ---

  Explanation

  GitHub Actions are automated workflows that can be triggered by various events on GitHub. Some common events that trigger workflows include pushes to a repository, creation of issues, and comments on discussion posts.

  Triggering GitHub Actions:

  Option D (Pushing to a GitHub repository) is correct because this is one of the most common triggers for CI/CD workflows.

  Option F (Creating an Issue) is correct because issues are commonly used as triggers for workflows, such as automatically assigning a label or notifying a team.

  Option A (Adding a comment to a discussion post) is correct because actions can be triggered by activity on discussion posts, including comments.

  Incorrect Options:

  Option B (Creating a new repository) is incorrect because this action typically does not trigger workflows within a specific repository.

  Option C (Committing a change to a local git repository) is incorrect because GitHub Actions are triggered by events on the GitHub platform, not by local commits.

  Option E (Disabling a GitHub runner) is incorrect because it is related to the environment where actions are executed, not a trigger for workflows.

  References:

  GitHub Docs: Events That Trigger Workflows

• Question 68:

  Which of the following is a primary goal of GitHub's community?

  A. Exclusively supporting experienced developers
  B. Creating a competitive environment for developers
  C. Facilitating collaboration and creativity
  D. Enforcing strict code quality standards
  C. Facilitating collaboration and creativity

  ---

  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.

  References:

  GitHub Docs: Building a Strong Community

• Question 69:

  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

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

  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. Create a README file describing the repository.
  C. Add labels to categorize the repository.
  D. Add topics to classify the repository.
  B. Create a README file describing the repository.
  D. Add topics to classify the repository.

  ---

  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.