Free Microsoft GitHub Foundations GH-900 Exam Questions

Cloning a repository in GitHub refers to creating a copy of the repository on your local machine. This allows you to work on the project offline, make changes, and later push those changes back to the remote repository. It does not involve creating a copy on GitHub.com (which would be forking), retrieving updates (which would be pulling), or importing source code into a new repository (which is done differently).

The GitHub Marketplace is the place where users can discover, browse, and install various tools and integrations that extend the functionality of GitHub. These tools can include CI/CD services, security checks, and other development utilities that enhance workflow automation and project management.

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.

GitHub Docs: About Pull Requests

A user's GitHub profile typically includes public information such as a personal biography, profile picture, and a list of public repositories. More sensitive information, like email addresses and passwords, is not publicly displayed.

Personal Biography and Profile Picture:

Option A is correct because these are standard elements displayed on a user's public GitHub profile. This information is meant to provide a brief introduction to the user and their interests or skills.

Incorrect Options:

Option B is incorrect because public SSH keys may be associated with a user's account but are not displayed by default on the profile page.

Option C is incorrect because private repositories are not listed on a public profile.

Option D is incorrect because a user's email address and password are private information and not displayed on their public profile.

GitHub Docs: Managing Your Profile

When creating an issue in GitHub, the issue form captures the information needed to describe the work, bug, question, or request. The title identifies the issue in lists, search results, notifications, and project views. The description provides context, details, steps to reproduce, expected behavior, screenshots, or other supporting information. Repository visibility is configured in repository settings, not when opening an issue. Branch name and commit message are related to Git changes and commits, not issue creation. GitHub issues are designed for tracking work and discussion, so the key information belongs in the issue title and description. A clear title and useful description make it easier for maintainers and collaborators to triage, assign, prioritize, and resolve the issue efficiently.

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 Docs: Subscribing to Notifications

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.