You are an administrator and need to enforce a policy on forking private and internal repositories. Which options are available for configuring the policy at the enterprise level? (Each answer…

Question

Options

• AAllow organization owners to administer the setting at the organization level.
• BAllow people who have access to private and internal repositories to fork these repositories.
• CAllow specific people or teams to fork private and internal repositories.
• DDisallow repository owners from administering the setting at the repository level.
• EDisallow forking of private and internal repositories.

• A
  75% (18)
• C
  17% (4)
• D
  8% (2)

Explanation

At the GitHub Enterprise level, forking policy offers exactly three configuration options: you can delegate control downward to organization owners (A), permit all users with repository access to fork (B), or completely prohibit forking (E) - these map directly to the three radio-button choices in Enterprise Settings > Policies > Forking.

Why the distractors are wrong:

• C is incorrect because granular "specific people or teams" scoping is not available at the enterprise policy level; that kind of fine-grained control doesn't exist as an enterprise-wide fork option.
• D is incorrect because enterprise policy doesn't expose a distinct setting to block repository owners from administering forking - the delegation model works at the org-owner level (as in A), not the repo-owner level.

Memory tip: Think of the three correct options as a permission dial - Full block (E), Full allow (B), or Delegate to org (A). Enterprise policy is coarse-grained by design: block everything, allow everything, or hand off the decision. Any answer describing finer granularity (specific teams, repo-level controls) is operating at the wrong layer.

No community discussion yet for this question.