Which of the following is NOT a technical design consideration for a TAA?

Question

Options

• AThe number of users for the SUT
• BAvailability of interfaces for the SUT to be testable
• CStandards and Legal requirements, e.g data privacy
• DData used by the SUT, e.g configuration, users

• A
  89% (31)
• B
  6% (2)
• C
  3% (1)
• D
  3% (1)

Explanation

Option A is correct because the number of users for the SUT is a characteristic of the System Under Test itself - relevant to performance/load testing goals - but it does not influence how you architect the Test Automation Architecture (TAA). The TAA is concerned with how you build the automation framework, not the SUT's user volume.

Why the distractors are wrong (i.e., they ARE genuine TAA design considerations):

• B - Knowing which interfaces (API, UI, DB) are available on the SUT directly shapes what tools and layers you can build your TAA around.
• C - Legal and data privacy standards (e.g., GDPR) constrain how you handle test data, requiring specific design choices in the TAA.
• D - The type and structure of data the SUT depends on (config files, user records) must be accounted for in the TAA's test data management design.

Memory tip: Think of TAA design considerations as anything that shapes how you build the automation - interfaces let you hook in, data tells you what to manage, standards set constraints. User count is a SUT metric, not an automation architecture driver - it would belong in a performance test plan, not a TAA.

No community discussion yet for this question.