Free Microsoft GH-900 Practice Exam with Questions & Answers

To locate an existing GitHub Action provided by a GitHub-approved vendor, you can use the following methods:

Verification Badge:

Option C is correct because actions provided by GitHub-approved vendors will typically have a verification badge. This badge indicates that the action is from a trusted source, giving users confidence in its security and reliability.

Search the GitHub Marketplace:

Option F is correct because GitHub Marketplace is the official location to find and install actions, including those provided by third-party vendors. You can search for actions by the vendor ' s name to find the specific one you need.

Incorrect Options:

Option A is not necessary to locate an existing action; creating a workflow file is for implementing the action, not locating it.

Option B is incorrect because searching the vendor’s website for a github.yaml index is not a standard practice for finding actions.

Option D is incorrect because installing a GitHub App is unrelated to finding an existing action.

Option E is incorrect because adding a vendor as an allowed Actions Source is a configuration step for using the action, not for locating it.

When multiple README files exist in different locations within a GitHub repository, the README.md file located in the root directory of the repository will be displayed first by default. This file serves as the main documentation for the repository and is automatically rendered on the repository ' s home page.

Root Directory:

Option C is correct because the README.md file in the root directory is prioritized and displayed first on GitHub. This is the standard behavior for how GitHub presents documentation.

Incorrect Options:

Option A ( .github ) is incorrect because while a README.md file in the .github directory might be used for certain configurations, it is not the first to be displayed.

Option B ( /src ) is incorrect because the README.md in the src directory is not prioritized over the root.

Option D ( /docs ) is incorrect because documentation in the /docs folder is typically secondary to the root README.md .

Forking a repository on GitHub is a common practice, especially when contributing to open-source projects or when you want to build on existing work. Here are the two main reasons for forking a repository:

B. To propose changes to the base repository :

One of the primary reasons for forking a repository is to make changes or improvements that you can later propose to the original repository (often called the " upstream " repository). This is typically done through a pull request. By forking the repository, you get your own copy of the project where you can freely experiment, make changes, and then propose those changes back to the original project.

C. To create a new repository based on an existing one :

Forking is also used to create a new repository that is a copy of an existing one. This allows you to work on the project independently of the original repository, effectively creating a new direction for the project or using it as a starting point for a different purpose. This is particularly useful for customization, experimentation, or when you want to build something different while still leveraging the existing codebase.

Explanation of Other Options :

A. To create an issue or open a discussion :

This is incorrect because creating an issue or opening a discussion can be done directly on the original repository without needing to fork it. Forking is unnecessary for these actions.

D. To create a new branch to develop a new feature :

While creating a new branch is related to development, it does not require a fork. Branches are typically created within the same repository to work on new features. Forking is used when you need an entirely separate copy of the repository.

Given this information, the correct answers are B and C .

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.

Creating a repository template in GitHub requires specific steps and permissions:

Creating a Repository Template:

Option A is correct because a user with Admin permissions can navigate to the repository ' s settings and enable the " Template Repository " option. This allows other users to generate new repositories from this template, which includes all branches, tags, and file history.

Other Options:

Option B is incorrect because " Maintain " permissions do not allow the creation of repository templates, and the option is not found in Organization settings but in the repository settings.

Option C is incorrect because the " Template Repository " option is in the repository settings, not in Organization settings.

Option D is incorrect because " Maintain " permissions do not grant the ability to create a repository template.

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.

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.

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