GitHub Foundations (GH-900) · 10% practice allocation

GitHub GH-900: Explore the GitHub Community Practice Questions

5 free sample questions from the Explore the GitHub Community domain, with answers and explanations. The full GH-900 bank has 150 questions across 7 domains. Questions are scenario-based and written from the official GitHub exam guide.

A large enterprise wants its internal teams to share reusable code across business units the way open-source communities do — transparent repositories, pull requests from any internal team, and public-style documentation — while keeping all code inside the company. What is this practice called?

A. Federated governance
B. Open core licensing
C. InnerSource✓ Correct
D. Forking policy

Explanation

InnerSource is the practice of applying open-source collaboration principles (transparency, shared ownership, contribution via pull request, good documentation) to work inside an organization, commonly implemented with internal repositories. Open core is a business model where a core product is open source and extras are commercial. A forking policy is only one narrow governance rule, not the overall practice. Federated governance is a general organizational-design term, not the GitHub-recognized term for this collaboration model.

A platform team publishes a repository containing a standard service skeleton: CI workflows, linter configuration, a Dockerfile, and a docs folder. Dozens of teams need to start new services from it, and each new service must have its own clean, independent history with no upstream link. What should the platform team configure?

A. Mark the repository as a template repository✓ Correct
B. Convert the repository into a GitHub Gist
C. Publish the repository to GitHub Marketplace
D. Tell teams to fork the repository

Explanation

A template repository lets anyone generate a brand-new repository with the same files and directory structure but a fresh, single-commit history and no fork relationship. Forks preserve the upstream connection and full commit history, which is intended for contributing changes back, not for starting unrelated projects. Marketplace is for listing apps and Actions, not scaffolding repositories. Gists are for sharing snippets and cannot carry a full repository structure with workflows in a reusable template way.

On GitHub Enterprise Cloud, which repository visibility setting best supports InnerSource by making a repository readable by all members of the enterprise while keeping it hidden from the public internet?

A. Restricted
B. Public
C. Internal✓ Correct
D. Private

Explanation

Internal repositories are visible to all members of the enterprise, which is the visibility purpose-built for InnerSource. Private repositories are visible only to people explicitly granted access, which blocks the discovery that InnerSource depends on. Public repositories are visible to everyone on the internet, which violates the requirement to stay internal. "Restricted" is not a GitHub repository visibility option.

A developer wants to receive updates in their GitHub personal dashboard feed whenever a particular maintainer opens issues, creates repositories, or stars projects. Which GitHub feature should they use?

A. Star the maintainer's profile README repository
B. Add the maintainer as an outside collaborator
C. Follow the maintainer's user account✓ Correct
D. Watch every repository the maintainer owns

Explanation

Following a user surfaces their public activity (new repositories, stars, follows, and other public events) in your personal dashboard feed. Watching repositories only delivers notifications about activity inside those specific repositories, not everything the person does, and it would miss repositories they create later. Adding someone as an outside collaborator grants them access to your repository and produces no activity feed. Starring a repository is a bookmark/appreciation signal and does not follow a person's activity.

An engineering manager is evaluating whether her company should publish an internal library as open source on GitHub. Which TWO statements describe realistic, accurate benefits of open sourcing the project?

A. Publishing the code automatically transfers copyright ownership to the open-source community
B. Making the repository public guarantees that vulnerabilities cannot exist because 'many eyes' review it
C. External contributors can review the code and submit fixes, potentially improving quality and security✓ Correct
D. The project can attract adopters who become a talent and feedback pipeline for the company✓ Correct
E. GitHub automatically assumes maintenance responsibility for popular public repositories

Explanation

Open sourcing broadens the pool of reviewers and contributors, which can raise code quality and surface security issues, and a healthy user community generates adoption, feedback, and visibility that aid recruiting. GitHub does not maintain third-party repositories; maintenance always stays with the owners. Publishing code does not transfer copyright — the author retains copyright and grants rights through a license. The "many eyes" argument is a heuristic, not a guarantee; public projects still ship vulnerabilities.

Test yourself across every GH-900 domain

The free GH-900 practice test mixes about 20 questions weighted like the exam. The full 150-question bank adds instant grading, flashcards and a timed mock exam.

Take the free GH-900 practice test Practice the full bank

Study this domain

Explore the GitHub Community study guide (GH-900) →

Other GH-900 domains

← All GitHub Foundations study resources