Microsoft GH-900 Online Practice Questions and Exam Preparation

Microsoft GH-900 Online Questions & Answers

• Question 71:

  Which of the following GitHub syntax formats is consistent with the associated text?

  A. * This is a heading
  B. This is a link
  D. This is bolded text
  E. 1. This is an ordered list
  C

  ---

  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 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.

  References: GitHub Flavored Markdown (GFM) GitHub Docs: Basic writing and formatting syntax

• Question 72:

  Who can be assigned to an Issue or pull request? (Each answer presents a complete solution. Choose two.)

  A. Anyone who has an enterprise GitHub account
  B. Anyone who has commented on the Issue or pull request
  C. Anyone who has a personal GitHub account
  D. Anyone with write permissions to the repository
  B. Anyone who has commented on the Issue or pull request
  D. Anyone with write permissions to the repository

  ---

  Explanation

  In GitHub, issues and pull requests (PRs) are essential tools for managing work and collaboration in a project. Assigning individuals to these issues or PRs is a way to indicate responsibility for addressing the issue or completing the PR.

  Anyone with write permissions to the repository:

  Users who have write permissions to a repository can be assigned to issues and pull requests. Write permissions allow users to push changes to the repository, create branches, and modify issues and pull requests. Assigning them to an

  issue or PR ensures they are recognized as responsible for the task.

  Anyone who has commented on the Issue or pull request:

  GitHub allows you to assign issues or pull requests to users who have already engaged with the discussion by commenting on it. This feature is particularly useful for quickly assigning tasks to those who are already involved in the

  conversation.

  Incorrect Options:

  Option A is incorrect because having an enterprise GitHub account alone does not necessarily grant the ability to be assigned to issues or PRs. Permission to assign is based on repository-specific roles and permissions.

  Option C is incorrect because not all personal GitHub accounts can be assigned to issues or PRs. The user needs either write permissions to the repository or must have commented on the issue or PR.

  References:

  GitHub Docs: Assigning Issues and Pull Requests

  GitHub Docs: Permission Levels for a Repository

  This detailed explanation provides clarity on GitHub's assignment mechanics for issues and pull requests, reflecting the platform's collaborative nature.

• Question 73:

  From the list of projects for an organization, how can a user identify a GitHub Projects template?

  A. Check the "show template" checkbox.
  B. Use the "is" filter in the search text box.
  C. Select the Templates tab.
  D. View the contents in the .github/projects folder.
  C. Select the Templates tab.

  ---

  Explanation

  In GitHub, when viewing the list of projects for an organization, a user can identify a GitHub Projects template by selecting the Templates tab. This tab specifically lists available templates that can be used to create new projects based on predefined structures and workflows.

• Question 74:

  How can a user highlight a post to the top of the Discussions page?

  A. Save the discussion.
  B. Pin the discussion.
  C. Create an issue from the discussion.
  D. Star the discussion.
  B. Pin the discussion.

  ---

  Explanation

  To highlight a post at the top of the Discussions page on GitHub, you can Pin the discussion. Pinning a discussion ensures it remains prominently visible at the top of the list, making it easier for others to find and participate in that discussion. This is particularly useful for important announcements or frequently referenced topics.

• Question 75:

  What is GitHub?

  A. A proprietary software platform for nurturing creativity in developers and building a technology community
  B. A cloud-based hosting service for version control and collaboration, focused on creating a safe and collaborative environment for developers
  C. A platform that focuses on facilitating the growth and sharing of code, specifically designed for new developers to hone their skills
  D. A centralized version control system designed for nurturing a community of developers and providing access to open source projects
  B. A cloud-based hosting service for version control and collaboration, focused on creating a safe and collaborative environment for developers

  ---

  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.

  References:

  GitHub Docs: About GitHub