A team notices that secret detection is flagging a large number of false positives for a custom rule they added. They want to reduce the noise without disabling the rule entirely. What should they do?

Increase the `SECRET_DETECTION_TIMEOUT` variable.

Add the rule to a 'disabled' list in the ruleset.

Adjust the rule's regular expression to be more specific.

Change the rule's severity to 'Info'.

A developer wants to prevent secret detection from blocking a merge request for a known false positive that appears in a test fixture file. They want to allow the merge to proceed without dismissing the finding. What should they do?

Disable the entire secret detection job for the merge request pipeline.

Add a `skip` comment to the merge request.

Set the rule's severity to 'Info' so it doesn't block the merge.

Add the file to the ruleset's `exclude` paths.

What is the recommended action when secret detection reports a false positive?

Delete the entire project to remove the finding

Change the secret to a different value

Dismiss the finding with a comment explaining why it is a false positive

Ignore the finding and leave it unresolved

How can a user enable secret detection for a project in GitLab?

By enabling the 'Secret Detection' toggle in the project's General settings

By creating a new project with the 'Security Scanner' template

By adding a `secret_detection` job to the `.gitlab-ci.yml` file

By installing a GitLab Runner on the local machine

GitLabCertified Security Associate

Domain 2Objective 1

Configure Secret Detection GITLAB-CERTIFIED-SECURITY-SPECIALIST Practice Questions (Page 3)

Part of the Secret and Dependency Scanning domain, which makes up ~21% of our current practice bank.

24questions here

5free pages

6concepts

Questions 11–15

11application · medium
A team notices that secret detection is flagging a large number of false positives for a custom rule they added. They want to reduce the noise without disabling the rule entirely. What should they do?
Select an answer first
12application · medium
A developer wants to prevent secret detection from blocking a merge request for a known false positive that appears in a test fixture file. They want to allow the merge to proceed without dismissing the finding. What should they do?
Select an answer first
13foundation · easy
Where can you view secret detection findings in GitLab?
Select an answer first
14foundation · easy
What is the recommended action when secret detection reports a false positive?
Select an answer first
15foundation · easy
How can a user enable secret detection for a project in GitLab?
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.