A large organization wants to enforce a custom secret detection rule across all projects in a group. They also want to allow individual projects to override the rule's severity. What is the most efficient way to achieve this?

Add the rule to the predefined rules in the GitLab instance.

Create a group-level ruleset and reference it in each project's `secret_detection` job.

Create a separate project that contains the ruleset and use it as a template in all projects.

Use the GitLab UI to add the rule to the group's security settings.

What is the primary purpose of GitLab secret detection in the security scanning suite?

To analyze application code for security flaws

To monitor running applications for security threats

To identify hardcoded secrets such as API keys and passwords in the repository

To scan container images for known vulnerabilities

A project uses a monorepo with multiple services. The team wants to run secret detection only for the `auth-service` directory to reduce scan time. What should they do?

Use the `only` keyword with `changes` to run the job only when files in `auth-service` change.

Set a CI/CD variable `SECRET_DETECTION_PATHS` to `auth-service`.

Create a separate project for `auth-service` and enable secret detection there.

Add a `paths` rule to the `secret_detection` job to include only `auth-service/**`.

Which configuration option allows you to add a custom secret detection rule?

The `SECRET_DETECTION_EXCLUDED_PATHS` CI/CD variable

The `SECRET_DETECTION_LOG_LEVEL` CI/CD variable

The `SECRET_DETECTION_HISTORIC_SCAN` CI/CD variable

A `ruleset` file in the project

How can you permanently reduce false positives for a specific pattern in secret detection?

Increase the `SECRET_DETECTION_TIMEOUT` variable

Disable secret detection for the entire project

Add the pattern to the ruleset as an exception

Use the `SECRET_DETECTION_EXCLUDED_PATHS` variable to exclude the file

GitLabCertified Security Associate

Domain 2Objective 1

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

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

24questions here

5free pages

6concepts

Questions 16–20

16expert · medium
A large organization wants to enforce a custom secret detection rule across all projects in a group. They also want to allow individual projects to override the rule's severity. What is the most efficient way to achieve this?
Select an answer first
17foundation · easy
What is the primary purpose of GitLab secret detection in the security scanning suite?
Select an answer first
18application · medium
A project uses a monorepo with multiple services. The team wants to run secret detection only for the `auth-service` directory to reduce scan time. What should they do?
Select an answer first
19foundation · easy
Which configuration option allows you to add a custom secret detection rule?
Select an answer first
20foundation · easy
How can you permanently reduce false positives for a specific pattern in secret detection?
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.