ExamworthyExamworthy
Open the appStart free

GH-500 - Describe GitHub Security suites, features, and ecosystem - Section 1.2

Differentiate security feature availability for public repositories versus private repositories and enterprise environments.

Recognise which GitHub Advanced Security features are available for free on public repositories and which require GitHub Enterprise Cloud or GitHub Enterprise Server licences. Apply this knowledge to determine whether a given security feature is accessible in a specific environment.

public repositoriesGitHub Enterprise CloudGitHub Enterprise Serverfeature availability

Practice question for this objective

Free sampleDescribe GitHub Security suites, features, and ecosystemmedium

A platform team is deploying secret scanning custom patterns and validity checks on a GitHub Enterprise Server instance for which the organisation holds a GitHub Advanced Security entitlement. A capability they read about in the GitHub Enterprise Cloud documentation is missing from their server instance's settings. They suspect the instance version rather than the licence. Which consideration most accurately explains why a documented feature might be unavailable on their GitHub Enterprise Server instance even though it is licensed?

  • AValidity checks and custom patterns are billed separately from GitHub Advanced Security on GitHub Enterprise Server, so they stay hidden until that add-on is purchased.
  • BGitHub Enterprise Server never receives secret scanning custom patterns, because custom patterns are a GitHub Enterprise Cloud exclusive that cannot run on self-hosted instances.
  • CThe feature requires a separate per-user GitHub Enterprise Server cloud connector subscription that is distinct from the GitHub Advanced Security entitlement.
  • DGitHub Enterprise Server ships features in numbered releases, so a capability available on GitHub Enterprise Cloud may only reach the server instance once it is upgraded to the version that introduced that capability. Correct
Understand that GitHub Enterprise Server delivers features in versioned releases, so a licensed capability present on GitHub Enterprise Cloud may require a server upgrade before it appears. GitHub Enterprise Cloud is a continuously updated hosted service, while GitHub Enterprise Server is self-hosted and receives functionality through discrete numbered releases. A feature can therefore be live on the cloud yet absent from a server instance until that instance is upgraded to the release that shipped the feature, independent of whether the GitHub Advanced Security entitlement is held.

Why A is wrong: Tempting if the candidate assumes granular add-on billing, but these capabilities are part of the GitHub Advanced Security entitlement, not a hidden separate purchase; availability is gated by the server version.

Why B is wrong: Tempting because some governance features are cloud-first, but secret scanning custom patterns are available on GitHub Enterprise Server given a recent enough version, so the blanket exclusion is wrong.

Why C is wrong: Tempting because GitHub Connect exists, but the missing capability is explained by the instance's release version, not by an additional connector subscription for this feature.

Why D is correct: Correct. GitHub Enterprise Cloud is continuously updated, whereas GitHub Enterprise Server delivers features in discrete versioned releases, so a feature can exist on the cloud and be absent on a server instance until the instance is upgraded to the release that includes it.

See more GH-500 practice questions, answers explained.

More in this domain

Back to all Describe GitHub Security suites, features, and ecosystem objectives, or the GH-500 cert hub.

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