Remediate Detected Findings GITLAB-CERTIFIED-SECURITY-SPECIALIST Practice Questions (Page 2)

Questions 6–10

1. 6foundation · easy

   Which GitLab feature is specifically designed to help track and manage security findings across a project?

   • AMerge Request Approval Rules
   • BSecurity Dashboard
   • CContainer Registry
   • DIssue Board
   Reveal Solution Discussion Select an answer first
2. 7foundation · easy

   A developer has just received a security alert for a detected secret in a merge request. According to GitLab's standard remediation workflow, what is the FIRST step the developer should take?

   • AReview the finding details, confirm it is a real secret, and then plan the appropriate fix
   • BDisable the secret detection scanner for the project
   • CImmediately delete the branch and create a new merge request
   • DMerge the merge request immediately to avoid blocking the pipeline
   Reveal Solution Discussion Select an answer first
4. 8expert · hard

   A security scan on a large monorepo reports 50 dependency findings. 45 are in development-only tooling with CVSS scores below 4.0. Three are in a production-facing API with CVSS scores of 7.5, 8.1, and 9.0. Two are in a rarely-used internal admin tool with CVSS scores of 6.5. The team has limited capacity this sprint. What is the most appropriate prioritization strategy?

   • AMark all 50 findings as false positives to clear the backlog
   • BFix the three production API findings first, then the two admin tool findings, and defer the dev-tooling ones
   • CFix the 45 dev-tooling findings first because they are more numerous
   • DFix all 50 findings in this sprint to eliminate all risk
   Reveal Solution Discussion Select an answer first
5. 9foundation · easy

   A dependency scanning finding reports a vulnerable version of a library. What is the recommended remediation action?

   • AIgnore the finding because it is a transitive dependency
   • BUpgrade the library to a patched version
   • CRemove the library from the project entirely
   • DChange the package manager to avoid the vulnerability
   Reveal Solution Discussion Select an answer first
6. 10expert · hard

   A critical vulnerability is found in a shared library used by five different projects. The fix requires a coordinated upgrade across all projects. The security team wants to ensure the remediation is tracked and completed. What is the most effective approach?

   • ACreate a single issue in one project and fix all others silently
   • BSend an email to all project maintainers asking them to upgrade
   • CCreate one issue in each project and link them to a parent epic
   • DDisable the shared library until all projects are upgraded
   Reveal Solution Discussion Select an answer first