Which of the following is a benefit of creating a new GitHub organization?

Question

Options

• AAutomatic inheritance of policies from other organizations.
• BReduced administrative overhead.
• CClear separation of reggs, projects, teams, billing, and organization-specific policies.
• DSimplified collaboration across all organizations.

• A
  4% (1)
• B
  4% (1)
• C
  89% (25)
• D
  4% (1)

Explanation

Creating a new GitHub organization provides clear separation of repositories, projects, teams, billing, and organization-specific policies (C) - each org is an independent administrative boundary, letting you isolate resources, access controls, and billing entirely from other organizations. This is the primary architectural reason organizations exist as a concept in GitHub.

Why the distractors are wrong:

• A is wrong because organizations do not automatically inherit policies from other organizations - each org manages its own policies independently.
• B is wrong because adding an organization actually increases administrative overhead, since you now manage another set of members, repos, settings, and billing.
• D is wrong because separate organizations create more friction for cross-org collaboration, not less - contributors need access granted explicitly in each org.

Memory tip: Think of a GitHub organization like a separate company subsidiary - it has its own budget (billing), its own employees (members), its own files (repos), and its own rules (policies). The whole point is isolation, not unification.

No community discussion yet for this question.