Free Practice Questions for Microsoft GH-900 Exam

In GitHub, labels are used to categorize issues and pull requests, and certain default labels are provided to help manage tasks:

Help Wanted Label:

Option C is correct. The " Help wanted " label is used to indicate that the maintainer of the repository needs assistance on a particular issue or pull request. This label helps in attracting contributors who might be interested in helping with specific tasks.

Other Options:

Option A ( " Enhancement " ) is incorrect because it indicates a request for a new feature or improvement rather than a call for help.

Option B ( " Question " ) is incorrect because it is used to flag issues or pull requests that seek clarification or additional information, not necessarily requiring assistance.

Option D ( " Documentation " ) is incorrect because it labels issues or PRs related to documentation, not for seeking help.

A pull request tracks changes from a compare branch into a base branch. After a pull request is opened, additional commits pushed to the same compare branch are automatically included in that pull request. Reviewers can see those new commits under the Commits tab and examine updated file differences under the Files changed tab. GitHub also records commit activity in the pull request timeline so collaborators can follow what changed during the review process. The pull request does not need to be reopened, because it remains connected to the branch. The base branch is not automatically updated by these commits; the new commits are on the source branch until the pull request is merged. This behavior supports iterative review and collaboration.

Organization owners on GitHub have control over how GitHub Actions can be used within their organization. They can enforce restrictions to ensure security and compliance with organizational policies.

Allow Actions That Use Self-Hosted Runners:

Option A is correct because organization owners can configure the usage of self-hosted runners, allowing greater control over the environment where actions are run.

Allow Specified Actions:

Option C is correct because organization owners can allow only specific actions to run, adding a layer of security by limiting actions to those that have been vetted.

Allow Actions by Marketplace Verified Creators:

Option D is correct because organization owners can choose to allow actions created by GitHub Marketplace verified creators, ensuring that only trusted actions are used.

Incorrect Options:

Option B is incorrect because GitHub Actions are not designed to be run directly from a Codespace; Codespaces are for development environments.

Option E is a valid choice, but since the prompt asks for only three answers, it is not included in this response.

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 personal account is the GitHub account type designed for an individual user. It represents that person’s identity on GitHub.com and is used to create repositories, contribute to projects, open issues, review pull requests, follow other users, and participate in discussions. A personal account can also be invited to organizations or teams, but it remains the user’s individual identity. Organization accounts are shared spaces for groups, companies, or communities to manage repositories and members. Enterprise accounts are used to manage multiple organizations at a larger business level. “Team account” is not a primary GitHub account type; teams exist inside organizations to manage permissions and collaboration. For a single user identity, the correct account type is a personal account.

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.