Microsoft GH-900 Practice Exam Questions & Answers

Explanation

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.

Explanation

GitHub is a cloud-based platform that provides hosting for software development and version control using Git. It offers tools for collaboration, project management, and security to create a safe and productive environment for developers.

GitHub Overview:

Option B is correct because GitHub is primarily known as a cloud-based hosting service for Git repositories, offering a collaborative environment where developers can work together on projects, manage version control, and implement security practices.

Incorrect Options:

Option A is incorrect because GitHub is not proprietary in the sense of being closed off from version control standards; it is widely recognized as an open platform for collaboration.

Option C is incorrect because, while GitHub is accessible to new developers, it is designed for developers of all skill levels and not specifically tailored for beginners.

Option D is incorrect because GitHub is not a centralized version control system; it supports Git, which is distributed.

GitHub Docs: About GitHub

Explanation

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.

Explanation

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.

GitHub Docs: Events That Trigger Workflows

Explanation When an organization sets base permissions to 'No permissions,' users have no default access. However, members within that same organization can see internal repositories because organizational membership grants them visibility. Members from other organizations in the enterprise can also see internal repositories because enterprise members have the ability to view internal repos across the organization. Users outside the enterprise or those not part of any organization would be blocked. This setting prevents external access while allowing internal organizational transparency.