Which of the following statements BEST describe aspects of the SUT to consider when designing a TAA?

Question

Options

• AAll the interaction between SUT and TAS should be logged with the highest level of detail
• BAll the internal test interfaces of the SUT should be removed prior to the product release
• CAll the interface of the SUT affected by the tests should be controllable by the TAA
• DAll the external test interfaces of the SUT should be removed prior to the product release

• A
  80% (43)
• B
  2% (1)
• C
  6% (3)
• D
  13% (7)

Explanation

Logging all SUT-TAS (Test Automation Solution) interactions at a high level of detail is a foundational TAA design principle because it enables traceability, supports root-cause analysis of test failures, and provides audit evidence - making A the best answer among the choices.

Why the distractors are wrong:

• B is incorrect because removing internal test interfaces before product release is not a universal rule - whether to keep or remove them depends on risk, security policy, and the specific architecture. Blanket removal could eliminate valuable diagnostic hooks.
• D is wrong for similar reasons: external test interfaces (e.g., public APIs used for test control) are often intentionally preserved post-release. Mandating their removal would be incorrect and counterproductive.
• C sounds plausible but overstates the requirement. Not every SUT interface affected by tests needs to be controllable by the TAA - some only need to be observable. Observability and controllability are distinct TAA concerns; demanding full control of all interfaces is too absolute.

Memory tip: Think of the TAA as a "flight recorder" for your tests - just as a black box logs everything for analysis, a well-designed TAA logs all SUT interactions in detail. When in doubt on TAA questions, favor observability and logging over sweeping statements about removing interfaces.

No community discussion yet for this question.