CTAL-TAE · Question #85
As a TAE you are evaluating a functional test automation tool that will be for several projects within your organization. The projects require that tool to work effectively and efficiently with…
The correct answer is C. b and e. Option C identifies b and e as the two least important concerns given the specific scenario constraints. The scenario emphasizes three critical requirements: distributed environment support, integration with existing tools, and resilience when those tools update. Concerns…
Question
As a TAE you are evaluating a functional test automation tool that will be for several projects within your organization. The projects require that tool to work effectively and efficiently with SUT's in distributed environments. The test automated tool also needs to interface with other existing test tools (test management tool and defect tracking tool.) The existing test tools subject to planned updates and their interface to the test automated tool may not work property after these updates. Which of the following are the two LEAST important concerns related to the evaluation of the test automation in this scenario?
Options
- Aa and c
- Ba and e
- Cb and e
- Dc and d
- EDoes the test automation tool need to install specific libraries that could impact the SUT?
How the community answered
(23 responses)- A17% (4)
- B9% (2)
- C65% (15)
- D4% (1)
- E4% (1)
Explanation
Option C identifies b and e as the two least important concerns given the specific scenario constraints. The scenario emphasizes three critical requirements: distributed environment support, integration with existing tools, and resilience when those tools update. Concerns mapped to items b (typically tool aesthetics/UI usability) and e (whether the tool installs libraries that could impact the SUT) are tangential to these priorities - a functional test tool operating externally to the SUT in a distributed setup doesn't inherently risk SUT stability through library installation, making that concern lower priority.
The distractors are wrong because options A and B both include "a," which typically relates to distributed environment compatibility - a core requirement explicitly stated in the scenario, so it is important. Option D includes "d," which relates to integration stability when tools are updated - directly relevant given the scenario warns about interface breakage after updates. These are among the most important concerns, not the least.
Memory tip: Think "DIST + INTEGRATE = critical." Anything directly supporting distributed operation or tool-to-tool integration is a top concern. What's left over - cosmetic features and indirect SUT side-effects - are your "least important" candidates. When the scenario spells out constraints explicitly, those constraints define what matters most.
Topics
Community Discussion
No community discussion yet for this question.