Free Practice Questions for Microsoft GH-900 Exam

GitHub Actions are automated workflows that can be triggered by various events on GitHub. Some common events that trigger workflows include pushes to a repository, creation of issues, and comments on discussion posts.

Triggering GitHub Actions:

Option D (Pushing to a GitHub repository) is correct because this is one of the most common triggers for CI/CD workflows.

Option F (Creating an Issue) is correct because issues are commonly used as triggers for workflows, such as automatically assigning a label or notifying a team.

Option A (Adding a comment to a discussion post) is correct because actions can be triggered by activity on discussion posts, including comments.

Incorrect Options:

Option B (Creating a new repository) is incorrect because this action typically does not trigger workflows within a specific repository.

Option C (Committing a change to a local git repository) is incorrect because GitHub Actions are triggered by events on the GitHub platform, not by local commits.

Option E (Disabling a GitHub runner) is incorrect because it is related to the environment where actions are executed, not a trigger for workflows.

The terms Alpha and Beta are often used in software development to describe different stages of feature testing and release.

Alpha Features:

Option A is correct because Alpha features are typically in the early stages of development and are not available to the public. They are usually tested internally or by a limited audience.

Incorrect Options:

Option B is incorrect because Alpha features are often undocumented as they are in the early development phase.

Option C is incorrect because Alpha and Beta features usually do not offer Service Level Agreements (SLAs) due to their experimental nature.

Option D is incorrect because Beta features might offer limited support, but it is not guaranteed, especially compared to fully released features.

GitHub Desktop is a graphical interface that allows users to interact with GitHub repositories. It simplifies certain Git operations without the need for command-line usage.

GitHub Desktop Capabilities:

Option C is correct because GitHub Desktop allows users to add local repositories to their GitHub account, clone repositories from GitHub to their local machine, and manage repositories effectively.

Incorrect Options:

Option A is incorrect because GitHub Desktop does not support creating or managing issues directly; this is done through the GitHub web interface.

Option B is incorrect because reviewing and approving pull requests is also managed through the GitHub web interface.

Option D is incorrect because commenting on discussions is done on the GitHub platform, not through GitHub Desktop.

Option E is incorrect because GitHub Desktop does not integrate with office suite software.

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.

In GitHub Discussions, several default categories are provided to help organize conversations within a project. One of the default categories is Show and tell. This category is designed for users to showcase their work, share progress, or discuss achievements with the community. The other options listed (Bug report, Daily check-in, Security concern) are not default categories but could be custom categories created by the repository maintainers.

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

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).

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

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 Desktop is a standalone application that provides a graphical user interface (GUI) for interacting with GitHub repositories, as opposed to the command-line or web-based interfaces available on github.com.

Graphical User Interface:

Option D is correct because GitHub Desktop offers a GUI, making it easier for users to manage repositories, perform commits, and handle other Git-related tasks without needing to use the command line.

Incorrect Options:

Option A is partially correct in that GitHub Desktop is a standalone application, but the key difference is the GUI.

Option B is incorrect because GitHub Desktop does not specifically enable integration with office suite applications.

Option C is incorrect because GitHub Desktop is available on both Windows and macOS.

Option E is incorrect because GitHub Desktop is not a self-hosted version of GitHub; it is a client application for accessing GitHub repositories.

Commits and pull requests (PRs) are fundamental concepts in Git and GitHub workflows, particularly in collaborative software development.

Commits:

Commits are individual changes or updates made to the codebase. Each commit is identified by a unique SHA-1 hash and typically includes a commit message describing the changes.

Commits are made to a specific branch in the repository. The branch could be the main branch, or more commonly, a feature branch created for specific work or a feature.

Pull Requests (PRs):

A pull request is a mechanism for developers to notify team members that a branch is ready to be merged into another branch, usually the main branch.

PRs are used to review code, discuss changes, and make improvements before the branch is merged into the target branch.

Relationship Between Commits and PRs:

Option A is correct because commits are made on a branch, and this branch can have a pull request associated with it. The pull request tracks the branch’s commits and allows for code review before merging into the target branch.

Commits can be added to the branch both before and after the pull request is created. Any new commits pushed to the branch are automatically included in the pull request.

Incorrect Options:

Option B is incorrect because commits can be made both before and after a pull request is created.

Option C is incorrect because it suggests that commits can only be made before a pull request is created, which is not true.

Option D is incorrect because commits are not made on a pull request; they are made on a branch. The pull request links a branch to another branch (e.g., feature branch to the main branch).