I85PREP
⌘ K
ISTQB CTAL-TAE study materials
ISTQB CTAL-TAE study resources

ISTQB CTAL-TAE practice questions

One question at a time. Build your ISTQB CTAL-TAE understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Test Automation Engineering (domain breakdown not enumerated in source)

In a keyword-driven test automation architecture, what is the primary responsibility of the keyword layer?

  1. To generate the test data required by the system under test
  2. To store the expected results of every test case in a database
  3. To execute the compiled production code directly against the database
  4. To hide the technical implementation of interactions behind business-readable action words Correct answer.

Explanation

The keyword layer abstracts low-level automation calls into reusable, business-readable action words so that test designers can compose test cases without touching technical implementation details. This separation improves maintainability and lets non-technical stakeholders review test intent.

Question 2Test Automation Engineering (domain breakdown not enumerated in source)

A team wants the same test logic to run against several browsers and operating system combinations. Which design approach best supports this with minimal duplication?

  1. Introduce a configuration-driven abstraction so the environment is selected at runtime Correct answer.
  2. Record separate scripts with a capture-replay tool for each platform
  3. Hard-code the browser choice in each test method
  4. Copy the test scripts per browser and maintain separate suites

Explanation

A configuration-driven abstraction decouples test logic from environment specifics, so the same scripts execute across browsers and operating systems by changing configuration rather than code. This reduces duplication and maintenance effort compared with per-platform copies.

Question 3Test Automation Engineering (domain breakdown not enumerated in source)

Which metric best indicates the maintainability of a test automation suite over time?

  1. The number of test cases executed per hour
  2. The count of defects found by the automation
  3. The percentage of automated tests that must be modified whenever the system under test changes Correct answer.
  4. The total lines of code in the automation framework

Explanation

Maintainability reflects how much effort is needed to keep tests aligned with the evolving system under test, so the proportion of tests requiring modification after changes is a direct indicator. High modification rates signal brittle, tightly coupled tests.

Question 4Test Automation Engineering (domain breakdown not enumerated in source)

What is the main purpose of a test automation framework's reporting component?

  1. To replace the need for test design
  2. To provision test environments automatically
  3. To consolidate execution results and provide actionable information to stakeholders Correct answer.
  4. To compile the application under test

Explanation

The reporting component aggregates results from test execution and presents them in a form stakeholders can act on, such as pass/fail summaries and defect evidence. It does not compile the application, design tests, or provision environments.

Question 5Test Automation Engineering (domain breakdown not enumerated in source)

In a data-driven approach, where should test input data and expected results ideally be stored?

  1. In the version control commit messages
  2. Inside the test script as literal values
  3. In external data sources separated from the test logic Correct answer.
  4. In the reporting module configuration

Explanation

Data-driven testing separates data from logic, storing inputs and expected results in external sources such as files or databases so the same script runs with many data sets. Embedding data in scripts reduces reuse and increases maintenance.

Question 6Test Automation Engineering (domain breakdown not enumerated in source)

What does a continuous integration pipeline typically trigger when new code is committed to the main branch?

  1. Automated build and execution of the regression automation suite Correct answer.
  2. Re-recording of all capture-replay scripts
  3. Manual review of every test script
  4. Deletion of previous test results

Explanation

Continuous integration automatically builds the application and runs the automated regression suite on each commit to provide fast feedback. This early feedback helps detect integration defects before they propagate.

Question 7Test Automation Engineering (domain breakdown not enumerated in source)

Which type of test is most appropriate to verify that a single automated test script behaves correctly independent of the application?

  1. A system integration test
  2. A performance test
  3. An acceptance test
  4. A unit test of the automation code itself Correct answer.

Explanation

Unit testing the automation code verifies that helper functions, page objects, and utilities behave correctly in isolation from the application. This catches framework defects early and prevents false results caused by faulty test code.

Question 8Test Automation Engineering (domain breakdown not enumerated in source)

Why is version control essential for automated test assets?

  1. It enables traceability, collaboration, and rollback of test code changes Correct answer.
  2. It removes the need for code reviews
  3. It guarantees that tests always pass
  4. It automatically fixes flaky tests

Explanation

Version control provides traceability of changes, supports collaboration among team members, and allows rollback to earlier states when problems arise. It does not guarantee passing tests or fix flakiness by itself.

Question 9Test Automation Engineering (domain breakdown not enumerated in source)

A test suite passes when run alone but fails intermittently when run in parallel with other suites sharing a database. Which action best addresses the root cause?

  1. Increase the timeout values in all tests
  2. Reorder the tests alphabetically
  3. Disable parallel execution permanently
  4. Isolate test data per test execution to prevent interference Correct answer.

Explanation

Intermittent failures under parallel execution often stem from shared state, such as a common database, where tests interfere with each other. Isolating data per execution removes the interference and makes results deterministic.

Question 10Test Automation Engineering (domain breakdown not enumerated in source)

What is the most effective way to handle a test that fails because an element is not yet visible due to asynchronous loading?

  1. Ignore the failure in the report
  2. Use explicit waits that poll for the expected condition Correct answer.
  3. Reduce the application's loading time
  4. Insert a fixed sleep of ten seconds before every interaction

Explanation

Explicit waits poll for a specific condition, such as element visibility, and proceed as soon as it is met, making tests both faster and more reliable than fixed delays. Fixed sleeps waste time and remain fragile if timing varies.

Question 11Test Automation Engineering (domain breakdown not enumerated in source)

Which design pattern best reduces duplication when many automated tests interact with the same screen?

  1. Singleton pattern applied to every class
  2. Page Object pattern encapsulating screen elements and behaviors Correct answer.
  3. Observer pattern for logging
  4. Factory pattern for generating random data

Explanation

The Page Object pattern encapsulates a screen's elements and behaviors in a dedicated class, so tests call reusable methods instead of repeating locators. When the screen changes, only the page object needs updating.

Question 12Test Automation Engineering (domain breakdown not enumerated in source)

A team measures automation ROI. Which combination of factors should the analysis include?

  1. The number of testers on the team only
  2. The size of the application's codebase only
  3. Only the initial tool license cost
  4. Development and maintenance effort versus manual execution effort saved Correct answer.

Explanation

Automation ROI compares the total cost of building and maintaining automation with the effort saved by replacing manual execution over time. Ignoring maintenance or savings produces a misleading picture.

Question 13Test Automation Engineering (domain breakdown not enumerated in source)

What is the primary risk of automating tests at too low a level of abstraction?

  1. Tests become tightly coupled to implementation details and break frequently Correct answer.
  2. Test results become impossible to report
  3. Tests can no longer be version controlled
  4. Tests execute too slowly to be useful

Explanation

Low-abstraction tests that reference implementation specifics are brittle and break whenever the underlying implementation changes, even if behavior is unchanged. Higher abstraction focuses tests on behavior and improves resilience.

Question 14Test Automation Engineering (domain breakdown not enumerated in source)

In a behavior-driven development approach, which artifact bridges business requirements and automated tests?

  1. Executable specifications written in a business-readable format Correct answer.
  2. A network topology diagram
  3. A compiled binary
  4. A database schema

Explanation

BDD uses executable specifications written in a business-readable format that both stakeholders and automation can understand, aligning tests with requirements. These specifications serve as living documentation and drive automation.

Question 15Test Automation Engineering (domain breakdown not enumerated in source)

Which practice best supports the long-term maintainability of test data used by automated suites?

  1. Using production customer data directly without anonymization
  2. Defining reusable, versioned data sets with clear ownership Correct answer.
  3. Embedding data in each test script
  4. Generating data randomly without constraints

Explanation

Reusable, versioned data sets with clear ownership can be updated centrally and traced, which keeps tests maintainable. Unconstrained or embedded data leads to duplication and hard-to-diagnose failures.

Question 16Test Automation Engineering (domain breakdown not enumerated in source)

When selecting a test automation tool, which criterion is most directly related to the exam's emphasis on integration with the existing toolchain?

  1. The vendor's marketing material quality
  2. The number of features listed on the website
  3. The tool's default color scheme
  4. Compatibility with version control, CI, and defect tracking systems Correct answer.

Explanation

Tool selection should consider how well the tool integrates with version control, continuous integration, and defect tracking so automation fits the existing workflow. Poor integration increases manual effort and friction.

Question 17Test Automation Engineering (domain breakdown not enumerated in source)

A regression suite takes six hours, delaying feedback. Which strategy most directly improves feedback time without reducing coverage?

  1. Running the suite less frequently
  2. Removing the slowest tests permanently
  3. Parallelizing execution across multiple agents Correct answer.
  4. Increasing the timeout on each test

Explanation

Parallelizing execution across multiple agents distributes the workload and shortens total runtime while preserving coverage. Removing tests or reducing frequency sacrifices coverage or feedback cadence.

Question 18Test Automation Engineering (domain breakdown not enumerated in source)

Which statement best describes the role of a test harness in automation?

  1. It designs the test cases automatically
  2. It replaces the system under test during execution
  3. It provides the infrastructure to execute tests and capture results Correct answer.
  4. It guarantees defect-free software

Explanation

A test harness supplies the infrastructure, including drivers, stubs, and result capture, needed to execute tests consistently. It supports execution but does not replace the system under test or design tests.

Question 19Test Automation Engineering (domain breakdown not enumerated in source)

An automated test passes locally but fails in the CI environment because of a hard-coded absolute file path. Which change best resolves this?

  1. Run the test only on developer machines
  2. Add a retry loop around the failing step
  3. Externalize the path into environment-specific configuration Correct answer.
  4. Increase the machine's disk space

Explanation

Hard-coded absolute paths break when the environment differs, so externalizing paths into configuration makes the test portable across environments. Retries or hardware changes mask the underlying portability defect.

Question 20Test Automation Engineering (domain breakdown not enumerated in source)

What distinguishes a smoke test suite in an automation pipeline?

  1. It verifies every business rule in depth
  2. It replaces regression testing entirely
  3. It measures application performance under load
  4. It provides a fast, shallow check that critical functionality is available before deeper testing Correct answer.

Explanation

A smoke suite is a fast, shallow check confirming that critical functionality is available, acting as a gate before deeper suites run. It does not provide exhaustive verification or performance measurement.

Question 21Test Automation Engineering (domain breakdown not enumerated in source)

A team observes that 20 percent of automated tests fail intermittently with no application change. Which analysis approach is most appropriate first?

  1. Ignore the failures as noise
  2. Classify failures by cause, such as timing, data, or environment, before remediation Correct answer.
  3. Delete the flaky tests immediately
  4. Increase all timeouts uniformly

Explanation

Flaky tests have varied root causes, so classifying failures by cause guides targeted remediation rather than blanket fixes. Deleting or ignoring tests loses coverage and hides real defects.

Question 22Test Automation Engineering (domain breakdown not enumerated in source)

When designing an automation framework for reuse across multiple projects, which consideration most affects long-term cost?

  1. The number of comments in the code
  2. The balance between shared reusable components and project-specific customization Correct answer.
  3. The choice of programming language font
  4. The frequency of team meetings

Explanation

Reusable frameworks must balance shared components with project-specific needs; over-generalization creates complexity, while under-generalization forces duplication. This balance drives long-term maintenance cost.

Question 23Test Automation Engineering (domain breakdown not enumerated in source)

An organization wants to shift automation left. Which practice aligns best with that goal?

  1. Integrating automated checks into the earliest development stages and CI pipeline Correct answer.
  2. Outsourcing all testing to a separate team after deployment
  3. Running all automated tests only after release
  4. Reducing test coverage to speed up releases

Explanation

Shifting left means integrating automated checks early in development and CI so defects are found sooner, when they are cheaper to fix. Post-release or outsourced late testing contradicts the shift-left principle.

Question 24Test Automation Engineering (domain breakdown not enumerated in source)

A test automation strategy must decide which tests to automate first. Which criterion is most defensible?

  1. Prioritize high-value, frequently executed, stable tests with clear expected results Correct answer.
  2. Automate the tests that are easiest to script regardless of value
  3. Automate tests in reverse alphabetical order
  4. Automate only tests that manual testers dislike

Explanation

Prioritizing high-value, frequently executed, stable tests with clear expected results maximizes return and reduces risk of brittle automation. Ease of scripting alone or arbitrary ordering ignores business value.

Question 25Test Automation Engineering (domain breakdown not enumerated in source)

Which situation most strongly justifies NOT automating a test?

  1. The test is executed on every build
  2. The test is part of a frequently run regression suite
  3. The test has stable, well-defined expected results
  4. The test requires subjective human judgment of visual aesthetics Correct answer.

Explanation

Tests requiring subjective human judgment, such as aesthetic evaluation, are poor automation candidates because expected results cannot be reliably encoded. Frequent, stable, well-defined tests are strong automation candidates.

Question 26Test Automation Engineering (domain breakdown not enumerated in source)

In the TAA (Test Automation Architecture) layer model, which layer is responsible for providing reusable low-level functions such as launching the application, connecting to a database, or reading a file?

  1. The test definition layer
  2. The test execution layer
  3. The test adaptation layer Correct answer.
  4. The test generation layer

Explanation

The test adaptation layer exposes the SUT and its interfaces as reusable services, hiding technical detail from higher layers. Generation and definition layers build on these services rather than implementing low-level access.

Question 27Test Automation Engineering (domain breakdown not enumerated in source)

A team adopts a keyword-driven approach in its automation framework. Which statement best describes the primary benefit this approach delivers?

  1. Defects in the SUT are detected earlier because keywords execute before the application starts
  2. Test data is no longer required because keywords embed their own inputs
  3. Test logic can be expressed by non-programmers using domain keywords separated from the automation code Correct answer.
  4. Test execution time is reduced because keywords are compiled into native machine code

Explanation

Keyword-driven testing separates the test specification (keywords and data) from the implementation of the automation, so domain experts can author and maintain test cases. It does not change execution speed, defect timing, or remove the need for test data.

Question 28Test Automation Engineering (domain breakdown not enumerated in source)

A test automation engineer is designing a framework that must support both a web UI and a REST API for the same business process. Which design choice best supports this requirement?

  1. Define business-level test cases once and bind them to separate interface-specific adapter implementations Correct answer.
  2. Duplicate the business test cases in two suites so each interface can evolve independently
  3. Automate only the API and treat the UI as untestable through automation
  4. Embed UI locators directly inside the business-level test steps so both interfaces share them

Explanation

Separating abstract business-level test definitions from interface-specific adapters lets the same test intent run against different interfaces. Duplication, abandoning the UI, or leaking locators into business steps all undermine maintainability and reuse.

Question 29Test Automation Engineering (domain breakdown not enumerated in source)

Which statement correctly distinguishes a test automation framework from a test automation tool?

  1. A tool encompasses multiple frameworks and orchestrates them
  2. A framework provides the structure, guidelines, and reusable components in which tools are applied to build and run tests Correct answer.
  3. A framework and a tool are synonyms in the ISTQB glossary and can be used interchangeably
  4. A framework is a commercial product while a tool is always open source

Explanation

A framework is the architectural and organizational scaffolding plus practices that guide how automation is built and maintained, while a tool is a specific software product used within it. The two concepts are related but not interchangeable.

Question 30Test Automation Engineering (domain breakdown not enumerated in source)

An automation team wants to reduce the effort of maintaining object locators when the UI changes. Which practice most directly addresses this goal?

  1. Increasing the number of assertions in each test script
  2. Running the full regression suite more frequently
  3. Centralizing locators in an object repository referenced by name Correct answer.
  4. Recording tests with the capture/replay tool for every new build

Explanation

An object repository stores locators in one place so a UI change is fixed once rather than in every script. More assertions, more frequent runs, and repeated recording do not reduce locator maintenance.

Question 31Test Automation Engineering (domain breakdown not enumerated in source)

A team is defining exit criteria for its automation project. Which criterion is most appropriate and measurable?

  1. The team feeling confident that automation is mature enough
  2. The total lines of automation code written
  3. A defined percentage of prioritized regression test cases automated and passing in the CI pipeline Correct answer.
  4. The number of automation tools evaluated during selection

Explanation

Good exit criteria are objective, measurable, and tied to coverage and quality goals, such as an agreed percentage of prioritized regression tests automated and green in CI. Feelings, tool counts, and code volume are not meaningful quality indicators.

Question 32Test Automation Engineering (domain breakdown not enumerated in source)

In a data-driven test automation approach, what is the primary role of the external data file?

  1. It records the execution log produced by the test runner
  2. It supplies input and expected-result values so one script can execute many test iterations Correct answer.
  3. It stores the compiled automation binaries used at run time
  4. It replaces the need for any test oracle in the suite

Explanation

Data-driven testing keeps the script logic fixed and iterates it over rows of input and expected values held externally. The data file does not hold binaries, remove the oracle, or serve as the execution log.

Question 33Test Automation Engineering (domain breakdown not enumerated in source)

A team wants automated tests to report failures with enough context to diagnose them quickly. Which practice best supports this?

  1. Log only a single pass or fail status per test case
  2. Capture logs only for tests that pass so failures stay uncluttered
  3. Log the executed step, input data, expected result, actual result, and a screenshot or message at the point of failure Correct answer.
  4. Rely on the developer to re-run the test manually to observe the failure

Explanation

Diagnosable failure reports capture the context of the failing step, the data used, and the expected versus actual outcome, often with a screenshot. Minimal status logging, manual re-runs, and logging only passes all delay or prevent diagnosis.

Question 34Test Automation Engineering (domain breakdown not enumerated in source)

Which metric best indicates the maintainability of an automated test suite over time?

  1. The number of testers on the automation team
  2. The proportion of test execution time spent on maintenance changes relative to new test development Correct answer.
  3. The total number of test cases in the suite
  4. The count of tools installed in the CI environment

Explanation

Maintainability is reflected in how much effort goes into keeping existing tests working versus adding value, so the share of effort spent on maintenance is a meaningful indicator. Raw counts of tests, staff, or tools say nothing about maintainability.

Question 35Test Automation Engineering (domain breakdown not enumerated in source)

A team must decide how to handle test results from an automated run. Which action aligns with good test management practice?

  1. Discard results when any test fails so the run stays clean
  2. Mark every discrepancy as a product defect without investigation
  3. Compare results against expected outcomes, classify discrepancies, and route them to the appropriate defect or triage process Correct answer.
  4. Report results only to the automation engineer and no one else

Explanation

Results must be evaluated against expected outcomes and discrepancies triaged, because a failure may be a product defect, a test defect, or an environment issue. Blindly logging defects, discarding results, or hiding them from stakeholders all break the feedback loop.

Question 36Test Automation Engineering (domain breakdown not enumerated in source)

Which characteristic is most important when evaluating a tool for automating tests of a legacy system that exposes only a proprietary terminal protocol?

  1. The tool's support for the latest web browser versions
  2. The tool's built-in mobile device farm
  3. The tool's graphical report theme options
  4. The tool's ability to extend or plug in custom interface adapters for that protocol Correct answer.

Explanation

When the SUT exposes an unusual interface, extensibility to add custom adapters is decisive because no standard driver will cover it. Browser support, a mobile farm, or report styling are irrelevant to a terminal-only legacy system.

Question 37Test Automation Engineering (domain breakdown not enumerated in source)

What is the main purpose of a pilot project when introducing test automation into an organization?

  1. To permanently replace manual testing across all teams
  2. To validate the chosen approach, tooling, and estimates on a limited scope before wider rollout Correct answer.
  3. To automate the entire regression suite before any stakeholder sees results
  4. To select the programming language for the product under test

Explanation

A pilot proves feasibility and calibrates effort, tooling, and process on a small, representative scope, producing evidence for a rollout decision. Automating everything up front, replacing all manual testing, or choosing the product language are not its purpose.

Question 38Test Automation Engineering (domain breakdown not enumerated in source)

A team maintains a large library of automated regression tests. Which approach best balances execution cost against defect detection in a CI pipeline?

  1. Run the entire regression suite on every commit regardless of duration
  2. Run a fast prioritized subset on every commit and the full regression suite on a scheduled or pre-release basis Correct answer.
  3. Run only the newest tests on every commit and never run the older ones
  4. Run tests manually whenever a developer remembers to do so

Explanation

Tiering the suite gives rapid feedback on each change while still achieving full coverage through scheduled or release-gated runs. Always running everything, ignoring older tests, or relying on memory all sacrifice either speed or coverage.

Question 39Test Automation Engineering (domain breakdown not enumerated in source)

Which statement best describes the concept of a test oracle in automated testing?

  1. A server that hosts the test execution environment
  2. A mechanism that determines whether an observed outcome is correct for a given input Correct answer.
  3. A repository that stores test scripts and data
  4. A tool that records and replays user interactions

Explanation

The oracle is whatever decides pass or fail by comparing actual results with expected results, whether a hard-coded value, a model, or a heuristic. Recording tools, execution hosts, and script repositories serve different purposes.

Question 40Test Automation Engineering (domain breakdown not enumerated in source)

A team is choosing between automating a test at the API level versus through the GUI. Which consideration most strongly favors the API level?

  1. The API level removes the need for any test data management
  2. The business logic can be verified with less coupling to presentation details that change frequently Correct answer.
  3. The GUI level cannot detect any functional defects
  4. The API level always produces more realistic user-facing results

Explanation

API-level tests exercise business logic without depending on volatile presentation layers, which reduces brittleness and often speeds execution. They are not inherently more user-realistic, the GUI can detect functional defects, and test data management is still required.

Question 41Test Automation Engineering (domain breakdown not enumerated in source)

Which element is essential in a test automation improvement process after each iteration?

  1. Freezing the framework so it never changes
  2. Reviewing automation results and lessons learned to adjust the framework and practices Correct answer.
  3. Removing all tests that ever failed to keep the suite green
  4. Adding more tools to the environment regardless of need

Explanation

Continuous improvement relies on retrospectives that examine results, defects in the tests themselves, and friction points, then feed concrete adjustments back into the framework and practices. Tool accumulation, deleting failures, or freezing the framework all block improvement.

Question 42Test Automation Engineering (domain breakdown not enumerated in source)

What distinguishes a test automation solution's 'transition' phase from its 'implementation' phase in a structured rollout?

  1. Implementation covers stakeholder training while transition covers coding
  2. The two phases are identical and can be merged without risk
  3. Transition is only about writing the first automated script
  4. Transition covers deploying the solution into operational use with training and process changes, while implementation builds it Correct answer.

Explanation

Implementation produces the framework and initial tests, whereas transition moves the solution into everyday use through training, process adaptation, and handover. Reducing transition to a first script or swapping the phases misrepresents both.

Question 43Test Automation Engineering (domain breakdown not enumerated in source)

Which practice best ensures that automated test scripts remain understandable to new team members?

  1. Writing each test as one long procedural block
  2. Avoiding all comments and documentation in the codebase
  3. Applying consistent naming conventions and structuring tests around clear business-level steps Correct answer.
  4. Using cryptic abbreviations to keep scripts short

Explanation

Readable automation uses meaningful names and expresses intent through clear business-level steps, so newcomers can understand and extend it. Abbreviations, absent documentation, and monolithic blocks all reduce comprehension.

Question 44Test Automation Engineering (domain breakdown not enumerated in source)

A framework uses a layered architecture. Why should test data be kept separate from test logic?

  1. It allows the same logic to run with different data sets and lets data be updated without editing scripts Correct answer.
  2. It guarantees that no defects will occur in the data
  3. It eliminates the need for assertions
  4. It makes the test scripts execute faster than compiled code

Explanation

Separating data from logic enables reuse across data sets and isolates changes, improving maintainability and coverage. It cannot guarantee defect-free data, remove assertions, or make interpreted scripts faster than compiled code.

Question 45Test Automation Engineering (domain breakdown not enumerated in source)

Which risk is most directly associated with relying on a single person as the sole expert for an automation framework?

  1. Reduced need for version control
  2. Increased execution speed of the test suite
  3. Loss of knowledge and stalled maintenance if that person leaves or is unavailable Correct answer.
  4. Automatic improvement in test coverage

Explanation

Concentrating framework knowledge in one individual creates a key-person risk that threatens continuity and maintenance. It does not speed execution, reduce the need for version control, or improve coverage.

Question 46Test Automation Engineering (domain breakdown not enumerated in source)

A team wants to verify that an automated test detects a defect when one is present. Which action best demonstrates this?

  1. Reduce the assertion count to speed up the run
  2. Increase the number of test steps in the script
  3. Run the test twice and confirm it passes both times
  4. Introduce a controlled fault into the SUT and confirm the relevant test fails as expected Correct answer.

Explanation

Fault injection checks the test's sensitivity by showing it fails when a defect exists, complementing the passing runs that show it accepts correct behavior. Repeated passing runs, longer scripts, and fewer assertions do not demonstrate defect detection.

Question 47Test Automation Engineering (domain breakdown not enumerated in source)

Which factor most strongly justifies automating a set of tests in a regulated environment where evidence of execution must be retained?

  1. The availability of a free trial of an automation tool
  2. The need for consistent, repeatable execution with auditable records of results Correct answer.
  3. The preference of one tester for scripting over manual execution
  4. The desire to reduce the number of test cases executed

Explanation

Regulated contexts demand repeatable execution and reliable, retained evidence, which automation provides through consistent runs and stored logs. Reducing test count, a tool trial, or individual preference are weak or inappropriate justifications.

Question 48Test Automation Engineering (domain breakdown not enumerated in source)

What is the primary purpose of a proof of concept in test automation tool selection?

  1. To benchmark the salary cost of automation engineers
  2. To evaluate whether a candidate tool can handle representative technical challenges of the SUT Correct answer.
  3. To replace the need for a pilot project entirely
  4. To finalize the production framework architecture for all teams

Explanation

A proof of concept tests a candidate tool against the specific technical obstacles the SUT presents, informing selection with evidence. It does not finalize enterprise architecture, substitute for a pilot, or address staffing costs.

Question 49Test Automation Engineering (domain breakdown not enumerated in source)

Which statement about the relationship between test automation and manual testing is most accurate?

  1. Automation is intended to eliminate all manual testing eventually
  2. Automation complements manual testing by handling repetitive, stable checks while humans focus on exploratory and judgment-based work Correct answer.
  3. Manual testing is obsolete once any automation exists
  4. Automation and manual testing cannot coexist in the same project

Explanation

Automation is best at repeatable, deterministic checks, while human judgment remains valuable for exploration, usability, and ambiguous situations. Claims that automation eliminates manual testing, renders it obsolete, or cannot coexist misstate the relationship.

Question 50Test Automation Engineering (domain breakdown not enumerated in source)

A team notices that its automated tests are tightly coupled to internal implementation details of the SUT. Which consequence is most likely?

  1. Tests become more robust and require less maintenance
  2. Test execution becomes independent of the SUT's internal structure
  3. Defect detection improves because tests mirror the code
  4. Tests break frequently due to refactoring even when behavior is unchanged, raising maintenance cost Correct answer.

Explanation

Coupling tests to internal structure means legitimate refactoring triggers failures unrelated to behavior changes, inflating maintenance. It does not improve robustness, decouple tests from internals, or reliably improve defect detection.