GH-900 Sample Questions Answers

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.

In GitHub, when viewing the list of projects for an organization, a user can identify a GitHub Projects template by selecting the Templates tab. This tab specifically lists available templates that can be used to create new projects based on predefined structures and workflows.

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

The primary benefits of using GitHub issues templates include:

A. To automatically label or assign newly created issues : Issue templates can be configured to automatically apply labels or assign users when the issue is created, helping to streamline triage and management processes.

B. To provide an easy-to-fill-out form for creating new issues : Templates provide a standardized format for submitting issues, ensuring that all necessary information is captured and reducing the need for follow-up questions.

Coercing existing issues into a standard format or automatically creating new branches when issues are created are not functions provided by GitHub issues templates.

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

GitHub provides a powerful search syntax to filter and find specific issues across repositories in an organization.

Search Query Syntax:

Option A is correct because the query org:Avocado is:issue label:guacamole " 404 error " is the best way to search for all issues within the " Avocado " organization that contain the text " 404 error " and are labeled with " guacamole " . This query is precise and leverages GitHub’s advanced search capabilities.

Incorrect Options:

Option B is incorrect because it requires manual filtering in a specific repository rather than searching across the entire organization.

Option C is incorrect because selecting " Issues " in the filter by section is redundant when using the query is:issue .

Option D is incorrect because accessing organization settings to look for repository labels is not relevant to searching for issues.

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.

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.

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

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.

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

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 Secret Scanning helps protect repositories by detecting committed credentials and other sensitive values that should not be exposed in source code. SSH private keys are sensitive because they can allow unauthorized access to servers or repositories. API keys are also critical because they can grant access to external services, cloud platforms, or applications. Database connection strings may expose usernames, passwords, hosts, or database endpoints, making them dangerous if leaked. Secret Scanning is designed to identify these kinds of credential patterns and alert repository maintainers or security teams. Hardcoded email addresses are usually not treated as secrets, and code formatting issues are handled by linters or code quality tools, not Secret Scanning.

Linking an issue to a pull request connects planned or reported work with the code change intended to resolve it. In GitHub workflows, this relationship helps maintainers track which pull request addresses a specific issue. When a pull request is linked in a way that closes the issue, such as through supported closing keywords or the development relationship, GitHub can automatically close the issue after the pull request is merged. This improves traceability and reduces manual cleanup after work is completed. Linking does not approve the pull request, because approval depends on review permissions and branch protection settings. It also does not lock the issue or automatically add the pull request to a project board. The main benefit is connecting work items to code changes.

Pull requests (PRs) on GitHub can have several statuses that indicate their current state in the development and review process:

Draft:

Option A is correct. A pull request can be in a " Draft " status, indicating that it is a work in progress and not yet ready for review.

Closed:

Option B is correct. A pull request can be " Closed " without being merged, which might happen if the proposed changes are not needed or are incorporated differently.

Merged:

Option D is correct. A pull request that has been reviewed and approved can be " Merged " into the target branch, indicating that the changes have been successfully incorporated.

Open:

Option F is correct. An " Open " pull request is one that is active and awaiting review or further action.

Incorrect Options:

Option C (Rebasing) is incorrect because " Rebasing " is not a status; it ' s an operation that can be performed on branches.

Option E (Modified) is incorrect because there is no " Modified " status for pull requests.

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

The qualifier mentions: is used in GitHub ' s search functionality to find issues that mention a certain user. For example, if you want to find all issues where a specific user is mentioned, you would use mentions:username . This helps in tracking where a user has been involved in discussions across issues or pull requests.

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

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

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

Saved replies in GitHub are a feature that allows users to create and save templates of commonly used responses for issues and pull requests. This feature can significantly enhance productivity and ensure consistent communication.

Saved Replies Are Tied to a User ' s Personal Account:

Option A is correct because saved replies are specific to a user ' s GitHub account, meaning they are accessible to the user across all repositories they have access to.

Saved Replies Allow Reusable Responses:

Option C is correct because the primary purpose of saved replies is to allow users to create reusable responses for issues and pull requests, saving time and ensuring consistency.

Incorrect Options:

Option B is incorrect because saved replies are not allocated at the enterprise level; they are specific to individual user accounts.

Option D is incorrect because saved replies do not send auto notifications; they are manually inserted by the user when responding to issues or pull requests.

From a discussion post on GitHub, a user can Create an issue from the discussion. This feature allows users to turn a discussion into an actionable item by creating an issue directly from the discussion thread. This is particularly useful when a conversation identifies a bug, task, or enhancement that needs to be tracked in the repository.

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

In a Git repository, a file can be in one of the following three valid states:

Committed : The file is saved in the local repository. It is part of the permanent history of the project.

Modified : The file has been changed but not yet staged or committed. It is in the working directory.

Staged : The file has been marked to be included in the next commit. It is in the staging area, ready to be committed.

These states represent the typical lifecycle of a file as it moves through the process of being edited, reviewed, and saved in Git.

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

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

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 develop ment. 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 supports special closing keywords that connect a pull request to an issue and automatically close the issue when the pull request is merged into the default branch. Examples include keywords such as “fixes,” “closes,” or “resolves,” followed by the issue number. Using a reference like Fixes #42 in the pull request description tells GitHub that the pull request resolves that issue. Assigning the issue to the pull request author does not create automatic closure behavior. Mentioning the issue after merging may create a reference, but it does not automatically close the issue retroactively. Adding the issue number to the pull request title may help humans understand the relationship, but the supported automatic closing behavior depends on the keyword reference.

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

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.

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.

Organization owners on GitHub have control over how GitHub Actions can be used within their organization. They can enforce restrictions to ensure security and compliance with organizational policies.

Allow Actions That Use Self-Hosted Runners:

Option A is correct because organization owners can configure the usage of self-hosted runners, allowing greater control over the environment where actions are run.

Allow Specified Actions:

Option C is correct because organization owners can allow only specific actions to run, adding a layer of security by limiting actions to those that have been vetted.

Allow Actions by Marketplace Verified Creators:

Option D is correct because organization owners can choose to allow actions created by GitHub Marketplace verified creators, ensuring that only trusted actions are used.

Incorrect Options:

Option B is incorrect because GitHub Actions are not designed to be run directly from a Codespace; Codespaces are for development environments.

Option E is a valid choice, but since the prompt asks for only three answers, it is not included in this response.

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.

InnerSource applies open source collaboration practices inside an organization while keeping the work internal. Its primary goal is to make company projects more visible to employees and reduce friction when teams contribute across boundaries. Instead of every team working in isolation, InnerSource encourages shared ownership, discoverable repositories, clear contribution guidelines, issues, pull requests, and code reviews. This helps employees reuse existing solutions, avoid duplicated work, and collaborate more efficiently. Unlike open source, InnerSource does not require making repositories public or accepting outside contributors. It also does not remove the need for pull requests; pull requests are often central to the contribution process. The key difference is that InnerSource focuses on internal collaboration using open source-style practices.

Forking a gist is the most efficient way to create a public gist based on another user ' s gist while maintaining the history of the original gist. When you fork a gist, you create a new gist in your own account that retains a link to the original, allowing you to track changes and contribute back if desired.

Forking a Gist:

Option A is correct because forking is a straightforward way to create your own copy of another user ' s gist while preserving the history and making it easy to track updates.

Incorrect Options:

Option B is incorrect because creating a new gist and copying the content would not preserve the history or link back to the original gist.

Option C is incorrect because cloning is typically associated with repositories, not gists, and is more complex than forking for this purpose.

Option D is incorrect because requesting to be added to the existing gist is not a standard GitHub feature.

A pull request compares changes from one branch into another branch. The compare branch contains the proposed changes, while the base branch is the branch those changes are intended to merge into. A pull request also includes a description where the author explains what changed, why the change is needed, and any related issue or testing information. Repository visibility settings are not part of an individual pull request. Visibility settings belong to the repository configuration and determine whether the repository is public, private, or internal, depending on the account type and plan. Since pull requests focus on proposing, reviewing, discussing, and merging branch changes, the compare branch, base branch, and description are pull request components, while repository visibility settings are not.

Repository insights provide maintainers with visual and analytical information about repository activity and health. Pull request activity can be reviewed to understand collaboration patterns, review activity, and changes over time. Contributions over time are also available through repository insights, helping maintainers see how actively people are contributing to the project. Security vulnerabilities in dependencies can be surfaced through security-related views such as dependency alerts and related repository security information. Team synchronization status and repository visibility settings are administrative or configuration-related items, not repository insight metrics. Issue resolution rates may be useful in project reporting, but it is not one of the selected repository insights metrics in this question. These insights help teams monitor repository progress, collaboration, and risk.

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 inter face allows you to set up and manage your 2FA methods, which provide an additional layer of security beyond just your password.

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