Practice Free GitHub Foundations Exam Online Questions
Question #11
When using Organizations, GitHub Teams is better than GitHub Free because it offers:
- A . Advanced tools and insights in private repositories.
- B . Authentication with SAML single sign-on and increased GitHub Actions minutes.
- C . Expanded storage and priority support.
- D . Increased GitHub Actions minutes and additional GitHub Packages storage.
Correct Answer: B
B
Explanation:
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.
Reference: GitHub Docs: About GitHub Teams
B
Explanation:
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.
Reference: GitHub Docs: About GitHub Teams
Question #12
New open source contributors can receive funding from GitHub sponsors:
- A . Using PayPal as a payment processor.
- B . Equal to 95% of the contribution value.
- C . By including GitHub matching funds.
- D . After setting up a sponsored developer profile.
Correct Answer: D
D
Explanation:
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
D
Explanation:
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
Question #13
How can a user highlight a post to the top of the Discussions page?
- A . Pin the discussion.
- B . Create an issue from the discussion.
- C . Star the discussion.
- D . Save the discussion.
Correct Answer: A
Question #14
An employee needs to find all issues within organization “Avocado" containing text "404 error" and a "guacamole" label.
Which of the following steps would be best to search for these results?
- A . Enter query org:Avocado is:issue label:guacamole "404 error" in the search bar.
- B . Go to "Avocado" organization. Select Issues under a repository. Filter issues with a "guacamole" label.
- C . Enter query org:Avocado label:guacamole "404 error" in the search bar. Select "Issues" in the Filter by section.
- D . Go to the Avocado organization settings. Select Repository defaults under Repository. Scroll to Repository labels and select the ‘guacamole’ label.
Correct Answer: A
A
Explanation:
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.
Reference: GitHub Docs: Searching Issues and Pull Requests
A
Explanation:
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.
Reference: GitHub Docs: Searching Issues and Pull Requests
Question #15
As a GitHub user, where in the UI can you configure two-factor authentication (2FA) to further secure your account?
- A . Profile -> Account -> 2FA
- B . Repository Settings -> Secrets and Variables -> 2FA
- C . Organization Settings -> Authentication Security -> 2FA
- D . Settings -> Password and Authentication -> 2FA
Correct Answer: D
D
Explanation:
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.
D
Explanation:
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.
Question #16
Which of the following statements most accurately describes who can access a private repository Wiki?
- A . Wikis are only viewable by repository admins.
- B . Wikis can be viewed by the same people who have Read access to the repository.
- C . Wikis will not be visible until shared with a specific user.
- D . Wikis are public regardless of whether you have access to the repository.
Correct Answer: B
B
Explanation:
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.
B
Explanation:
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.
Question #17
Where can you go to discover, browse, and install tools?
- A . GitHub Marketplace
- B . GitHub Apps
- C . Organization settings
- D . Explore
Correct Answer: A
A
Explanation:
The GitHub Marketplace is the place where users can discover, browse, and install various tools and integrations that extend the functionality of GitHub. These tools can include CI/CD services, security checks, and other development utilities that enhance workflow automation and project management.
A
Explanation:
The GitHub Marketplace is the place where users can discover, browse, and install various tools and integrations that extend the functionality of GitHub. These tools can include CI/CD services, security checks, and other development utilities that enhance workflow automation and project management.
Question #18
While maintaining the gist history, which of the following is the most efficient way to create a public gist based on another user’s gist?
- A . Fork the gist.
- B . Create a new gist and copy the content from the existing gist.
- C . Clone the gist.
- D . Request to be added to the existing gist.
Correct Answer: A
A
Explanation:
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.
Reference: GitHub Docs: Forking Gists
A
Explanation:
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.
Reference: GitHub Docs: Forking Gists
Question #19
Which of the following is an Innersource development practice?
- A . Adopting open source code into the organization
- B . Sharing code between teams within the organization
- C . Removing open source code from the organization
- D . Making all repositories publicly accessible
Correct Answer: B
B
Explanation:
Innersource is a development practice where an organization adopts open-source development methodologies within its own internal environment. The primary goal of innersource is to break down silos and encourage collaboration across different teams within the organization.
Sharing Code Between Teams:
Option B is correct because innersource involves sharing code between teams within the organization, similar to how open-source communities share code across the public domain. This practice fosters collaboration, improves code quality, and allows for reuse of code, reducing duplication of efforts.
Incorrect Options:
Option A is incorrect because adopting open-source code into the organization is related to using open-source software, not specifically to innersource practices.
Option C is incorrect because removing open-source code from the organization is contrary to the principles of both open source and innersource.
Option D is incorrect because making all repositories publicly accessible refers to open source, not innersource. Innersource typically involves keeping code internal to the organization.
Reference: GitHub Docs: What is Innersource?
Innersource Commons: The Basics
B
Explanation:
Innersource is a development practice where an organization adopts open-source development methodologies within its own internal environment. The primary goal of innersource is to break down silos and encourage collaboration across different teams within the organization.
Sharing Code Between Teams:
Option B is correct because innersource involves sharing code between teams within the organization, similar to how open-source communities share code across the public domain. This practice fosters collaboration, improves code quality, and allows for reuse of code, reducing duplication of efforts.
Incorrect Options:
Option A is incorrect because adopting open-source code into the organization is related to using open-source software, not specifically to innersource practices.
Option C is incorrect because removing open-source code from the organization is contrary to the principles of both open source and innersource.
Option D is incorrect because making all repositories publicly accessible refers to open source, not innersource. Innersource typically involves keeping code internal to the organization.
Reference: GitHub Docs: What is Innersource?
Innersource Commons: The Basics
Question #20
Which of the following steps are part of the Codespaces lifecycle? (Each answer presents a complete solution. Choose three.)
- A . Commit
- B . Clone
- C . Rebuild
- D . Rollback
- E . Delete
- F . Create
- G . Install
Correct Answer: C, E, F
C, E, F
Explanation:
The Codespaces lifecycle on GitHub includes several key steps:
Create: This is the step where a new Codespace is initiated.
Rebuild: A Codespace can be rebuilt to ensure that the environment is up-to-date with the latest code or configurations.
Delete: Once a Codespace is no longer needed, it can be deleted to free up resources.
Committing, cloning, or installing are typical Git operations but are not considered part of the specific lifecycle steps for a GitHub Codespace.
C, E, F
Explanation:
The Codespaces lifecycle on GitHub includes several key steps:
Create: This is the step where a new Codespace is initiated.
Rebuild: A Codespace can be rebuilt to ensure that the environment is up-to-date with the latest code or configurations.
Delete: Once a Codespace is no longer needed, it can be deleted to free up resources.
Committing, cloning, or installing are typical Git operations but are not considered part of the specific lifecycle steps for a GitHub Codespace.