GitHub Foundations Exam Practice Test

Answer : A, B, D, F

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 Docs: About Pull Requests

Answer : A, C, D

The following two-factor authentication (2FA) methods can be used to secure a GitHub account:

A . Authenticator app: You can use an authenticator app (like Google Authenticator or Authy) to generate time-based one-time passwords (TOTP) for logging in.

C . GitHub mobile: The GitHub mobile app can also be used to receive 2FA codes, adding convenience for users who prefer to manage everything from their mobile devices.

D . Security keys: Physical security keys (such as YubiKeys) can be used as a strong form of 2FA, requiring physical access to the key to authenticate.

Security questions and Single sign-on (SSO) are not considered 2FA methods in the context of GitHub account security.

Answer : D

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.

Answer : B

To highlight a post at the top of the Discussions page on GitHub, you can Pin the discussion. Pinning a discussion ensures it remains prominently visible at the top of the list, making it easier for others to find and participate in that discussion. This is particularly useful for important announcements or frequently referenced topics.

Answer : C

GitHub's community is centered around enabling developers to collaborate and innovate together. The platform provides tools and environments that foster open communication, sharing of ideas, and collective problem-solving.

Facilitating Collaboration and Creativity:

Option C is correct because GitHub is designed to be a collaborative platform where developers can work together on projects, share code, and contribute to open source initiatives, all in an environment that encourages creativity.

Incorrect Options:

Option A is incorrect because GitHub is inclusive of developers of all skill levels, not just experienced ones.

Option B is incorrect because GitHub is not about creating a competitive environment; rather, it focuses on collaboration.

Option D is incorrect because while code quality is important, enforcing strict code quality standards is not the primary goal of the GitHub community.

GitHub Docs: Building a Strong Community

Answer : D

GitHub Sponsors is a program designed to provide a platform for developers and companies to financially support open-source projects and their maintainers.

Financial Support for Open Source Projects:

Option D is correct because the main purpose of GitHub Sponsors is to allow members of the developer community, including individuals and organizations, to financially support open-source projects and maintainers. This helps sustain open-source development by providing developers with the resources they need to continue their work.

Incorrect Options:

Option A is incorrect because GitHub Sponsors is not based on project popularity (e.g., stars); it is based on voluntary contributions.

Option B is incorrect because while GitHub provides the platform, the purpose of GitHub Sponsors is not for GitHub itself to fund projects, but to enable the broader community to do so.

Option C is incorrect because GitHub Sponsors is not a marketplace for purchasing software but a platform for supporting developers.

GitHub Docs: GitHub Sponsors

Answer : B, C

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 Documentation: Fork a repo

GitHub Documentation: About forks