In GitLab, what is the purpose of an approval workflow for licenses?

To generate a report of licenses that need approval

To deny all licenses that are not in the allowed list without any review

To automatically approve all licenses that appear in the project

To allow specific users to manually approve the use of a license that is not in the allowed list

What information does the license compliance report provide for each dependency?

The license name and whether it is allowed, denied, or pending approval

The number of lines of code in the dependency

The maintainer's contact information for each dependency

The exact version of the dependency and its release date

A compliance officer wants to see a summary of all licenses used across the organization's projects, including which ones are not approved. They need a single view that aggregates data from multiple projects. What should they use?

The License Compliance report in each project's pipeline, and manually compile the results.

The group-level License Compliance page, which shows a summary of licenses across all projects in the group.

The project's Dependency List, which includes license information for all dependencies.

The instance-level License Compliance dashboard, which shows all projects in the instance.

A development team wants to prevent merge requests from being merged if they introduce a dependency with a license that is on a company-wide deny list. They already have a license compliance policy that denies those licenses. What else is required to block the merge?

Add a manual approval rule that requires a maintainer to approve the license report before merge.

Enable the 'License Compliance' feature flag in the project settings.

Add the License Compliance job to the pipeline and configure the merge request to require that the license compliance check passes.

Configure the pipeline to run the `license_management` job and set the job to `allow_failure: false`.

A compliance auditor asks for a list of all dependencies in a project that use a license with a 'copyleft' classification. They want this information from the latest pipeline. Where should the administrator look?

The merge request's Changes tab.

The project's Settings > CI/CD > License Compliance page.

The License Compliance report in the latest pipeline, which lists all detected licenses and their status.

GitLabCertified Security Associate

Domain 6Objective 1

Enforce License Compliance GITLAB-CERTIFIED-SECURITY-SPECIALIST Practice Questions (Page 1)

Part of the License Compliance domain, which makes up ~10% of our current practice bank.

14questions here

3free pages

4concepts

Questions 1–5

1foundation · medium
In GitLab, what is the purpose of an approval workflow for licenses?
Select an answer first
2foundation · medium
What information does the license compliance report provide for each dependency?
Select an answer first
3application · medium
A compliance officer wants to see a summary of all licenses used across the organization's projects, including which ones are not approved. They need a single view that aggregates data from multiple projects. What should they use?
Select an answer first
4application · medium
A development team wants to prevent merge requests from being merged if they introduce a dependency with a license that is on a company-wide deny list. They already have a license compliance policy that denies those licenses. What else is required to block the merge?
Select an answer first
5application · medium
A compliance auditor asks for a list of all dependencies in a project that use a license with a 'copyleft' classification. They want this information from the latest pipeline. Where should the administrator look?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to GITLAB-CERTIFIED-SECURITY-SPECIALIST

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by GitLab. “GITLAB-CERTIFIED-SECURITY-SPECIALIST” is a trademark of its owner, used for identification only.