What is a common limitation of static security testing related to code coverage?

It may not analyze code that is dynamically generated or loaded at runtime.

It can only analyze code written in a single programming language.

It always analyzes 100% of the codebase, including third-party libraries.

It requires the entire application to be deployed to a test environment.

A company wants to ensure that all code merged into the main branch passes security checks. They have a CI/CD pipeline that runs builds and tests. Which integration approach would best enforce static security testing before code is merged?

Run static analysis manually on a weekly basis

Run static analysis only on release branches

Add a static analysis step to the CI pipeline that fails the build on critical findings

Use a pre-commit hook that only warns about issues

Certified Tester Security Test Engineer

Domain 9Objective 7

Understand the Usage and Concepts of Static Security Test Tools CT-STE Practice Questions (Page 3)

Part of the Security Test Tools domain, which makes up ~15% of our current practice bank. ISTQB does not publish an official question count, but from its 75-minute exam (~30–50 total, ~5–8 in this domain), expect 1–1 from this objective — we provide 12 practice questions to prepare you well beyond it. (estimate)

12questions here

3free pages

7concepts

Questions 11–12

11foundation · easy
What is a common limitation of static security testing related to code coverage?
Select an answer first
12application · medium
A company wants to ensure that all code merged into the main branch passes security checks. They have a CI/CD pipeline that runs builds and tests. Which integration approach would best enforce static security testing before code is merged?
Select an answer first

Finished these 2 questions?

Review the revealed explanations, or continue through the curriculum.

No more pagesBack to CT-STE

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 ISTQB. “CT-STE” is a trademark of its owner, used for identification only.

Understand the Usage and Concepts of Static Security Test Tools CT-STE Practice Questions (Page 3)

Questions 11–12

What is a common limitation of static security testing related to code coverage?

A company wants to ensure that all code merged into the main branch passes security checks. They have a CI/CD pipeline that runs builds and tests. Which integration approach would best enforce static security testing before code is merged?

Keep studying — Security Test Tools