Microsoft GH-900 Online Practice Questions and Exam Preparation

Microsoft GH-900 Online Questions & Answers

• Question 51:

  What layouts are available for GitHub Projects? (Each answer presents a complete solution. Choose three.)

  A. Roadmap
  B. Kanban
  C. Board
  D. Table
  E. Backlog
  B. Kanban
  C. Board
  D. Table

  ---

  Explanation

  GitHub Projects supports various layouts to help teams organize and visualize their work. The available layouts include:

  B. Kanban: This is a visual task management tool where tasks are represented as cards and moved across columns that represent different stages of work.

  C. Board: This layout is similar to Kanban but can be more flexible, allowing users to set up boards in various ways to suit their workflow needs.

  D. Table: The Table layout allows you to view your tasks in a spreadsheet-like format, making it easy to manage and edit large amounts of data at once.

  Roadmap and Backlog are not standard layouts provided by GitHub Projects. While these terms might be relevant in other project management contexts, GitHub Projects specifically offers Kanban, Board, and Table layouts.

• Question 52:

  What folder is the definition files stored in when creating custom issue forms?

  A. .issues
  B. .issues/ISSUE_TEMPLATE
  C. .github/ISSUE_TEMPLATE
  D. .GitHub
  C. .github/ISSUE_TEMPLATE

  ---

  Explanation

  When creating custom issue forms on GitHub, the definition files are stored in the .github /ISSUE_TEMPLATE folder. This directory is used to define issue templates and forms that help standardize the information collected when users open new issues in the repository. The .github folder is a special directory used for various repository configurations and workflows.

• Question 53:

  Pull requests can only be created between two branches that are:

  A. Authored by the same user.
  B. Authored by different users.
  C. The same.
  D. Different.
  D. Different.

  ---

  Explanation

  Pull requests are created to propose changes from one branch to another. These branches must be different; otherwise, there would be no changes to propose. Typically, pull requests are made from a feature or topic branch to a main branch (such as main or master), allowing for code review and integration before the changes are merged.

• Question 54:

  After 30 minutes of inactivity, a GitHub Codespace will:

  A. Be deleted
  B. Commit changes
  C. Restart
  D. Time out
  D. Time out

  ---

  Explanation

  After 30 minutes of inactivity, a GitHub Codespace will time out. This is designed to conserve resources when the Codespace is not being actively used. The session will be paused, and you'll need to reconnect to resume your work. However, the Codespace is not deleted, and any unsaved changes might not be lost but should be committed or saved to prevent data loss.

• Question 55:

  A distributed version control system is best described as a system that:

  A. Relies on a central server to store the entire project history and allows developers to check out files for editing.
  B. Stores project files on a cloud-based server and allows multiple developers to collaborate on the same codebase simultaneously.
  C. Ensures each developer has their own local copy of the entire code repository, including the complete project history and metadata.
  D. Requires developers to manually track and manage different versions of their files using naming conventions and manual backups.
  C. Ensures each developer has their own local copy of the entire code repository, including the complete project history and metadata.

  ---

  Explanation

  A distributed version control system (DVCS) like Git is best described as a system that ensures each developer has their own local copy of the entire code repository, including the complete project history and metadata. This decentralized approach allows developers to work independently, with full access to the project's history and files, and later synchronize their changes with others. Unlike centralized systems, DVCS does not rely on a single central server, which provides greater flexibility and robustness in collaboration.

• Question 56:

  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

  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

• Question 57:

  Which of the following is an Innersource development practice?

  A. Adopting open source code into the organization
  B. Sharing code between teams within the organization
  C. Removing open source code from the organization
  D. Making all repositories publicly accessible
  B. Sharing code between teams within the organization

  ---

  Explanation

  Innersource is a development practice where an organization adopts open-source development methodologies within its own internal environment. The primary goal of innersource is to break down silos and encourage collaboration across

  different teams within the organization.

  Sharing Code Between Teams:

  Option B is correct because innersource involves sharing code between teams within the organization, similar to how open-source communities share code across the public domain. This practice fosters collaboration, improves code quality,

  and allows for reuse of code, reducing duplication of efforts.

  Incorrect Options:

  Option A is incorrect because adopting open-source code into the organization is related to using open-source software, not specifically to innersource practices. Option C is incorrect because removing open-source code from the

  organization is contrary to the principles of both open source and innersource.

  Option D is incorrect because making all repositories publicly accessible refers to open source, not innersource. Innersource typically involves keeping code internal to the organization.

  References:

  GitHub Docs: What is Innersource?

  Innersource Commons: The Basics

• Question 58:

  Which of the following are included as pre-defined repository roles? (Each answer presents a complete solution. Choose three.)

  A. Security
  B. View
  C. Triage
  D. Maintain
  E. Delete
  F. Write
  C. Triage
  D. Maintain
  F. Write

  ---

  Explanation

  GitHub provides several pre-defined repository roles that determine the level of access and permissions a user has within a repository. The roles that are included by default are: Triage: Allows users to manage issues and pull requests

  without write access to the code. Maintain: Provides more extensive access, including managing settings, but without full administrative

  control.

  Write: Grants permission to push changes and manage issues and pull requests.

  Roles like "Security" and "Delete" are not standard pre-defined roles, and "View" is generally referred to as"Read" in GitHub's permission structure.

• Question 59:

  Which of the following two-factor authentication (2FA) methods can you use to secure a GitHub account? (Each answer presents a complete solution. Choose three.)

  A. Authenticator app
  B. Security questions
  C. GitHub mobile
  D. Security keys
  E. Single sign-on
  A. Authenticator app
  C. GitHub mobile
  D. Security keys

  ---

  Explanation

  The following two-factor authentication (2FA) methods can be used to secure a GitHub account:

  A. Authenticator app: You can use an authenticator app (like Google Authenticator or Authy) to generate time-based one-time passwords (TOTP) for logging in.

  C. GitHub mobile: The GitHub mobile app can also be used to receive 2FA codes, adding convenience for users who prefer to manage everything from their mobile devices.

  D. Security keys: Physical security keys (such as YubiKeys) can be used as a strong form of 2FA, requiring physical access to the key to authenticate. Security questions and Single sign-on (SSO) are not considered 2FA methods in the context of GitHub account security.

• Question 60:

  Where can you go to discover, browse, and install tools?

  A. GitHub Marketplace
  B. GitHub Apps
  C. Organization settings
  D. Explore
  A. GitHub Marketplace

  ---

  Explanation

  The GitHub Marketplace is the place where users can discover, browse, and install various tools and integrations that extend the functionality of GitHub. These tools can include CI/CD services, security checks, and other development utilities that enhance workflow automation and project management.