
Certified Tester Security Test Engineer
Domain 9Objective 7
Understand the Usage and Concepts of Static Security Test Tools CT-STE Practice Questions (Page 1)
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 1–5
- 1
A static analysis tool reports a high-severity vulnerability in a module that is rarely used and has no external input. The security team is concerned about the tool's accuracy. What is the most likely explanation for this finding?
Select an answer first - 2
A development team wants to reduce the number of security issues found during code review. They plan to introduce a static analysis tool. What is the most effective way to ensure developers use the tool and benefit from it?
Select an answer first - 3
Why can configuration issues be a challenge for static security testing?
Select an answer first - 4
A security team is evaluating tools for a web application that uses a mix of server-side Java and client-side JavaScript. They need to identify vulnerabilities that only manifest when the application is running, such as authentication bypasses that depend on runtime state. They also want to minimize false positives. Which approach is most appropriate?
Select an answer first - 5
A security test engineer is selecting a tool to automatically detect common coding mistakes, such as unused variables, potential null-pointer dereferences, and style violations, in a large codebase during development. Which type of static security tool is most appropriate for this task?
Select an answer first
Finished these 5 questions?
Review the revealed explanations, or continue through the curriculum.
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.