Pass the Microsoft GitHub Administrator GH-900 Questions and answers with CertsForce

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.

On GitHub, certain actions automatically subscribe you to conversations so that you receive notifications about further activity in that thread.

Opening a Pull Request or Issue:

Option C is correct because when you open a pull request or issue, you are automatically subscribed to the conversation and will receive notifications for any updates.

Commenting on a Thread:

Option D is correct because commenting on an issue or pull request automatically subscribes you to that thread, ensuring you are notified of further comments or changes.

Being Assigned to an Issue or Pull Request:

Option E is correct because when you are assigned to an issue or pull request, you are automatically subscribed to notifications related to it.

Incorrect Options:

Option A is incorrect because pushing a commit to the default branch does not automatically subscribe you to conversations.

Option B is incorrect because being added as a repo admin does not automatically subscribe you to specific conversations unless you engage with them.

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.

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

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.

GitHub Projects is a newer, more powerful version of project management within GitHub, offering enhanced features over the classic version.

Multiple Layout Views:

Option A is correct because GitHub Projects supports multiple views, such as board, table, and timeline views, allowing users to visualize their work in different ways according to their needs.

Insights:

Option B is correct because GitHub Projects provides insights and analytics, enabling teams to track progress and make data-driven decisions.

Incorrect Options:

Option C is incorrect because while GitHub Copilot is a tool for code suggestions, it is not directly integrated with GitHub Projects as a feature.

Option D is incorrect because both GitHub Projects and GitHub Projects Classic can be connected to third-party tools, so it is not an exclusive advantage of the newer GitHub Projects.

Pull requests (PRs) on GitHub can have several statuses that indicate their current state in the development and review process:

Draft:

Option A is correct. A pull request can be in a " Draft " status, indicating that it is a work in progress and not yet ready for review.

Closed:

Option B is correct. A pull request can be " Closed " without being merged, which might happen if the proposed changes are not needed or are incorporated differently.

Merged:

Option D is correct. A pull request that has been reviewed and approved can be " Merged " into the target branch, indicating that the changes have been successfully incorporated.

Open:

Option F is correct. An " Open " pull request is one that is active and awaiting review or further action.

Incorrect Options:

Option C (Rebasing) is incorrect because " Rebasing " is not a status; it ' s an operation that can be performed on branches.

Option E (Modified) is incorrect because there is no " Modified " status for pull requests.

A pull request compares changes from one branch into another branch. The compare branch contains the proposed changes, while the base branch is the branch those changes are intended to merge into. A pull request also includes a description where the author explains what changed, why the change is needed, and any related issue or testing information. Repository visibility settings are not part of an individual pull request. Visibility settings belong to the repository configuration and determine whether the repository is public, private, or internal, depending on the account type and plan. Since pull requests focus on proposing, reviewing, discussing, and merging branch changes, the compare branch, base branch, and description are pull request components, while repository visibility settings are not.