📘 Free GH-500 Sample Questions
After investigating a code scanning alert related to injection, you determine that the input is properly sanitized using custom logic. What should be your next step?
A
Draft a pull request to update the open-source query.
B
Ignore the alert.
C
Open an issue in the CodeQL repository.
D
Dismiss the alert with the reason "false positive."
Correct Answer:
D. Dismiss the alert with the reason "false positive."
Explanation:
When you identify that a code scanning alert is a false positive—such as when your code uses a
custom sanitization method not recognized by the analysis—you should dismiss the alert with the
reason "false positive." This action helps improve the accuracy of future analyses and maintains the
relevance of your security alerts.
As per GitHub's documentation:
"If you dismiss a CodeQL alert as a false positive result, for example because the code uses a
sanitization library that isn't supported, consider contributing to the CodeQL repository and
improving the analysis."
By dismissing the alert appropriately, you ensure that your codebase's security alerts remain
actionable and relevant.
When does Dependabot alert you of a vulnerability in your software development process?
A
When a pull request adding a vulnerable dependency is opened
B
As soon as a vulnerable dependency is detected
C
As soon as a pull request is opened by a contributor
D
When Dependabot opens a pull request to update a vulnerable dependency
Correct Answer:
B. As soon as a vulnerable dependency is detected
Explanation:
Dependabot alerts are generated as soon as GitHub detects a known vulnerability in one of your
dependencies. GitHub does this by analyzing your repository’s dependency graph and matching it
against vulnerabilities listed in the GitHub Advisory Database. Once a match is found, the system
raises an alert automatically without waiting for a PR or manual action.
This allows organizations to proactively mitigate vulnerabilities as early as possible, based on real-
time detection.
Reference: GitHub Docs – About Dependabot alerts; Managing alerts in GitHub Dependabot
Which of the following is the most complete method for Dependabot to find vulnerabilities in third- Dependabot reviews manifest files in the repositoryparty dependencies?
A
Dependabot reviews manifest files in the repository
B
CodeQL analyzes the code and raises vulnerabilities in third-party dependencies
C
A dependency graph is created, and Dependabot compares the graph to the GitHub Advisory
database
D
The build tool finds the vulnerable dependencies and calls the Dependabot API
Correct Answer:
C. A dependency graph is created, and Dependabot compares the graph to the GitHub Advisory
database
Explanation:
Dependabot builds a dependency graph by analyzing package manifests and lockfiles in your
repository. This graph includes both direct and transitive dependencies. It then compares this graph
against the GitHub Advisory Database, which includes curated, security-reviewed advisories.
This method provides a comprehensive and automated way to discover all known vulnerabilities
across your dependency tree. Reference: GitHub Docs – About the dependency graph; About Dependabot alerts
What is a security policy?
A
An automatic detection of security vulnerabilities and coding errors in new or modified code
B
A security alert issued to a community in response to a vulnerability
C
A file in a GitHub repository that provides instructions to users about how to report a security
vulnerability
D
An alert about dependencies that are known to contain security vulnerabilities
Correct Answer:
C. A file in a GitHub repository that provides instructions to users about how to report a security
vulnerability
Explanation:
A security policy is defined by a SECURITY.md file in the root of your repository or .github/ directory.
This file informs contributors and security researchers about how to responsibly report
vulnerabilities. It improves your project’s transparency and ensures timely communication and
mitigation of any reported issues.
Adding this file also enables a “Report a vulnerability” button in the repository’s Security tab.
Reference: GitHub Docs – Adding a security policy to your repository
As a repository owner, you want to receive specific notifications, including security alerts, for an
individual repository. Which repository notification setting should you use?
A
Ignore
B
Participating and @mentions
C
All Activity
D
Custom
Correct Answer:
D. Custom
Explanation:
Using the Custom setting allows you to subscribe to specific event types, such as Dependabot alerts
or vulnerability notifications, without being overwhelmed by all repository activity. This is essential
for repository maintainers who need fine-grained control over what kinds of events trigger
notifications.
This setting is configurable per repository and allows users to stay aware of critical issues while
minimizing notification noise.
Reference: GitHub Docs – Configuring notifications; Managing security alerts
Which of the following Watch settings could you use to get Dependabot alert notifications? (Each answer presents part of the solution. Choose two.)
A
The Custom setting
B
The Participating and @mentions setting
C
The All Activity setting
D
The Ignore setting
Correct Answer:
A. The Custom setting
Explanation:
Comprehensive and Detailed Explanation:
To receive Dependabot alert notifications for a repository, you can utilize the following Watch
settings:
Custom setting: Allows you to tailor your notifications, enabling you to subscribe specifically to
security alerts, including those from Dependabot.
All Activity setting: Subscribes you to all notifications for the repository, encompassing issues, pull
requests, and security alerts like those from Dependabot.
The Participating and @mentions setting limits notifications to conversations you're directly involved
in or mentioned, which may not include security alerts. The Ignore setting unsubscribes you from all
notifications, including critical security alerts.
GitHub Docs
+1
GitHub Docs
+1
Reference: GitHub Docs – Configuring notifications; Managing security alerts
Which Dependabot configuration fields are required? (Each answer presents part of the solution. Choose three.)
A
directory
B
package-ecosystem
C
milestone
D
schedule.interval
E
allow
Correct Answer:
A. directory
Explanation:
Comprehensive and Detailed Explanation:
When configuring Dependabot via the dependabot.yml file, the following fields are mandatory for
each update configuration:
directory: Specifies the location of the package manifest within the repository. This tells Dependabot
GH-500: Actual Exam Q&A | CLEARCATNET
where to look for dependency files.
package-ecosystem: Indicates the type of package manager (e.g., npm, pip, maven) used in the
specified directory.
schedule.interval: Defines how frequently Dependabot checks for updates (e.g., daily, weekly). This
ensures regular scanning for outdated or vulnerable dependencies.
The milestone field is optional and used for associating pull requests with milestones. The allow field
is also optional and used to specify which dependencies to update.
GitLab
Reference: GitHub Docs – Configuration options for dependency updates
As a contributor, you discovered a vulnerability in a repository. Where should you look for the instructions on how to report the vulnerability?
A
support.md
B
readme.md
C
contributing.md
D
security.md
Correct Answer:
D. security.md
Explanation:
The correct place to look is the SECURITY.md file. This file provides contributors and security
researchers with instructions on how to responsibly report vulnerabilities. It may include contact
methods, preferred communication channels (e.g., security team email), and disclosure guidelines.
This file is considered a GitHub best practice and, when present, activates a “Report a vulnerability”
button in the repository’s Security tab.
Reference: GitHub Docs – Adding a security policy to your repository
Assuming there is no custom Dependabot behavior configured, where possible, what does Dependabot do after sending an alert about a vulnerable dependency in a repository?
A
Creates a pull request to upgrade the vulnerable dependency to the minimum possible secure
version
B
Scans repositories for vulnerable dependencies on a schedule and adds those files to a manifest
C
Constructs a graph of all the repository's dependencies and public dependents for the default
branch
D
Scans any push to all branches and generates an alert for each vulnerable repository
Correct Answer:
A. Creates a pull request to upgrade the vulnerable dependency to the minimum possible secure
version
Explanation:
After generating an alert for a vulnerable dependency, Dependabot automatically attempts to create
a pull request to upgrade that dependency to the minimum required secure version—if a fix is
available and compatible with your project.
This automated PR helps teams fix vulnerabilities quickly with minimal manual intervention. You can
also configure update behaviors using dependabot.yml, but in the default state, PR creation is
automatic.
Reference: GitHub Docs – About Dependabot alerts; About Dependabot security updates
What is the first step you should take to fix an alert in secret scanning?
A
Archive the repository.
B
Update your dependencies.
C
Revoke the alert if the secret is still valid.
D
Remove the secret in a commit to the main branch.
Correct Answer:
C. Revoke the alert if the secret is still valid.
Explanation:
The first step when you receive a secret scanning alert is to revoke the secret if it is still valid. This
ensures the secret can no longer be used maliciously. Only after revoking it should you proceed to
remove it from the code history and apply other mitigation steps.
Simply deleting the secret from the code does not remove the risk if it hasn’t been revoked —
especially since it may already be exposed in commit history.
Reference: GitHub Docs – About secret scanning alerts; Remediating a secret scanning alert
Questions: 1-10 out of 75
Continue Full Practice..
GET ALL 75 QUESTIONS