A team wants to run secret detection with a custom ruleset that adds a new rule for a proprietary token format. They also want to keep the predefined rules. What should they do?

Add the custom rule directly to the predefined rules file.

Create a ruleset file and reference it in the `secret_detection` job using the `ruleset` variable.

Create a new job that runs a separate secret detection scan with the custom rule.

Use the `custom_rules` keyword in the `.gitlab-ci.yml` file.

A developer sees a secret detection finding in a merge request widget. The finding shows a token that looks like a real API key, but the developer knows it is a placeholder used in documentation. What is the most appropriate action?

Add the file to `.gitignore` to prevent future scans.

Disable the entire secret detection rule that flagged it.

Rotate the token immediately to be safe.

Dismiss the finding as a false positive with a comment explaining why.

How do predefined secret detection rules identify secrets?

By using machine learning to predict secret-like strings

By analyzing the code logic for secret usage

By checking if the secret is valid by connecting to external services

By matching patterns for known secret formats

What can be done to manage the severity of a secret detection finding?

Adjust the severity in the ruleset

Use the `severity` field in the `.gitlab-ci.yml` job

Modify the project's security level in settings

Change the `SECRET_DETECTION_SEVERITY` CI/CD variable

A security analyst wants to increase the severity of a predefined secret detection rule for AWS access keys from 'Critical' to 'Blocker' so that merge requests are blocked when such a key is found. What should they do?

Edit the predefined rule in the GitLab UI to change its severity.

Use the `severity` keyword in the `secret_detection` job definition.

Create a custom ruleset that overrides the rule's severity to 'Blocker'.

Add a CI/CD variable `SECRET_DETECTION_SEVERITY` to set the severity.

GitLabCertified Security Associate

Domain 2Objective 1

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

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

24questions here

5free pages

6concepts

Questions 6–10

6application · medium
A team wants to run secret detection with a custom ruleset that adds a new rule for a proprietary token format. They also want to keep the predefined rules. What should they do?
Select an answer first
7application · medium
A developer sees a secret detection finding in a merge request widget. The finding shows a token that looks like a real API key, but the developer knows it is a placeholder used in documentation. What is the most appropriate action?
Select an answer first
8foundation · easy
How do predefined secret detection rules identify secrets?
Select an answer first
9foundation · easy
What can be done to manage the severity of a secret detection finding?
Select an answer first
10application · medium
A security analyst wants to increase the severity of a predefined secret detection rule for AWS access keys from 'Critical' to 'Blocker' so that merge requests are blocked when such a key is found. What should they do?
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.