Free GitHub Advanced Security Exam Practice Questions

For GitHub Enterprise Server, secret scanning and code scanning are Advanced Security capabilities that require instance-level availability and configuration before organizations and repositories can use them. GitHub's GHES administration documentation identifies code scanning and secret scanning as security products that site administrators enable and configure for the appliance. Dependency review operates through repository dependency data and GitHub Actions rather than being one of the corresponding appliance-level Management Console options described by this question. Dependabot version updates are also a separate Dependabot capability for automatically keeping dependencies current and are not the requested GHAS Management Console security option. GitHub's newer licensing terminology may refer to these capabilities through GitHub Secret Protection and GitHub Code Security, but the functional distinction tested by the question remains the same.

To proactively address secret scanning:

Webhooks can be configured to listen for secret scanning events. This allows automation, logging, or alerting in real-time when secrets are detected.

Documenting secure development practices (like using environment variables or secret managers) helps reduce the likelihood of developers committing secrets in the first place.

Dismissal based on age is not a best practice without triage. SCIM deals with user provisioning, not scanning alerts.