In a workflow: GitHub Actions workflows are the most common place for CodeQL code scanning. The codeql-analysis.yml defines how the analysis runs and when it triggers.
In an external CI system: GitHub allows you to run CodeQL analysis outside of GitHub Actions. Once complete, the results can be uploaded using the upload-sarif action to make alerts visible in the repository.
You cannot run or trigger analysis from third-party repositories directly, and theFiles changed tabin pull requests only shows diff — not analysis results.
[: GitHub Docs – Using CodeQL with CI and workflows, ==========]
Question # 5
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.
Thedependency graphin a repository is built byparsing 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 # 6
Why should you dismiss a code scanning alert?
A.
If you fix the code that triggered the alert
B.
To prevent developers from introducing new problems
C.
If it includes an error in code that is used only for testing
Thefirst stepwhen you receive a secret scanning alert is torevoke the secretif 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 doesnotremove the risk if it hasn’t been revoked — especially since it may already be exposed in commit history.
[: GitHub Docs – About secret scanning alerts; Remediating a secret scanning alert, ==========]
Question # 8
Which CodeQL query suite provides queries of lower severity than the default query suite?
Thesecurity-extendedquery suite includes additional CodeQL queries that detectlower severity issuesthan those in the default security-and-quality suite.
It’s often used when projects want broader visibility into code hygiene and potential weak spots beyond critical vulnerabilities.
The other options listed arepaths to language packs, not query suites themselves.