Free Microsoft GH-900 Practice Exam with Questions & Answers | Set: 4

On GitHub, you can choose to receive ongoing updates about specific activities by subscribing to notifications for all activity in a repository. This allows you to stay informed about all changes, discussions, and updates related to a particular project. Additionally, GitHub provides the ability to customize notifications to suit your preferences.

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

A centralized version control system stores the main project history in one central location, usually a server. Developers connect to that server to check out files, make changes, and submit updates. This differs from Git, which is distributed and allows every developer to have a full local copy of the repository history. In a centralized model, collaboration depends heavily on the availability of the central server. If the server is unavailable, developers may be limited in what they can do. GitHub Foundations emphasizes this distinction because GitHub is built around Git, a distributed version control system. Option C correctly describes centralized version control because the central server holds the authoritative project history.

A gist on GitHub is essentially a Git repository, albeit a simplified one, designed for sharing snippets of code, notes, or other text content. Gists support version control and can be public or secret.

Gist as a Git Repository:

Option B is correct because each gist is a Git repository, meaning you can clone it, commit changes, and even fork it, just like any other Git repository.

Incorrect Options:

Option A is incorrect because a gist is not an app; it’s a feature of GitHub that provides a simplified repository.

Option C is incorrect because while a gist may contain Markdown documents, it is fundamentally a repository that can hold various file types.

Option D is incorrect because GitHub Pages is a separate service for hosting websites, not related to gists.

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.

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

Milestones in GitHub help teams group related issues and pull requests around a shared goal, release, sprint, or deadline. They provide a progress-tracking mechanism by showing which linked items are open and which are complete. For example, a team may create a milestone for a product release and attach all required bugs, features, and documentation tasks to it. This gives maintainers a clear view of progress toward that larger objective. Custom fields are part of GitHub Projects, but they are not the main purpose of milestones. Charts belong to insights and reporting features, while automation is usually handled with GitHub Actions or project workflows. Milestones are mainly for organizing and tracking related work.