ISQI ISTQB Certified Tester Advanced Level - Test Automation Engineering CTAL-TAE (Syllabus v2.0) - CTAL-TAE_V2무료 덤프문제 풀어보기

A. As a final activity, immediately before releasing the new build into production

B. As a first activity, before performing static source code analysis and before generating the new build

C. After deploying the new build to the test environment and before performing more extensive testing

D. After performing static analysis on the source code and before generating the new build

A. Has a lower level of intrusion than the alternative implementation, and therefore its test scripts are less likely to produce false positives

B. Has a higher level of intrusion than the alternative implementation, and therefore its test scripts are less likely to produce false positives

C. Has a lower level of intrusion than the alternative implementation, and therefore its test scripts are more likely to produce false positives

D. Has the same level of intrusion as the alternative implementation, and therefore the risk of test scripts producing false positives is the same in both cases

A. Contract testing can be viewed as a specialized form of API testing that can be applied to effectively and efficiently test integration between systems, but only if they interact synchronously

B. Contract testing can be viewed as a specialized form of API testing that can be applied to effectively and efficiently test integration between microservices, but only if they interact with REST APIs

C. Contract testing, regardless of the approach chosen (provider-driven or consumer-driven) does not need to rely on the creation of stubs/mocks since it is used to implement integration testing, not unit
/component testing

D. The differences between the two approaches to contract testing stem primarily from which side creates the contract: this creation is done by the provider for the provider-driven approach and by the consumer (s) for the consumer-driven approach

A. The specified root cause must be in the instability of the test environment, since no code has been changed

B. The specified root cause is a race condition that can be identified by also analyzing the log files of the test case, the SUT, and the TAF

C. Determining the specified root cause is certainly easier than if the automated test always fails (deterministic behavior)

D. Determining the specified root cause may require, in addition to the TAE, the support of others such as developers and system engineers

A. Static analysis tools do not generate false positives when attempting to detect security vulnerabilities within test automation code

B. Static analysis tools can help detect hard-coded credentials that expose sensitive information within test automation code

C. Static analysis tools can help detect the presence of repeated instances of code within test automation code

D. Static analysis tools can ensure there are no security vulnerabilities within test automation code