A team wants to run container scanning on a schedule, not just on every pipeline. They have enabled container scanning in the project. What is the best way to achieve this?

Add a `schedule` to the container scanning job using the `rules` keyword.

Configure a cron job on the GitLab Runner to run the scan.

Use the Security Configuration UI to set a scan frequency.

Create a pipeline schedule that triggers a pipeline with a variable that includes the container scanning job.

In a container scanning report, what does the 'severity' field indicate?

The number of lines of code affected by the vulnerability

The potential impact of the vulnerability on the system

The likelihood that the vulnerability will be exploited in the wild

The importance of the affected component to the application

A team is new to GitLab and wants to start using container scanning. They have a project with a Dockerfile and a working pipeline. What is the first step they should take?

Upgrade to a paid GitLab tier that includes container scanning.

Enable container scanning in the Security Configuration UI.

Install a GitLab Runner with the Docker executor.

Create a new `.gitlab-ci.yml` file with a container scanning job.

A development team uses GitLab CI/CD to build a Docker image in the `build` job and push it to the project's container registry. The security team wants to add container scanning to the pipeline without requiring developers to modify their existing `.gitlab-ci.yml` files. Which approach should you recommend?

Create a new project and enable container scanning there, then import the image.

Install a GitLab Runner with the Docker executor and configure it to scan images.

Add a `container_scanning` job to the existing `.gitlab-ci.yml` that runs after the `build` job.

Enable container scanning via the Security Configuration UI in the project's settings.

Which of the following is a valid way to configure container scanning to run only on the main branch?

Set the 'CS_ANALYZER_IMAGE' variable to 'main'

Use the 'only: - main' keyword in the job definition

Add 'rules: - if: $CI_COMMIT_BRANCH == "main"' to the container scanning job

Set the 'SCAN_BRANCH' variable to 'main'

GitLabCertified Security Associate

Domain 3Objective 1

Implement Container Scanning GITLAB-CERTIFIED-SECURITY-SPECIALIST Practice Questions (Page 1)

Part of the Container Scanning domain, which makes up ~14% of our current practice bank.

27questions here

6free pages

7concepts

Questions 1–5

1application · medium
A team wants to run container scanning on a schedule, not just on every pipeline. They have enabled container scanning in the project. What is the best way to achieve this?
Select an answer first
2foundation · easy
In a container scanning report, what does the 'severity' field indicate?
Select an answer first
3application · medium
A team is new to GitLab and wants to start using container scanning. They have a project with a Dockerfile and a working pipeline. What is the first step they should take?
Select an answer first
4application · medium
A development team uses GitLab CI/CD to build a Docker image in the `build` job and push it to the project's container registry. The security team wants to add container scanning to the pipeline without requiring developers to modify their existing `.gitlab-ci.yml` files. Which approach should you recommend?
Select an answer first
5foundation · easy
Which of the following is a valid way to configure container scanning to run only on the main branch?
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.