Free GitHub Advanced Security Exam Braindumps
GitHub Advanced Security GHAS Questions 21–25 (page: 6)

Updated On: 10-Feb-2026

­ [Use Code Scanning with CodeQL]

How would you build your code within the CodeQL analysis workflow? (Each answer presents a complete solution. Choose two.)

  1. Upload compiled binaries.
  2. Use CodeQL's init action.
  3. Ignore paths.
  4. Implement custom build steps.
  5. Use jobs.analyze.runs-on.
  6. Use CodeQL's autobuild action.

Answer(s): D,F

Explanation:

Comprehensive and Detailed Explanation;
When setting up CodeQL analysis for compiled languages, there are two primary methods to build your code:

GitHub Docs

Autobuild: CodeQL attempts to automatically build your codebase using the most likely build method. This is suitable for standard build processes.

GitHub Docs

Custom Build Steps: For complex or non-standard build processes, you can implement custom build steps by specifying explicit build commands in your workflow. This provides greater control over the build process.

GitHub Docs

The init action initializes the CodeQL analysis but does not build the code. The jobs.analyze.runs-on specifies the operating system for the runner but is not directly related to building the code. Uploading compiled binaries is not a method supported by CodeQL for analysis.


Reference:

GitHub Docs ­ CodeQL code scanning for compiled languages



­ [Configure and Use Dependency Management]

Which of the following workflow events would trigger a dependency review? (Each answer presents a complete solution. Choose two.)

  1. pull_request
  2. workflow_dispatch
  3. trigger
  4. commit

Answer(s): A,B

Explanation:

Comprehensive and Detailed Explanation;
Dependency review is triggered by specific events in GitHub workflows:

pull_request: When a pull request is opened, synchronized, or reopened, GitHub can analyze the changes in dependencies and provide a dependency review.

workflow_dispatch: This manual trigger allows users to initiate workflows, including those that perform dependency reviews.

The trigger and commit options are not recognized GitHub Actions events and would not initiate a dependency review.


Reference:

GitHub Docs ­ Events that trigger workflows



­ [Configure and Use Dependency Management]

You are a maintainer of a repository and Dependabot notifies you of a vulnerability.
Where could the vulnerability have been disclosed? (Each answer presents part of the solution. Choose two.)

  1. In the National Vulnerability Database
  2. In the dependency graph
  3. In security advisories reported on GitHub
  4. In manifest and lock files

Answer(s): A,C

Explanation:

Comprehensive and Detailed Explanation;
Dependabot alerts are generated based on data from various sources:

National Vulnerability Database (NVD): A comprehensive repository of known vulnerabilities, which GitHub integrates into its advisory database.

GitHub Docs

Security Advisories Reported on GitHub: GitHub allows maintainers and security researchers to report and discuss vulnerabilities, which are then included in the advisory database.

The dependency graph and manifest/lock files are tools used by GitHub to determine which dependencies are present in a repository but are not sources of vulnerability disclosures themselves.


Reference:

GitHub Docs ­ About Dependabot alerts



­ [Configure and Use Secret Scanning]

Which of the following statements most accurately describes push protection for secret scanning custom patterns?

  1. Push protection must be enabled for all, or none, of a repository's custom patterns.
  2. Push protection is an opt-in experience for each custom pattern.
  3. Push protection is not available for custom patterns.
  4. Push protection is enabled by default for new custom patterns.

Answer(s): B

Explanation:

Comprehensive and Detailed Explanation;
Push protection for secret scanning custom patterns is an opt-in feature. This means that for each custom pattern defined in a repository, maintainers can choose to enable or disable push protection individually. This provides flexibility, allowing teams to enforce push protection on sensitive patterns while leaving it disabled for others.


Reference:

GitHub Docs ­ Working with push protection from the command line



­ [Use Code Scanning with CodeQL]

When using the advanced CodeQL code scanning setup, what is the name of the workflow file?

  1. codeql-config.yml
  2. codeql-scan.yml
  3. codeql-workflow.yml
  4. codeql-analysis.yml

Answer(s): D

Explanation:

Comprehensive and Detailed Explanation;
In the advanced setup for CodeQL code scanning, GitHub generates a workflow file named codeql- analysis.yml. This file is located in the .github/workflows directory of your repository. It defines the configuration for the CodeQL analysis, including the languages to analyze, the events that trigger the analysis, and the steps to perform during the workflow.


Reference:

GitHub Docs ­ Customizing your advanced setup for code scanning



Viewing page 6 of 16
Viewing questions 26 - 30 out of 75 questions


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

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