An automated test script makes a well-formed request to a REST API in the backend of a web app to add a single item for a product (with ID = 710) to the cart and expects a response confirming that the product is successfully added. The status line of the API response is HTTP/1.1 200 OK, while the response body indicates that the product is out of stock. The API response is correct, the test script fails but completes, and the message to log is: The product with ID = 710 is out of stock. Cart not updated. When this occurs, you are already aware that both the failed test and the API are behaving correctly and that the problem is in the test data. The TAS supports the following test logging levels: FATAL, ERROR, WARN, INFO, DEBUG. Which of the following is the MOST appropriate test logging level to use to log the specified message?

• A. DEBUG
• B. FATAL
• C. INFO
• D. WARN

Automated tests run by a TAS on a SUT can be subject to sudden bursts of messages to log during their execution. All log messages that occur during execution must be permanently stored in the corresponding test execution logs by the TAS for later analysis. If logging is not performed correctly, these bursts can reduce the execution speed of these automated tests, causing them to produce unreliable results. Which of the following solutions would you expect to be MOST useful to address this issue for TAS logging?

• A. Avoid logging the messages that occur during the specified bursts to minimize any potential performance overhead in test execution
• B. Log all the messages in memory using a circular buffer and periodically flush the buffer to the corresponding log files associated with the specific execution
• C. Use a Network Time Protocol (NTP) server to ensure that the clocks of the machines running TAS and SUT are synchronized with a common time source
• D. Log all the messages directly on the corresponding log files associated with the specific execution to ensure the permanent storage of test execution logs

A new TAS allows the implementation of automated data-driven test scripts. All the tasks planned for the initial deployment of this TAS, aimed at installing and configuring the TAS components and provisioning the infrastructure, will be performed manually by a dedicated, specialized team. This TAS is expected to be deployed in the future in other similar environments. As a TAE, you see a risk that the correct and reproducible deployment of the TAS cannot be guaranteed. Which of the following options is BEST suited for mitigating this risk?

• A. Partition the data tables containing test data used by data-driven test scripts into smaller data tables, using an appropriate logical criterion, to make them more manageable
• B. Nothing needs to be done, because the team that will manually perform the specified tasks, as they are specialized, will not make mistakes and will therefore be able to ensure a correct and reproducible deployment
• C. Try to automate most of the tasks related to the installation and configuration of the TAS components and those related to the provisioning of the infrastructure
• D. Review data-driven test scripts to better organize test libraries by adding test functions containing identical sequences of actions commonly implemented in a relevant number of scripts

(Which of the following statements refers to a typical advantage of test automation?)

• A. Automated tests can allow defects to be detected earlier than manual tests because their execution times can be shorter
• B. Automated tests can determine whether actual results match expected results, even for non-machine- interpretable results
• C. Artificial intelligence can be used to help identify redundant tests within large, long-running automated regression test suites
• D. On average, automated tests written at the API level are likely to run faster than automated tests written at the UI level