Microsoft GH-900 GitHub Foundations Exam Practice Test

As mentioned in the answer to Question no. 66, GitHub Actions workflows can reference actions from a variety of sources:

Any Public Repository:

Option A is correct. Actions can be sourced from any public GitHub repository.

The Same Repository as Your Workflow File:

Option B is correct. Actions within the same repository as the workflow file can be referenced directly.

A Published Docker Container Image on Docker Hub:

Option E is correct. Workflows can also use actions provided as Docker container images from Docker Hub.

Incorrect Options:

Option C and D are not relevant for directly referencing actions in workflows.

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.

GitHub Mobile provides a streamlined experience for managing your GitHub notifications and participating in discussions, but it does not offer full functionality compared to the desktop or web interface.

Managing Notifications:

Option E is correct because GitHub Mobile allows users to manage notifications, keeping them up to date with their repositories, issues, pull requests, and other activities on GitHub.

Incorrect Options:

Option A is incorrect because GitHub Mobile cannot be used as a self-hosted runner.

Option B is incorrect because managing enterprise and organization settings is not supported in GitHub Mobile.

Option C is incorrect because GitHub Mobile does not offer a chat or voice calling feature.

Option D is incorrect because forking and cloning repositories are not actions available in GitHub Mobile.

GitHub provides several pre-defined repository roles that determine the level of access and permissions a user has within a repository. The roles that are included by default are:

Triage : Allows users to manage issues and pull requests without write access to the code.

Maintain : Provides more extensive access, including managing settings, but without full administrative control.

Write : Grants permission to push changes and manage issues and pull requests.

Roles like " Security " and " Delete " are not standard pre-defined roles, and " View " is generally referred to as " Read " in GitHub ' s permission structure.

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

After 30 minutes of inactivity, a GitHub Codespace will time out . This is designed to conserve resources when the Codespace is not being actively used. The session will be paused, and you ' ll need to reconnect to resume your work. However, the Codespace is not deleted, and any unsaved changes might not be lost but should be committed or saved to prevent data loss.

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

In GitHub, an organization member is a user who has been added to an organization and is subject to the organization ' s base permissions and policies. An outside collaborator is a user who is not a member of the organization but has been granted access to one or more repositories within the organization.

Here’s the difference between an organization member and an outside collaborator:

Organization Members :

Members are subject to the organization ' s base permissions, which apply across all repositories within the organization. These permissions might include read, write, or admin access, depending on what has been set as the default.

Members consume paid licenses if the organization is on a paid plan.

Members are required to have two-factor authentication (2FA) if the organization enforces it.

Outside Collaborators :

Outside collaborators do not have organization-wide permissions. They only have access to specific repositories to which they have been granted permission. This means organization base permissions do not apply to them (making option A correct).

Outside collaborators do not consume paid licenses. They are only counted toward the license if they are made organization members.

Outside collaborators can be granted any level of permission, including the admin role on specific repositories.

Two-factor authentication (2FA) can be enforced for outside collaborators at the repository level, depending on the organization ' s security settings.

Given this information, option A is the correct answer: " Organization base permissions do not apply to outside collaborators. "

To contribute to a GitHub repository, a user typically needs to be able to create branches, push changes, and open pull requests. These actions require Write access, which is the minimum level of access needed to contribute code directly to a repository.

Write Access:

Option D is correct because " Write " access allows users to contribute to the repository by pushing changes, creating branches, and opening pull requests. This is the minimum required access level for contributing code.

Incorrect Options:

Option A (Read) is incorrect because " Read " access only allows viewing the repository, not making changes.

Option B (Triage) is incorrect because while Triage access allows managing issues and pull requests, it does not allow pushing code.

Option C (Maintain) is incorrect because " Maintain " access includes additional permissions beyond those needed for basic contributions, such as managing repository settings.

Markdown is a lightweight markup language with plain-text formatting syntax. It is designed to be easy to write and read in its raw form, and it can be converted into HTML and other formats. Markdown is commonly used for formatting readme files, writing messages in online discussion forums, and creating rich text documents.

Markup Language:

Option A is correct because Markdown is indeed a markup language. It is not a programming language, scripting language, version control system, or containerization solution.

Incorrect Options:

Option B is incorrect because Markdown is not a programming language; it does not involve control structures or variables.

Option C is incorrect because Markdown is not used for scripting or automation.

Option D is incorrect because Markdown does not manage version control.

Option E is incorrect because Markdown is not related to containerization technologies like Docker.

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 .

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 Teams, as part of GitHub’s paid plans, offers additional features and capabilities compared to GitHub Free, particularly for organizations.

GitHub Teams Benefits:

Option B is correct because GitHub Teams provides advanced security features like SAML single sign-on for secure authentication, as well as increased minutes for running GitHub Actions, which are essential for continuous integration and deployment workflows.

Incorrect Options:

Option A is incorrect because private repositories and advanced tools are features available, but the key differentiator in this context is the SAML SSO and additional GitHub Actions minutes.

Option C is incorrect because while expanded storage and priority support are valuable, SAML SSO and increased GitHub Actions minutes are more central to the differences between GitHub Free and GitHub Teams.

Option D is partially correct, but since the question asks for the best reason, Option B provides the most critical features that differentiate GitHub Teams from GitHub Free.

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 Pages is a feature provided by GitHub that allows you to create webpages hosted and published through GitHub repositories . It is commonly used for hosting project documentation, personal websites, or blogs directly from a GitHub repository. It integrates seamlessly with the repository, making it easy to deploy and manage website content.

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

As a GitHub user, you can configure two-factor authentication (2FA) to secure your account by navigating to Settings - > Password and Authentication - > 2FA . This section in the GitHub user interface allows you to set up and manage your 2FA methods, which provide an additional layer of security beyond just your password.

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

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 .

It is recommended to deploy from your feature branch before merging into the main branch to ensure the changes are verified and validated in a production environment . This practice helps in identifying any potential issues or bugs in a real-world scenario before the changes are permanently integrated into the main branch. By deploying from the feature branch, developers can catch and address issues early, reducing the risk of introducing bugs into the main branch, which is usually considered the stable branch.

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

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 using GitHub Codespaces, you can customize several aspects of the development environment:

Shell : You can choose the default shell to be used in the Codespace, such as Bash, Zsh, or PowerShell.

Name : Users can customize the name of their Codespace for easier identification.

Default editor : You can choose which editor to use within the Codespace, such as Visual Studio Code or others that may be supported.

Branch protections and the operating system are not customizable for an individual Codespace within GitHub, making the options Shell, Name, and Default editor the correct answers.

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

A distributed version control system (DVCS) like Git is best described as a system that ensures each developer has their own local copy of the entire code repository, including the complete project history and metadata . This decentralized approach allows developers to work independently, with full access to the project ' s history and files, and later synchronize their changes with others. Unlike centralized systems, DVCS does not rely on a single central server, which provides greater flexibility and robustness in collaboration.

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

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.

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.