Which of the following is an example of a security testing tool commonly used at the component level?

A project management tool for tracking test progress

A documentation tool for writing test reports

A fuzzing tool that sends malformed data to the component's interfaces

A performance monitoring tool that measures response times

Why is it important to document component-level security test designs in a structured manner?

To increase the number of test cases

To replace the need for automated testing

To satisfy regulatory requirements only

To facilitate communication among stakeholders and support future test maintenance

Which of the following best describes the scope of security test design at the component test level?

Testing individual components in isolation to verify their security functions and identify vulnerabilities

Testing the security of the entire application from an end-user perspective

Testing the interaction between multiple components to ensure secure data flow

Testing the security of the network infrastructure and firewalls

Which of the following is an example of a component-level security test case targeting input validation?

Verifying that the component's user interface is accessible

Testing the component's response time under normal load

Checking that the component's documentation is up to date

Sending a SQL injection payload in an input field to see if the component prevents the attack

A security test lead is reviewing the traceability matrix for a component. Several security risks have no corresponding test cases because the team ran out of time. What is the most appropriate action?

Assume the risks are low and do not mention them.

Remove the uncovered risks from the matrix to make the report look complete.

Document the uncovered risks in the final report and recommend follow-up testing.

Write test cases quickly without executing them.

Certified Tester Security Test Engineer

Domain 3Objective 3

Security Test Design at Component Test Level CT-STE Practice Questions (Page 4)

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

33questions here

7free pages

8concepts

8 Concepts in This Objective

Security Test Design at Component Level
Component-Level Security Test Objectives
Threat and Risk Analysis for Components
Security Test Design Techniques for Components
Security Test Cases for Components
Component Security Test Environment and Tools
Coverage and Traceability in Component Security Testing
Documentation and Reporting of Component Security Tests

Questions 16–20

16foundation · easy
Which of the following is an example of a security testing tool commonly used at the component level?
Select an answer first
17foundation · easy
Why is it important to document component-level security test designs in a structured manner?
Select an answer first
18foundation · easy
Which of the following best describes the scope of security test design at the component test level?
Select an answer first
19foundation · easy
Which of the following is an example of a component-level security test case targeting input validation?
Select an answer first
20expert · hard
A security test lead is reviewing the traceability matrix for a component. Several security risks have no corresponding test cases because the team ran out of time. What is the most appropriate action?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back 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.