Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  2. Home
  3. Exams
  4. GitHub
  5. GitHub-Advanced-Security

GitHub GitHub-Advanced-Security Exam Questions
GitHub Advanced Security GHAS (Page 2 )

Updated On: 12-Apr-2026
Page 2 of 16
PDF with 75 Questions

­ [Configure and Use Code Scanning]

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?

  1. Draft a pull request to update the open-source query.
  2. Ignore the alert.
  3. Open an issue in the CodeQL repository.
  4. Dismiss the alert with the reason "false positive."

Answer(s): D

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.



­ [Configure and Use Dependency Management]

When does Dependabot alert you of a vulnerability in your software development process?

  1. When a pull request adding a vulnerable dependency is opened
  2. As soon as a vulnerable dependency is detected
  3. As soon as a pull request is opened by a contributor
  4. When Dependabot opens a pull request to update a vulnerable dependency

Answer(s): B

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



­ [Configure and Use Dependency Management]

Which of the following is the most complete method for Dependabot to find vulnerabilities in third- party dependencies?

  1. Dependabot reviews manifest files in the repository
  2. CodeQL analyzes the code and raises vulnerabilities in third-party dependencies
  3. A dependency graph is created, and Dependabot compares the graph to the GitHub Advisory database
  4. The build tool finds the vulnerable dependencies and calls the Dependabot API

Answer(s): C

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



­ [Describe the GHAS Security Features and Functionality]

What is a security policy?

  1. An automatic detection of security vulnerabilities and coding errors in new or modified code
  2. A security alert issued to a community in response to a vulnerability
  3. A file in a GitHub repository that provides instructions to users about how to report a security vulnerability
  4. An alert about dependencies that are known to contain security vulnerabilities

Answer(s): C

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



­ [Configure GitHub Advanced Security Tools in GitHub Enterprise]

As a repository owner, you want to receive specific notifications, including security alerts, for an individual repository.
Which repository notification setting should you use?

  1. Ignore
  2. Participating and @mentions
  3. All Activity
  4. Custom

Answer(s): D

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



Viewing page 2 of 16
Viewing questions 6 - 10 out of 75 questions



Post your Comments and Discuss GitHub GitHub-Advanced-Security exam dumps with other Community members:

GitHub-Advanced-Security Exam Discussions & Posts

AI Tutor AI Tutor 👋 I’m here to help!