Your enterprise has multiple organizations, and you want to ensure consistent security policies across all teams. Which feature should you use?

Question

Options

• AOutside collaborators for all repositories.
• BOrganization-specific teams with custom policies.
• CEnterprise-level teams with inherited enterprise policies.
• DAssigning admin permissions to all team members.

• A
  4% (1)
• B
  4% (1)
• C
  92% (22)

Explanation

Enterprise-level teams with inherited enterprise policies (C) is correct because they allow administrators to define security policies once at the enterprise level, which then cascade down to all organizations and repositories automatically - ensuring consistency without per-team configuration.

Why the distractors fail:

• A (Outside collaborators) - this controls external access to repositories, not policy consistency across internal teams.
• B (Organization-specific teams with custom policies) - custom per-org policies create inconsistency by definition; each org can diverge from others.
• D (Admin permissions for all members) - granting everyone admin rights is a security anti-pattern that removes control rather than standardizing it.

Memory tip: Think "enterprise = enterprise-wide." If the question mentions multiple orgs needing the same rules, the answer lives at the highest level in the hierarchy - the enterprise - not at the org or team level.

No community discussion yet for this question.