Enjoy 20% OFF on CertsVault exam resources — use PREP20 at checkout!
Certs Vault
See all results for ""
Home Exams
CRISC ISACA CISSP ISC2 200-301 Cisco SY0-701 CompTIA AZ-104 Microsoft AI-900 Microsoft AIGP IAPP 1Z0-1067-26 Oracle View All Exams →
Sign in Create account

GitHub Advanced Security Certification GitHub-Advanced-Security Exam Questions

Preparing for the GitHub-Advanced-Security exam is simple with Certs Vault. We offer easy-to-understand study materials that help you learn the most important exam topics. You can study using our PDF questions, practice online with a real exam-style test, or use the desktop practice software. Choose the study method that works best for you and prepare at your own pace.

At Certs Vault, we keep our GitHub-Advanced-Security practice questions up to date. Whenever the exam syllabus or objectives change, we update our study materials so you always learn the latest topics. This helps you save time, avoid outdated content, and feel more confident when you take your exam.

Download Exam View Entire Exam
Page: 1 / 1
Question #1 (Topic: Demo Questions)

Which security feature shows a vulnerable dependency in a pull request?

A.

Dependency graph

B.

Dependency review

C.

Dependabot alert

D.

The repository's Security tab

Correct Answer: B
Explanation:

Dependency review runs as part of a pull request and shows which dependencies are being added, removed, or changed — and highlights vulnerabilities associated with any added packages.

It works in real-time and is specifically designed for use during pull request workflows.

The dependency graph is an overview, Dependabot alerts notify post-merge, and the Security tab shows the aggregated alert list.

[: GitHub Docs – About Dependency Review, ==========]
Question #2 (Topic: Demo Questions)

Which of the following options would close a Dependabot alert?

A.

Creating a pull request to resolve the vulnerability that will be approved and merged

B.

Viewing the Dependabot alert on the Dependabot alerts tab of your repository

C.

Viewing the dependency graph

D.

Leaving the repository in its current state

Correct Answer: A
Explanation:

A Dependabot alert is only marked as resolved when the related vulnerability is no longer present in your code — specifically after you merge a pull request that updates the vulnerable dependency.

Simply viewing alerts or graphs does not affect their status. Ignoring the alert by leaving the repo unchanged keeps the vulnerability active and unresolved.

[: GitHub Docs – Managing Dependabot Security Updates, ==========]
Question #3 (Topic: Demo Questions)

Where in the repository can you give additional users access to secret scanning alerts?

A.

Security

B.

Settings

C.

Secrets

D.

Insights

Correct Answer: B
Explanation:

To grant specific users access to view and manage secret scanning alerts , you do this via the Settings tab of the repository. From there, under the "Code security and analysis" section, you can add individuals or teams with roles such as security manager .

The Security tab only displays alerts; access control is handled in Settings.

[: GitHub Docs – Granting Access to Secret Scanning Alerts, ==========]
Question #4 (Topic: Demo Questions)

A repository's dependency graph includes:

A.

Dependencies parsed from a repository's manifest and lock files.

B.

Annotated code scanning alerts from your repository's dependencies.

C.

A summary of the dependencies used in your organization's repositories.

D.

Dependencies from all your repositories.

Correct Answer: A
Explanation:

The dependency graph in a repository is built by parsing manifest and lock files (like package.json, pom.xml, requirements.txt). It helps GitHub detect dependencies and cross-reference them with known vulnerability databases for alerting.

It is specific to each repository and does not show org-wide or cross-repo summaries.

[: GitHub Docs – Understanding the Dependency Graph, ==========]
Question #5 (Topic: Demo Questions)

Secret scanning will scan:​

A.

A continuous integration system.

B.

Any Git repository.

C.

The GitHub repository.

D.

External services.​

Correct Answer: C
Explanation:

Secret scanning is a feature provided by GitHub that scans the contents of your GitHub repositories for known types of secrets, such as API keys and tokens. It operates within the GitHub environment and does not scan external systems, services, or repositories outside of GitHub. Its primary function is to prevent the accidental exposure of sensitive information within your GitHub-hosted code.​

[: GitHub Docs – About secret scanning​, ]
Download Exam
Page: 1 / 1
Next Page