GITHUB-ADVANCED-SECURITY practice question 14 of 15
– [Configure and Use Dependency Management] A repository's dependency graph includes:
Full set: 75 questionsThe dependency graph for a specific repository is a feature that identifies all upstream dependencies and public downstream dependents. GitHub generates this graph by parsing manifest files (e.g., package.json, requirements.txt) and lock files (e.g., package-lock.json, Gemfile.lock) committed to the repository's default branch. This parsed information forms the basis of the graph, detailing the packages and versions the project relies on. Other security features, such as Dependabot alerts, then use this graph to identify vulnerabilities.
B. Annotated code scanning alerts are a separate feature that uses the dependency graph to flag vulnerabilities; they are not a component of the graph itself.
C. This describes the organization-level dependency insights view, which aggregates data from multiple repositories, not the graph for a single repository.
D. The dependency graph is scoped to a single repository, not an aggregation of dependencies from all of a user's or organization's repositories.
1. GitHub Docs. (n.d.). About the dependency graph. Retrieved from https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph
Section: "Dependency graph": "The dependency graph is a summary of the manifest and lock files stored in a repository... GitHub scans common package manifest files... in the default branch of your repository to find dependencies."
2. GitHub Docs. (n.d.). About Dependabot alerts. Retrieved from https://docs.github.com/en/code-security/dependabot/dependabot-alerts/about-dependabot-alerts
Section: "Detection of insecure dependencies": This page explains that Dependabot alerts are generated when a vulnerability is found for a dependency listed in the dependency graph, clarifying that alerts are a separate, subsequent process.
3. GitHub Docs. (n.d.). Viewing the dependency graph for your repository. Retrieved from https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/viewing-the-dependency-graph-for-your-repository
This document explicitly details the process for viewing the graph on a per-repository basis, reinforcing that its scope is a single repository.
Keep practicing
Take the free GITHUB-ADVANCED-SECURITY practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other GITHUB-ADVANCED-SECURITY practice questions
- Question 1– [Use Code Scanning with CodeQL] When using CodeQL, what extension stores query suite de…
- Question 2– [Configure and Use Secret Scanning] What happens when you enable secret scanning on a p…
- Question 3– [Configure and Use Dependency Management] A dependency has a known vulnerability. What …
- Question 4– [Configure and Use Secret Scanning] What is a prerequisite to define a custom pattern f…
- Question 5– [Describe the GHAS Security Features and Functionality] What is a security policy?
- Question 6– [Configure GitHub Advanced Security Tools in GitHub Enterprise] What role is required t…
