Microsoft GH-900 Online Practice Questions and Exam Preparation

Microsoft GH-900 Online Questions & Answers

• Question 11:

  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

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

  As a user, what feature can you use to merge proposed changes in a repository on GitHub?

  A. Issues
  B. Pull requests
  C. Projects
  D. Discussions
  B. Pull requests

  ---

  Explanation

  The feature you can use to merge proposed changes in a repository on GitHub is Pull requests. Pull requests are a core feature of GitHub, allowing developers to propose changes to a codebase, review code, discuss the changes, and eventually merge them into the main branch. This collaborative workflow ensures that code is reviewed and vetted before becoming part of the project.

• Question 13:

  As a GitHub user, where in the UI can you configure two-factor authentication (2FA) to further secure your account?

  A. Profile -> Account -> 2FA
  B. Repository Settings -> Secrets and Variables -> 2FA
  C. Organization Settings -> Authentication Security -> 2FA
  D. Settings -> Password and Authentication -> 2FA
  D. Settings -> Password and Authentication -> 2FA

  ---

  Explanation

  As a GitHub user, you can configure two-factor authentication (2FA) to secure your account by navigating to Settings -> Password and Authentication -> 2FA. This section in the GitHub user interface allows you to set up and manage your 2FA methods, which provide an additional layer of security beyond just your password.

• Question 14:

  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

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

  Which of the following statements most accurately describes who can access a private repository Wiki?

  A. Wikis are only viewable by repository admins.
  B. Wikis can be viewed by the same people who have Read access to the repository.
  C. Wikis will not be visible until shared with a specific user.
  D. Wikis are public regardless of whether you have access to the repository.
  B. Wikis can be viewed by the same people who have Read access to the repository.

  ---

  Explanation

  For private repositories on GitHub, the Wiki is accessible to anyone who has Read access to the repository. This means that if you can view the code and files in the repository, you can also view its Wiki. This makes Wikis a useful tool for documenting projects in a way that is available to all collaborators without requiring special permissions beyond those needed to access the repository itself.

• Question 16:

  Which of the following best describes GitHub Copilot?

  A. A Visual Studio Code extension for developing AI solutions
  B. An AI tool designed to replace software developers
  C. An AI pair programmer that offers autocomplete-style suggestions
  D. An advanced search tool to intelligently reuse existing code in your projects
  C. An AI pair programmer that offers autocomplete-style suggestions

  ---

  Explanation

  GitHub Copilot is described as an AI pair programmer that offers autocomplete-style suggestions. It is a tool integrated into development environments like Visual Studio Code that helps developers by providing code suggestions as they type. Copilot can suggest entire lines or blocks of code based on the context of what you

• Question 17:

  What does a CODEOWNERS file do in a repository?

  A. Restricts who can edit specific files
  B. Requires peer code review for code changes
  C. Defines access permissions for the repository
  D. Sets the reviewers for pull requests automatically
  D. Sets the reviewers for pull requests automatically

  ---

  Explanation

  The CODEOWNERS file in a GitHub repository is used to define individuals or teams that are responsible for specific parts of the codebase. When changes are made to files or directories that match the patterns specified in the

  CODEOWNERS file, GitHub automatically requests reviews from the listed code owners.

  Setting Reviewers Automatically:

  Option D is correct because the primary purpose of a CODEOWNERS file is to automatically set reviewers for pull requests that affect the specified files or directories. This ensures that the appropriate team members are notified and review

  the changes before they are merged.

  Incorrect Options:

  Option A is incorrect because the CODEOWNERS file does not restrict who can edit specific files; it only influences who is required to review changes. Option B is partially related but not fully accurate because while CODEOWNERS does

  require certain reviews, it does not mandate peer review for all code changes.

  Option C is incorrect because the CODEOWNERS file does not define access permissions for the repository; it deals with code review processes.

  References:

  GitHub Docs: About CODEOWNERS

  GitHub Blog: Automatically Requesting Reviews with CODEOWNERS

• Question 18:

  The difference between GitHub Desktop and github.com is that Desktop:

  A. Is a standalone software application.
  B. Enables integration with office suite applications.
  C. Is only available on Windows operating systems.
  D. Offers a graphical user interface.
  E. Is a self-hosted version of GitHub.
  D. Offers a graphical user interface.

  ---

  Explanation

  GitHub Desktop is a standalone application that provides a graphical user interface (GUI) for interacting with GitHub repositories, as opposed to the command-line or web-based interfaces available on github.com.

  Graphical User Interface:

  Option D is correct because GitHub Desktop offers a GUI, making it easier for users to manage repositories, perform commits, and handle other Git-related tasks without needing to use the command line.

  Incorrect Options:

  Option A is partially correct in that GitHub Desktop is a standalone application, but the key difference is the GUI.

  Option B is incorrect because GitHub Desktop does not specifically enable integration with office suite applications.

  Option C is incorrect because GitHub Desktop is available on both Windows and macOS.

  Option E is incorrect because GitHub Desktop is not a self-hosted version of GitHub; it is a client application for accessing GitHub repositories.

  References:

  GitHub Docs: GitHub Desktop Documentation

• Question 19:

  What are primary benefits of using GitHub issues templates? (Each answer presents a complete solution. 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 easily coerce existing issues into a standard format
  D. To automatically create new branches when issues are created
  A. To automatically label or assign newly created issues
  B. To provide an easy-to-fill-out form for creating new issues

  ---

  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.

• Question 20:

  Which of the following items can you customize for an individual Codespace? (Each answer presents a complete solution. Choose three.)

  A. Shell
  B. Branch protections
  C. Name
  D. Default editor
  E. Operating system
  A. Shell
  C. Name
  D. Default editor

  ---

  Explanation

  When using GitHub Codespaces, you can customize several aspects of the development environment:

  Shell: You can choose the default shell to be used in the Codespace, such as Bash, Zsh, or PowerShell.

  Name: Users can customize the name of their Codespace for easier identification.

  Default editor: You can choose which editor to use within the Codespace, such as Visual Studio Code or others that may be supported. Branch protections and the operating system are not customizable for an individual Codespace within

  GitHub, making the options Shell, Name, and Default editor the correct answers.