Microsoft GitHub Foundations GH-900 Exam Practice Test

Answer : D

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.

Answer : C

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.

GitHub Docs: About READMEs

Answer : B

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.

Answer : C, E, F

The Codespaces lifecycle on GitHub includes several key steps:

Create: This is the step where a new Codespace is initiated.

Rebuild: A Codespace can be rebuilt to ensure that the environment is up-to-date with the latest code or configurations.

Delete: Once a Codespace is no longer needed, it can be deleted to free up resources.

Committing, cloning, or installing are typical Git operations but are not considered part of the specific lifecycle steps for a GitHub Codespace.

Answer : A, C

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.

GitHub Docs: Using Saved Replies

Answer : A

GitHub Pages is a feature provided by GitHub that allows you to create webpages hosted and published through GitHub repositories. It is commonly used for hosting project documentation, personal websites, or blogs directly from a GitHub repository. It integrates seamlessly with the repository, making it easy to deploy and manage website content.

Answer : B, C, D

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.