Assuming that notification and alert recipients are not customized, what does GitHub do when it identifies a vulnerable dependency in a repository where Dependabot alerts are enabled? (Each answer presents part of the solution. Choose two.)
When GitHub identifies a vulnerable dependency in a repository with Dependabot alerts enabled, it performs the following actions:
Generates a Dependabot alert: The alert is displayed on the repository's Security tab, providing details about the vulnerability and affected dependency.
Notifies repository maintainers: By default, GitHub notifies users with write, maintain, or admin permissions about new Dependabot alerts.
GitHub Docs
These actions ensure that responsible parties are informed promptly to address the vulnerability.
References: GitHub Docs -- About Dependabot alerts; Configuring notifications for Dependabot alerts
==========
What is a benefit of using a custom CodeQL configuration file?
A custom CodeQL configuration file can be stored in an external repository and referenced by multiple repositories. This allows an organization to centralize query packs, additional queries, query filters, path exclusions, threat-model configuration, and other CodeQL settings rather than duplicating the same settings across many workflow files. GitHub explicitly documents centralized configuration as a benefit of external configuration files. A token may be required when an advanced-setup workflow retrieves a configuration file from a private external repository, but providing the token is not the purpose of the configuration file itself. Likewise, a configuration file does not automatically choose a package, and query packs do not inherently disable the default query suite. Default queries are disabled only when the appropriate configuration option is deliberately specified. Therefore, C is correct.
When using CodeQL, how does extraction for compiled languages work?
For compiled languages, CodeQL performs extraction by monitoring the normal build process. This means it watches your usual build commands (like make, javac, or dotnet build) and extracts the relevant data from the actual build steps being executed. CodeQL uses this information to construct a semantic database of the application.
This approach ensures that CodeQL captures a precise, real-world representation of the code and its behavior as it is compiled, including platform-specific configurations or conditional logic used during build.
References: GitHub Docs -- CodeQL for compiled languages
==========
-- [Use Code Scanning with CodeQL]
Which CodeQL query suite provides queries of lower severity than the default query suite?
The security-extended query suite includes additional CodeQL queries that detect lower severity issues than 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 are paths to language packs, not query suites themselves.
-- [Use Code Scanning with CodeQL]
When using CodeQL, what extension stores query suite definitions?
Query suite definitions in CodeQL are stored using the .qls file extension. A query suite defines a collection of queries to be run during an analysis and allows for grouping them based on categories like language, security relevance, or custom filters.
In contrast:
.ql files are individual queries.
.qll files are libraries used by .ql queries.
.yml is used for workflows, not query suites.
John Davis
1 month agoSteven Jackson
2 months agoJoseph Cooper
2 months agoSandra Roberts
3 months agoJeffrey Nelson
3 months agoMatthew Anderson
4 months agoOlivia Jones
4 months agoCrystal Hall
5 months agoBarbara Green
5 months agoSharon Green
6 months agoStephanie Howard
6 months agoRichard Jones
6 months agoAmy Lee
6 months agoAngela Reed
6 months agoOlivia Stewart
6 months agoLucia
7 months agoLauran
7 months agoMaryann
7 months agoMicheline
8 months agoThersa
8 months agoLorriane
8 months agoGretchen
8 months agoJesse
9 months agoKrissy
9 months agoDick
9 months agoGianna
9 months agoEllsworth
10 months agoDaniela
10 months agoCaprice
10 months agoQuiana
10 months agoLanie
11 months agoJuan
11 months agoDarrin
11 months agoGregoria
11 months agoKathryn
12 months agoCarmela
12 months agoDella
1 year agoTesha
1 year agoAlva
1 year agoVerona
1 year agoMadalyn
1 year agoMargarett
1 year agoDaren
1 year agoCora
1 year agoJesus
1 year ago