Which of the following lists the four primary features of GitHub Advanced Security?

Prepare for the GitHub Advanced Security Certification Test. Practice with multiple choice questions, detailed explanations, and hints. Achieve success on your first attempt!

Multiple Choice

Which of the following lists the four primary features of GitHub Advanced Security?

Explanation:
Understanding these four features shows how GitHub Advanced Security protects your code, secrets, dependencies, and component provenance. Code Scanning with CodeQL automatically analyzes your codebase to find security flaws across languages, giving developers quick feedback on potential vulnerabilities as they write and review code. Secret Scanning adds a layer that detects exposed credentials or sensitive tokens in the repository, helping prevent accidental leaks before code is merged. Dependency Review/Graph looks at the libraries and packages your project relies on, identifying known vulnerabilities and risky versions, and it maps how dependencies relate to each other so you can assess impact across the supply chain. SBOM Generation and Usage creates a Software Bill of Materials, listing every component included in the build and enabling ongoing tracking of vulnerabilities, licenses, and compliance through the lifecycle of the software. This combination is comprehensive because it covers secure coding, secret hygiene, supply-chain risk from dependencies, and visibility into all components through SBOMs. Lists that omit any of these capabilities would miss a critical aspect of Advanced Security, making the option that includes all four the best choice.

Understanding these four features shows how GitHub Advanced Security protects your code, secrets, dependencies, and component provenance. Code Scanning with CodeQL automatically analyzes your codebase to find security flaws across languages, giving developers quick feedback on potential vulnerabilities as they write and review code. Secret Scanning adds a layer that detects exposed credentials or sensitive tokens in the repository, helping prevent accidental leaks before code is merged. Dependency Review/Graph looks at the libraries and packages your project relies on, identifying known vulnerabilities and risky versions, and it maps how dependencies relate to each other so you can assess impact across the supply chain. SBOM Generation and Usage creates a Software Bill of Materials, listing every component included in the build and enabling ongoing tracking of vulnerabilities, licenses, and compliance through the lifecycle of the software.

This combination is comprehensive because it covers secure coding, secret hygiene, supply-chain risk from dependencies, and visibility into all components through SBOMs. Lists that omit any of these capabilities would miss a critical aspect of Advanced Security, making the option that includes all four the best choice.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy