CTAL-TAE

Free CTAL-TAE practice questions

10 questions from our CTAL-TAE practice tests, each with the correct answer and a written explanation. Read them with the answers shown, or switch to quiz mode and answer first.

Back to the CTAL-TAE practice exams

Question 1 of 10, Introduction and Objectives for Test Automation

A product owner expects that introducing automated regression tests will remove the need for any further manual testing. Which limitation of test automation should the test automation engineer (TAE) point out?

  1. AAutomated tests require the system under test to be fully complete before any test script can be developed
  2. BAutomated tests always run slower than manual tests, so they cannot provide feedback within a single two-week iteration
  3. CAutomated tests verify only the results they were programmed to check, so unexpected behavior can be missed Correct answer
  4. DAutomated tests cannot be executed more than once per build because their test data is consumed during the first run

Answer and explanation: Automation checks only what was scripted; it has no human judgment to notice unanticipated problems, so exploratory and other manual testing still add value. Repeatability is a strength of automation, not a limitation, and test data can be reset. Automated tests usually run faster than manual ones, and scripts can be developed in parallel with the SUT rather than only after completion.

Question 2 of 10, Preparing for Test Automation

A TAE analyzes a SUT that consists of a web front end, a REST back end, and a legacy mainframe batch job owned by another company. The batch job is available for testing only one day per month. What is the MOST appropriate decision for the test automation solution?

  1. AAutomate only the mainframe batch job with a dedicated tool, because it is the riskiest component, and keep testing the web and REST layers manually
  2. BAutomate all tests end to end through the web interface and schedule the complete suite for the monthly window when the mainframe batch job is available
  3. CPostpone automation of the whole system until the external company can provide a permanently available mainframe test environment for every scheduled test run
  4. DAutomate against the web and REST interfaces, virtualize the mainframe so tests run daily, and keep a few end-to-end tests for the monthly slot Correct answer

Answer and explanation: Analyzing the SUT includes identifying interfaces and dependencies that limit availability; virtualizing the unavailable mainframe enables frequent execution while a small number of real end-to-end tests still validates integration. Running everything only once a month destroys fast feedback. Waiting for a permanent environment blocks progress, and focusing only on the mainframe ignores the components the team can automate most efficiently.

Question 3 of 10, Test Automation Architecture

A page object class handles locating elements on the checkout page, calculating expected tax amounts, and writing results to the test report. Which SOLID principle is MOST clearly violated?

  1. AInterface segregation principle
  2. BDependency inversion principle
  3. CLiskov substitution principle
  4. DSingle responsibility principle Correct answer

Answer and explanation: The single responsibility principle states that a class should have only one reason to change; this class mixes page interaction, business calculation and reporting. Liskov substitution concerns subclasses being usable in place of base classes, interface segregation concerns clients not depending on methods they do not use, and dependency inversion concerns depending on abstractions rather than concrete implementations.

Question 4 of 10, Test Automation Architecture

A team writes test cases in a spreadsheet where each row contains an action word such as 'Login' or 'VerifyBalance' followed by its parameters. Testers without programming skills maintain the spreadsheet, while TAEs implement the action words. Which scripting approach is this?

  1. ACapture/playback
  2. BKeyword-driven testing Correct answer
  3. CData-driven testing with external data files
  4. DStructured scripting

Answer and explanation: Keyword-driven testing separates test design, expressed as sequences of keywords with parameters, from the implementation of those keywords, so non-programmers can create tests. Data-driven testing reuses one script with varying data rows but the actions are fixed in code. Structured scripting uses reusable libraries but tests are still written in code, and capture/playback records user interactions.

Question 5 of 10, Implementing Test Automation

Management expects the new TAS to cut the testing effort by 70% in the first release and has removed all manual testers from the plan. The TAEs estimate that only 30% of the regression tests can be automated in that time. Which risk should be raised and mitigated FIRST?

  1. AInsufficient test execution agents, mitigated by buying additional CI agents so that the 30% of automated tests can run more often during the release
  2. BPoor maintainability of the scripts, mitigated by introducing coding standards and peer reviews before any further automated tests are developed
  3. CTool licensing costs, mitigated by switching to an open-source tool so that the budget can be used to automate the remaining 70% of tests
  4. DUnrealistic expectations of automation benefits, mitigated by a staged automation roadmap and continued manual testing where needed Correct answer

Answer and explanation: The main risk is that expectations far exceed what automation can deliver, leaving untested areas once manual testers are removed; a staged roadmap with continued manual testing mitigates it. More agents, coding standards and switching tools may be useful but do not address the gap between expected and achievable automation.

Question 6 of 10, Implementation and Deployment Strategies for Test Automation

A provider team wants to verify consumer-driven contracts in its pipeline. Which practice is MOST appropriate?

  1. AGenerate the contracts from the provider's current implementation and publish them to consumers, so that consumers always match the provider
  2. BRetrieve the published consumer contracts, replay their requests against the provider build, and fail the build on any mismatch Correct answer
  3. CRun the consumers' end-to-end GUI test suites in the provider pipeline, so that every consumer workflow is exercised with each provider change
  4. DVerify the contracts manually before each major release, because automated contract verification cannot detect changes in response formats

Answer and explanation: In consumer-driven contract testing the provider verifies the published consumer contracts against its build and blocks changes that break them. Generating contracts from the provider reverses the approach and would not protect consumers, running consumers' GUI suites is slow and couples the pipelines, and contract verification is designed to be automated and detects format changes.

Question 7 of 10, Implementation and Deployment Strategies for Test Automation

Which statement BEST describes configuration management of testware in a test automation project?

  1. ATestware is archived as a zip file after each release, because version control systems are designed for production code rather than test code
  2. BTest scripts, test data, and environment configuration files are version-controlled together and linked to the SUT versions they support Correct answer
  3. COnly the test scripts are placed under version control, while test data and environment settings are kept locally by each TAE for flexibility
  4. DThe test management tool stores the latest version of each test case, which makes separate versioning of the automation code unnecessary for the team

Answer and explanation: Configuration management must cover all testware, including scripts, data and environment configurations, and relate it to SUT versions so that tests can be reproduced for any release. Keeping data and settings locally leads to inconsistent runs, zip archives lack traceable history, and a test management tool's latest test case does not version the automation code.

Question 8 of 10, Test Automation Reporting and Metrics

A failed automated test reports 'expected total 105.00 but was 100.00'. A TAE repeats the same steps manually and also gets 100.00. The requirements state that a 5% surcharge applies only on weekends, and the test ran on a Saturday. What is the MOST likely conclusion?

  1. AThe test script probably has a defect, because the manual repetition produced the same value as the automated test execution
  2. BThe SUT probably has a defect in applying the weekend surcharge, so a defect report with the logs and test data should be raised Correct answer
  3. CThe test environment probably has an incorrect time zone, so the test result should be ignored until the environment is checked
  4. DThe test is probably flaky, so it should be rerun several times and the majority result should be used as the final test outcome

Answer and explanation: Both automated and manual execution produce the value without the surcharge on a Saturday, while the requirement expects the surcharge, which points to a SUT defect. Agreement between manual and automated runs supports the test's correctness rather than indicating a script defect. A time zone problem is possible but would need evidence, and a consistent result is not flaky behavior.

Question 9 of 10, Verifying the Test Automation Solution

GUI tests pass on TAEs' machines but fail in the pipeline, where the browser runs headless with a small default window size. Elements are reported as not clickable. What is the MOST appropriate correction?

  1. ASet an explicit, consistent window size for all runs so the layout matches the conditions the tests were designed for Correct answer
  2. BAdd a retry to every click in the test scripts, so that the element can be clicked after the page has finished rendering
  3. CReport a defect against the SUT, because responsive layouts must make every element clickable at any window size
  4. DRun the pipeline tests with a visible browser on a TAE's workstation, because headless mode cannot be used for GUI tests

Answer and explanation: The difference is caused by environment configuration; setting an explicit window size makes runs consistent across machines. Headless browsers are widely used for GUI tests, retries do not change the layout that hides elements, and while responsive behavior can be tested deliberately, the immediate issue is the inconsistent test configuration.

Question 10 of 10, Continuous Improvement

A monolithic SUT is being split into microservices over the next year. The existing automated tests are mostly end-to-end GUI tests. Which restructuring of the testware is MOST appropriate?

  1. AKeep the existing GUI tests unchanged, because the user interface will hide the new architecture from the test automation
  2. BConvert all GUI tests into component tests of the monolith, because the services will reuse most of the existing code
  3. CAdd API and contract tests for each new service as it is extracted, and gradually reduce overlapping end-to-end GUI tests Correct answer
  4. DWait until all microservices are in production, and then rewrite the complete regression suite for the new architecture

Answer and explanation: As services are extracted, adding service-level and contract tests provides fast, targeted feedback, and overlapping GUI tests can be reduced over time. Relying only on GUI tests misses service-level risks, waiting a year leaves the transition poorly tested, and component tests of the monolith will not cover the new service boundaries.