In GitHub, anorganization memberis a user who has been added to an organization and is subject to the organization's base permissions and policies. Anoutside collaboratoris 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." References:
* GitHub Documentation: Roles in an organization
* GitHub Documentation: About outside collaborators
* GitHub Documentation: Managing repository access for your organization

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 Ais 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 Bis incorrect because commits can be made both before and after a pull request is created.
* Option Cis incorrect because it suggests that commits can only be made before a pull request is created, which is not true.
* Option Dis 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).
References:
* GitHub Documentation: About Pull Requests
* GitHub Docs: Understanding the GitHub Flow
* Git Documentation: Git Basics - Getting a Git Repository

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 Ais correct because secret gists can be viewed by anyone who has the direct URL, making them accessible yet unlisted.
* Incorrect Options:
* Option Bis incorrect because secret gists do not require GitHub Enterprise; they are available on all GitHub accounts.
* Option Cis incorrect because secret gists do not appear on the gist Discover page.
* Option Dis incorrect because secret gists do not have an "assigned access" feature; access is determined by sharing the URL.
References:
* GitHub Docs: About Gists

For private repositories on GitHub, the Wiki is accessible to anyone who hasRead accessto 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.

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.