Skip to main content
ITPrepCerts
Login
Exams Free Samples About Contact
Login Create an account

CTAL-TAE ISTQB Certified Tester Advanced Level, Test Automation Engineering

  • iSQI
  • 5 free sample questions

About this exam

CTAL-TAE is the iSQI exam ISTQB Certified Tester Advanced Level, Test Automation Engineering. Paid practice material for this exam is not available yet, but you can try its free sample questions.

Exam code
CTAL-TAE
Vendor
iSQI
Practice questions
Not available yet
Free sample questions
5
Question bank last updated
Not available yet

Try 2 sample questions

Taken from the free sample set for CTAL-TAE.

Question 1

Some automated regression test scripts run by a TAS in a given test environment make calls to private APIs that require authentication for all requests (the authentication method is the same for all APIs). The SUT is a business-critical system. The following two changes are planned: a change in the authentication method of all APIs and a minor upgrade of the OS (Operating System) in the test environment. You have updated the test scripts to cope with the change in the API authentication method. Which of the following sequences of activities is BEST to ensure that the test scripts are not adversely affected by these changes?

  1. Option A:

    First upgrade the OS, then implement the change in the API authentication method, and finally run all the updated test scripts

  2. Option B:

    Implement one change at a time and run a subset of the updated test scripts after each change, and finally run all the

    updated test scripts

  3. Option C:

    First implement the change in the API authentication method, then upgrade the OS, and finally run all the

    updated test scripts

  4. Option D:

    Implement one change at a time and run a subset of the updated test scripts after each change

Show answer and explanation

Correct answer: B

TAE recommends controlled change management to isolate causes when multiple changes are introduced. When you apply more than one change at once, diagnosing failures becomes harder because you cannot easily attribute effects to a specific change. The best practice is to implement changes incrementally, validating automation and system behavior after each change using a representative subset of tests (e.g., smoke/build verification or targeted regression) to quickly detect issues. Because the system is business-critical, risk mitigation is stronger: you want early detection and clear attribution. After each change is validated with a subset, you then execute the full updated regression suite to ensure overall coverage and confidence. Options A and C apply two changes before running tests, which reduces diagnostic clarity and increases the risk of late discovery. Option D describes incremental changes with subset testing but omits the final full-suite run, which TAE would recommend to ensure broad coverage after all changes have been applied. Therefore, the best sequence is: change one item, run a subset, repeat for the next change, then run all updated scripts.

Question 2

Which of the following statements about contract testing is TRUE?

  1. Option A:

    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

  2. Option 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

  3. Option C:

    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


  4. Option D:

    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

Show answer and explanation

Correct answer: C

TAE describes contract testing as verifying that two parties (e.g., consumer and provider services) adhere to an agreed interface contract, enabling earlier, more targeted detection of integration mismatches without requiring full end-to-end integration in every test run. A key distinction in approaches is indeed who defines/publishes the contract. In provider-driven contracts, the provider defines the contract describing what it offers; consumers validate compatibility against it. In consumer-driven contract testing, consumers define expectations (often per consumer), and providers verify they satisfy those expectations. Option A is false because stubs/mocks (or simulated counterparts) are frequently used to allow each side to test independently and deterministically, which is one of contract testing’s practical strengths. Option B is too narrow: contract testing can apply beyond REST (e.g., GraphQL, gRPC, messaging/event contracts). Option D is also too restrictive: it can apply to asynchronous interactions (events/messages) as well as synchronous calls. Therefore, the accurate statement is option C

See all 5 free sample questions