When creating a license approval policy in GitLab, what must you specify to define the policy?

The URL of the open-source license database to reference

The version of GitLab that will enforce the policy

The name of the legal team responsible for approving licenses

The list of licenses that are allowed and the list of licenses that are denied

In GitLab, where do license approval policies apply by default?

Only to projects that explicitly opt in to the policy

Only to the project where the policy is created

To the group where the policy is created and all its subgroups and projects

To all projects in the instance, regardless of group membership

When does GitLab enforce a license approval policy during a merge request?

During the pipeline execution, when license compliance is checked

Only when a user manually triggers a license check

When the merge request is created, before any pipeline runs

After the merge request is merged, during a post-merge scan

A security analyst reviews the license compliance report of a merge request and sees a license marked as 'not approved'. The policy action is 'warn'. What should the analyst do next?

Approve the license automatically in the report.

Block the merge request manually.

Review the dependency and decide whether to approve the license or request a change.

Ignore the warning because the policy is set to 'warn'.

A company's legal team has decided to deny the 'MIT' license for all new projects. The existing license approval policy allows MIT. What is the correct update?

Edit the policy to remove MIT from the allowed list and add it to the denied list.

Change the action of the existing policy to 'warn' for MIT.

Create a new policy that denies MIT, leaving the old policy in place.

Delete the existing policy and create a new one that denies MIT.

GitLabCertified Security Associate

Domain 6Objective 2

Manage License Approval Policies GITLAB-CERTIFIED-SECURITY-SPECIALIST Practice Questions (Page 1)

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

20questions here

4free pages

7concepts

Questions 1–5

1foundation · easy
When creating a license approval policy in GitLab, what must you specify to define the policy?
Select an answer first
2foundation · easy
In GitLab, where do license approval policies apply by default?
Select an answer first
3foundation · easy
When does GitLab enforce a license approval policy during a merge request?
Select an answer first
4expert · hard
A security analyst reviews the license compliance report of a merge request and sees a license marked as 'not approved'. The policy action is 'warn'. What should the analyst do next?
Select an answer first
5application · medium
A company's legal team has decided to deny the 'MIT' license for all new projects. The existing license approval policy allows MIT. What is the correct update?
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.