A team wants to run secret detection only on the default branch and not on feature branches to save pipeline time. They are using the standard `secret_detection` job. What should they do?

Set a CI/CD variable `SECRET_DETECTION_DISABLED` to `true` on feature branches.

Use the `only` keyword with `refs: [main]` in the job definition.

Create a separate pipeline for the default branch that includes secret detection.

Add a `rules` section to the `secret_detection` job to run only when the pipeline is on the default branch.

A security team is investigating a potential secret leak. The secret detection finding in the merge request shows a token, but the developer claims it is a test token that was rotated. The team wants to confirm whether the token is still active. What is the best way to verify?

Review the GitLab logs to see if the token was used.

Change the rule's severity to 'Info' to reduce the finding's importance.

Check the token against the service's API to see if it is still valid.

Dismiss the finding as a false positive because the developer rotated it.

A security team wants to create a custom rule that detects a specific internal token format. They also want to ensure that the rule does not flag tokens in test files. They have a ruleset file that defines the rule. What should they add to the ruleset?

Add a `paths` section to the rule that excludes `test/**`.

Add a `disabled` flag to the rule for test files.

Set the rule's `severity` to `Info` so it is less visible.

Create a separate ruleset for test files and apply it only to those files.

What is the purpose of a ruleset in GitLab secret detection?

To set the frequency of secret detection scans

To configure the output format of the scan results

To specify which branches to scan

To define custom rules for identifying secrets

GitLabCertified Security Associate

Domain 2Objective 1

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

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

24questions here

5free pages

6concepts

Questions 21–24

21application · medium
A team wants to run secret detection only on the default branch and not on feature branches to save pipeline time. They are using the standard `secret_detection` job. What should they do?
Select an answer first
22expert · medium
A security team is investigating a potential secret leak. The secret detection finding in the merge request shows a token, but the developer claims it is a test token that was rotated. The team wants to confirm whether the token is still active. What is the best way to verify?
Select an answer first
23expert · medium
A security team wants to create a custom rule that detects a specific internal token format. They also want to ensure that the rule does not flag tokens in test files. They have a ruleset file that defines the rule. What should they add to the ruleset?
Select an answer first
24foundation · easy
What is the purpose of a ruleset in GitLab secret detection?
Select an answer first

Finished these 4 questions?

Review the revealed explanations, or continue through the curriculum.

No more pagesBack 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.