Microsoft Updated GH-900 Exam Questions and Answers by isabella-rose

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.

=================

To contribute to a GitHub repository, a user typically needs to be able to create branches, push changes, and open pull requests. These actions require Write access, which is the minimum level of access needed to contribute code directly to a repository.

Write Access:

Option D is correct because "Write" access allows users to contribute to the repository by pushing changes, creating branches, and opening pull requests. This is the minimum required access level for contributing code.

Incorrect Options:

Option A (Read) is incorrect because "Read" access only allows viewing the repository, not making changes.

Option B (Triage) is incorrect because while Triage access allows managing issues and pull requests, it does not allow pushing code.

Option C (Maintain) is incorrect because "Maintain" access includes additional permissions beyond those needed for basic contributions, such as managing repository settings.

Saved replies in GitHub are a feature that allows users to create and save templates of commonly used responses for issues and pull requests. This feature can significantly enhance productivity and ensure consistent communication.

Saved Replies Are Tied to a User's Personal Account:

Option A is correct because saved replies are specific to a user's GitHub account, meaning they are accessible to the user across all repositories they have access to.

Saved Replies Allow Reusable Responses:

Option C is correct because the primary purpose of saved replies is to allow users to create reusable responses for issues and pull requests, saving time and ensuring consistency.

Incorrect Options:

Option B is incorrect because saved replies are not allocated at the enterprise level; they are specific to individual user accounts.

Option D is incorrect because saved replies do not send auto notifications; they are manually inserted by the user when responding to issues or pull requests.

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.