GH-500 domain - 14% of the exam

GitHub Security suites administration

GitHub Security suites administration is 14% of the GH-500 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

40
Practice questions
4
Objectives
9
Medium
31
Hard

Where people go wrong

  • Treating a default configuration as retroactive

    The wrong answers assume that setting a security configuration as the default reaches every repository, or that waiting will sweep older ones in. A default governs only repositories created after it is set, so repositories that already existed stay unprotected. The owner must explicitly apply the configuration to existing repositories, selecting them in bulk. A repository transferred into the organisation is not newly created either, so it also needs the configuration applied manually.

    See it in a sample question
  • Misreading what enforcement and detaching do

    The wrong answers blur three states. Attaching a configuration does not lock settings; only the enforced status stops a repository administrator from changing the features it manages. An unenforced configuration lets the administrator turn a feature off. Detaching does not switch features off or roll them back either: the repository keeps its current feature states, the link to the configuration ends, and the settings become editable again at repository level.

    See it in a sample question
  • Using a ruleset to switch features on

    The wrong answers reach for a ruleset, or another governance tool, to switch security features on. A ruleset governs branch and tag actions such as required checks and restricted pushes, so it cannot enable secret scanning, push protection or default setup, and a ruleset alone leaves a required check with nothing to evaluate. A template repository does not carry enabled features, and an allow policy only permits a feature. A security configuration is the tool that enables them, and an enterprise-level one is authored once and offered to every organisation.

    See it in a sample question
  • Letting a closer scope override a broader one

    The wrong answers assume that the setting nearest the repository wins. An enforced enterprise policy removes the option to disable push protection beneath it, and an organisation configuration cannot fall below an enterprise requirement. Rulesets do not override by proximity or creation order either: they aggregate, the most restrictive requirement applies, and a bypass entry on one ruleset does nothing for another ruleset.

    See it in a sample question

Objectives in this domain

What to study

The official documents this domain's practice questions cite most.

Sample questions from this domain

Free sampleGitHub Security suites administrationhard

An organisation owner sets a custom security configuration as the default for all newly created repositories but does not bulk-apply it to the hundreds of repositories that already exist. Three weeks later a team reports that an older repository has none of the new protections active. Assuming nobody changed that repository in the meantime, why is the older repository still unprotected?

  • ASetting a configuration as the default for newly created repositories does not attach it to repositories that already existed, which still need an explicit apply action. Correct
  • BDefaults apply retroactively only to repositories with recent push activity, and the older repository has been inactive long enough to fall outside the retroactive window.
  • CThe configuration failed to attach because a default can cover newly created repositories or existing repositories, but not both, and the owner chose the former.
  • DThe older repository inherited an 'enforced' empty configuration at creation that takes precedence over any later default and must be detached first.
Recognise that a default for newly created repositories does not attach to pre-existing repositories, which require an explicit apply action. Designating a security configuration as the default for newly created repositories only affects repositories created after that point. Repositories that already existed are left untouched and stay unattached until the organisation explicitly applies the configuration to existing repositories, which explains why an unchanged older repository shows none of the new protections.

Why A is correct: The default for newly created repositories governs only repositories made after it is set, so pre-existing repositories remain unattached. Bringing them under the configuration requires explicitly applying it to existing repositories, which the owner did not do.

Why B is wrong: There is no activity-based retroactive window for default configurations, so this fabricates a rule. Default status concerns when a repository is created, not how recently it has received pushes.

Why C is wrong: Framing this as a forced either-or where choosing new repositories actively excludes existing ones is misleading. The default for new repositories simply does not reach back to existing ones, rather than being blocked by an exclusive toggle.

Why D is wrong: Repositories are not seeded with a hidden enforced empty configuration that pre-empts later defaults, so this invents a blocking artefact. The straightforward reason is that defaults for new repositories never attach to ones created earlier.

Free sampleGitHub Security suites administrationhard

An organisation owner attaches the 'GitHub recommended' security configuration to a repository and sets the configuration's enforcement status to enforced. A repository administrator then opens that repository's 'Code security' settings and tries to turn off secret scanning, which the configuration enables. What outcome should the repository administrator expect?

  • AThe administrator can disable secret scanning for the repository, but the change is reverted automatically the next time the configuration is reapplied across the organisation.
  • BThe secret scanning toggle is unavailable for the settings the enforced configuration manages, so the administrator cannot disable it at the repository level. Correct
  • CThe administrator can disable secret scanning because repository-level settings always take precedence over an organisation security configuration.
  • DThe administrator must first detach the configuration, after which secret scanning can be disabled and the configuration silently reattaches with the new value.
Recognise that an enforced security configuration locks the feature settings it manages so repository administrators cannot override them locally. Setting a security configuration to enforced means the feature settings it defines, such as secret scanning, become read-only on every repository the configuration is attached to. Repository administrators see the managed toggles disabled, so they cannot turn the feature off, revert it later, or detach the configuration to escape it.

Why A is wrong: A reapply-and-revert cycle sounds plausible if you imagine enforcement as periodic reconciliation, but enforced configurations prevent the local change in the first place. There is no window in which the administrator successfully disables the feature and is later corrected.

Why B is correct: An enforced security configuration locks the feature settings it defines, so a repository administrator cannot override them locally and the relevant controls are not editable. Secret scanning therefore stays enabled exactly as the configuration dictates.

Why C is wrong: Repository settings do win when a configuration is attached but not enforced, which is why this is tempting. Enforcement is the specific status that removes that local override, so a blanket claim that repository settings always take precedence is wrong here.

Why D is wrong: A repository administrator cannot unilaterally detach an enforced organisation configuration, and detaching would not preserve a local override anyway. This describes a self-service escape hatch that enforcement is designed to close.

Free sampleGitHub Security suites administrationmedium

An enterprise owner on GitHub Enterprise Cloud wants one named baseline that enables secret scanning with push protection and code scanning, and wants it offered to every organisation in the enterprise so each organisation owner can apply it without rebuilding it. The owner does not want to log in to each organisation to recreate the same settings. Which mechanism lets the owner author the baseline once at the enterprise tier and make it available to the organisations beneath it?

  • ACreate the security configuration inside each organisation, then export and import the JSON between organisations so the settings stay identical across the enterprise.
  • BDefine a repository ruleset at the enterprise tier that turns on secret scanning and code scanning whenever a branch matching the ruleset receives a push.
  • CAssign the security manager role at the enterprise tier so the holders inherit a standard set of enabled features across all member organisations automatically.
  • DCreate an enterprise-level security configuration, which the enterprise owner authors once and which then becomes available for organisation owners to apply to their repositories. Correct
Recognise that an enterprise-level security configuration is authored once and made available for organisations to apply. Security configurations can be defined at the enterprise tier so the enterprise owner authors the baseline of features such as secret scanning with push protection and code scanning a single time. That configuration then becomes available to the organisations in the enterprise, where organisation owners apply it to repositories without recreating the settings.

Why A is wrong: There is no export-import flow for security configurations, and this still requires touching every organisation, which is exactly what the owner wants to avoid. It is tempting because copying config-as-code feels scalable, but it is not how the feature distributes baselines.

Why B is wrong: Rulesets govern branch and tag protections such as required checks and restricted pushes; they do not enable security features. The plausibility is that rulesets exist at enterprise scope, but they enforce branch rules rather than provision the scanning suite.

Why C is wrong: The security manager role grants permission to view and manage security settings and alerts; it does not bundle or push a feature baseline. Granting access is not the same as authoring and distributing a configuration, so this confuses a role with a configuration.

Why D is correct: Enterprise-level security configurations let an enterprise owner define a reusable baseline at the top tier that flows down to the organisations, where organisation owners can apply it. This matches authoring once and offering it downward without recreating settings per organisation.

Free sampleGitHub Security suites administrationhard

An enterprise owner defines a code scanning ruleset at the enterprise level that requires a passing CodeQL check on the default branch, and targets all organisations. An organisation owner inside that enterprise dislikes the rule and creates an organisation ruleset that does not require the check, hoping to relax it for their repositories. For a repository in that organisation, what is the net effect on the default branch?

  • AThe organisation ruleset overrides the enterprise ruleset for that organisation's repositories, so the code scanning check is no longer required there.
  • BThe two rulesets conflict, so GitHub disables both until an administrator resolves the contradiction in the enterprise security settings.
  • CBoth rulesets apply and their requirements are combined, so the code scanning check remains required because the enterprise rule still targets the repository. Correct
  • DWhichever ruleset was created most recently takes precedence, so the organisation's newer ruleset relaxes the requirement.
Recognise that enterprise and organisation rulesets layer cumulatively, so a lower-scope ruleset cannot relax a requirement imposed at a higher scope. When multiple rulesets target the same repository, GitHub evaluates all of them together and enforces the union of their requirements, applying the most restrictive outcome. An organisation ruleset that omits a check does not cancel an enterprise ruleset that requires it, so the enterprise-mandated code scanning check stays in force on the default branch.

Why A is wrong: Lower-scope rulesets feel like they should win because they are closer to the repository, but rulesets do not override one another by proximity. An organisation ruleset cannot loosen a requirement that an enterprise ruleset imposes.

Why B is wrong: A conflict-disables-both model sounds like a safe failure mode, but rulesets do not deactivate on disagreement. They aggregate, and a permissive rule simply adds nothing on top of a stricter one rather than cancelling it.

Why C is correct: Rulesets layer rather than override: all rulesets targeting a repository apply at once, and the most restrictive combination governs. The enterprise requirement therefore still holds, and the permissive organisation ruleset cannot subtract it.

Why D is wrong: Creation order is irrelevant to ruleset evaluation, though it is a plausible guess by analogy with last-write-wins systems. All applicable rulesets are evaluated together regardless of when each was created.

Other domains in this exam

See also the GH-500 cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by GitHub. Original, blueprint-aligned practice material only.