GITHUB-ADVANCED-SECURITY practice question 3 of 15
– [Configure and Use Dependency Management] A dependency has a known vulnerability. What does the warning message include?
Full set: 75 questionsWhen GitHub's Dependabot detects a vulnerable dependency in a repository, it generates a security alert. This alert is based on information from the GitHub Advisory Database. A fundamental component of this alert is a description of the vulnerability, which explains the nature of the security flaw (e.g., Cross-Site Scripting, Remote Code Execution). This description, along with a severity level and recommended patched version, provides the necessary context for developers to understand the risk and take appropriate action.
A. The security impact of these changes: This is imprecise. The alert concerns a vulnerability in the current dependency state, not necessarily a recent change. While a severity level (impact) is included, the description is more fundamental.
B. An easily understandable visualization of dependency change: This describes the dependency graph feature, which helps identify dependency relationships, but it is not the primary content of the vulnerability warning message itself.
C. How many projects use these components: This is general ecosystem metadata about a package's popularity. It is not included in a specific security alert for an individual repository.
1. GitHub Docs, "About Dependabot alerts": This document explains that alerts are generated for dependencies with known vulnerabilities. It states, "Each Dependabot alert contains a link to the full vulnerability advisory, which includes information about the vulnerability, its severity, the affected versions, [and] the patched version..." The core "information about the vulnerability" is its description.
Source: GitHub, Inc. (2024). About Dependabot alerts. GitHub Docs. Retrieved from https://docs.github.com/en/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.
2. GitHub Docs, "Viewing and updating Dependabot alerts": This page shows the user interface for a Dependabot alert. The full alert details page explicitly includes a "Description" section, which details the nature of the vulnerability, directly sourced from the corresponding security advisory.
Source: GitHub, Inc. (2024). Viewing and updating Dependabot alerts. GitHub Docs. Retrieved from https://docs.github.com/en/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.
3. GitHub Docs, "About the GitHub Advisory Database": This document details the structure of the security advisories that power Dependabot alerts. It explicitly lists the "description of the vulnerability" as a key piece of information contained within each advisory.
Source: GitHub, Inc. (2024). About the GitHub Advisory Database. GitHub Docs. Retrieved from https://docs.github.com/en/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database.
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 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…
- Question 7– [Configure and Use Code Scanning] Who can fix a code scanning alert on a private reposi…
