Practice Free GH-900 GitHub Foundations Exam Questions Answers With Explanation

In GitHub Actions workflows, actions can be referenced from various sources depending on the needs of the workflow.

Any Public Repository:

Option A is correct. Actions can be referenced from any public GitHub repository, allowing the reuse of shared actions across multiple projects.

The Same Repository as Your Workflow File:

Option B is correct. Actions stored in the same repository as the workflow file can be referenced directly, which is common for custom actions specific to that project.

A Published Docker Container Image on Docker Hub:

Option E is correct. Workflows can reference actions that are provided as Docker container images hosted on Docker Hub, allowing integration of complex tools and environments.

Incorrect Options:

Option C (GitHub Packages) is incorrect as it is more commonly used for storing and managing dependencies, not actions.

Option D (An enterprise marketplace) is incorrect because GitHub Actions are not directly referenced from an enterprise marketplace but rather from public repositories or Docker images.

A Codespace is a cloud-hosted development environment provided by GitHub. It allows developers to code in a fully-configured environment that can be accessed from any device with an internet connection. Codespaces integrate with Visual Studio Code, either through the desktop app or directly in the browser, providing a consistent development experience without the need to manually set up a local environment.

Cloud-Hosted Development Environment:

Option C is correct because GitHub Codespaces are essentially cloud-based environments that are pre-configured with the tools and dependencies needed for development. This allows developers to start coding immediately without the overhead of setting up a local environment.

Incorrect Options:

Option A is partially correct in that Codespaces can be accessed and used in a browser, but the defining feature is that it ' s a full development environment, not just a lightweight editor.

Option B is incorrect because this describes GitHub Copilot, not Codespaces.

Option D is incorrect because Codespaces is not a Visual Studio Code plug-in; it is a cloud-based service that integrates with Visual Studio Code.

GitHub provides repository admins with a feature called " Insights " where they can view various pre-built visualizations and analytics related to the repository.

Insights:

Option C is correct because the " Insights " tab in a GitHub repository offers various pre-built visualizations, including contributions, traffic, code frequency, dependency graphs, and more. This helps admins and maintainers track the project ' s activity and health.

Other Options:

Option A (Settings) is incorrect because the Settings tab is where you configure repository settings, permissions, and integrations, but it does not provide visualizations of repository data.

Option B (Issues) is incorrect because the Issues tab is used for tracking bugs, enhancements, and other tasks but does not provide data visualizations.

Option D (Charts) is incorrect as there is no " Charts " tab or section in GitHub. The correct location for data visualizations is under " Insights. "

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.

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.

Two recommended ways to improve the discoverability of a repository on GitHub are:

B. Create a README file describing the repository : A well-written README file provides essential information about the project, such as what it does, how to use it, and how to contribute. This is often the first thing potential users or contributors will see, making it critical for discoverability.

D. Add topics to classify the repository : Adding topics to your repository helps classify it under specific categories, making it easier for others to find it through GitHub’s search and exploration features. Topics act like tags, helping to connect your project with users interested in similar subjects.

Registering a repository with GitHub search and adding labels are not applicable actions for improving discoverability in the broader sense.

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

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 .

GitHub Flow is a simple, yet powerful, branching strategy that is widely used in modern software development. It emphasizes collaboration and flexibility.

GitHub Flow:

Option C is correct because GitHub Flow is a lightweight workflow designed for safe experimentation and collaboration. It involves creating branches for new fea tures or fixes, opening pull requests for review, and merging changes back into the main branch after approval.

Incorrect Options:

Option A is incorrect because GitHub Flow uses a single main branch, not multiple primary branches.

Option B is incorrect because GitHub Flow is not specifically designed around releases; it is more focused on continuous development and integration.

Option D is incorrect because GitHub Flow is not strict or linear; it encourages branching and pull requests rather than direct changes on the main branch.

On GitHub, you can choose to receive ongoing updates about specific activities by subscribing to notifications for all activity in a repository . This allows you to stay informed about all changes, discussions, and updates related to a particular project. Additionally, GitHub provides the ability to customize notifications to suit your preferences.

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

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

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

A GitHub repository serves as a collaborative space where developers can share and manage code files, track changes, and store revision history . It is much more than just a folder or simple tool; it is a comprehensive version control system that allows teams to collaborate effectively on codebases. Repositories enable developers to work together, manage contributions, review code, and maintain a complete history of every change made to the project.

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

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.

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

Secret gists on GitHub are " unlisted " gists, meaning they are not publicly discoverable but can be viewed by anyone who has the URL.

Visibility of Secret Gists:

Option A is correct because secret gists can be viewed by anyone who has the direct URL, making them accessible yet unlisted.

Incorrect Options:

Option B is incorrect because secret gists do not require GitHub Enterprise; they are available on all GitHub accounts.

Option C is incorrect because secret gists do not appear on the gist Discover page.

Option D is incorrect because secret gists do not have an " assigned access " feature; access is determined by sharing the URL.

GitHub Sponsors allows developers and organizations to financially support open-source contributors directly on the GitHub platform.

Setting Up a Sponsored Developer Profile:

Option D is correct because before a contributor can receive funding through GitHub Sponsors, they need

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

The CODEOWNERS file in a GitHub repository is used to define individuals or teams that are responsible for specific parts of the codebase. When changes are made to files or directories that match the patterns specified in the CODEOWNERS file, GitHub automatically requests reviews from the listed code owners.

Setting Reviewers Automatically:

Option D is correct because the primary purpose of a CODEOWNERS file is to automatically set reviewers for pull requests that affect the specified files or directories. This ensures that the appropriate team members are notified and review the changes before they are merged.

Incorrect Options:

Option A is incorrect because the CODEOWNERS file does not restrict who can edit specific files; it only influences who is required to review changes.

Option B is partially related but not fully accurate because while CODEOWNERS does require certain reviews, it does not mandate peer review for all code changes.

Option C is incorrect because the CODEOWNERS file does not define access permissions for the repository; it deals with code review processes.

For private repositories on GitHub, the Wiki is accessible to anyone who has Read access to the repository. This means that if you can view the code and files in the repository, you can also view its Wiki. This makes Wikis a useful tool for documenting projects in a way that is available to all collaborators without requiring special permissions beyond those needed to access the repository itself.

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