What is the primary source of information for deriving API test cases?

The API documentation and specification

A team is testing a REST API that manages user profiles. The OpenAPI specification defines a POST /users endpoint with a required 'email' field and an optional 'nickname' field. The team wants to verify that the API correctly rejects requests that violate the schema. Which test case design approach best targets this requirement?

Send a request with a valid email but omit the 'nickname' field, then verify a 200 response.

Send a request missing the 'email' field and another with an invalid email format, then verify appropriate 4xx responses.

Send a request with a valid email and nickname, then verify a 201 response.

Send a request with an extra unknown field 'age' and verify it is ignored.

In the context of white-box testing, what is the primary purpose of API testing?

To measure the performance of the application under a specific load by simulating multiple concurrent users

To validate the user interface and ensure that all graphical elements are displayed correctly

To verify the internal logic and data flow of the application by testing the interfaces between software components

To verify that the application meets the business requirements by testing the end-to-end workflows through the user interface

Which scenario is an example of API integration testing?

Measuring the response time of the API under a specific load

Sending a request to a single endpoint and verifying the response format

Checking the API documentation for accuracy

Verifying that the API correctly retrieves data from a database and returns it to the client

A team is integrating a new payment API with an existing order API. The payment API is a third-party service with a sandbox environment. The team wants to automate integration tests in CI. Which approach best balances realism and reliability?

Use the sandbox environment for integration tests and mock the payment API in unit tests.

Use the production payment API for integration tests to ensure real behavior.

Run integration tests only manually, not in CI.

Mock the payment API in all tests, including integration tests.

Certified Tester Advanced Level Technical Test Analyst

Domain 2Objective 7

API Testing CTAL-TTA Practice Questions (Page 3)

Part of the Domain 2: White-Box Test Techniques domain, which makes up ~19% of our current practice bank. ISTQB does not publish an official question count, but from its 120-minute exam (~50–80 total, ~10–15 in this domain), expect 1–2 from this objective — we provide 25 practice questions to prepare you well beyond it. (estimate)

25questions here

5free pages

8concepts

Questions 11–15

11foundation · easy
What is the primary source of information for deriving API test cases?
Select an answer first
12application · medium
A team is testing a REST API that manages user profiles. The OpenAPI specification defines a POST /users endpoint with a required 'email' field and an optional 'nickname' field. The team wants to verify that the API correctly rejects requests that violate the schema. Which test case design approach best targets this requirement?
Select an answer first
13foundation · easy
In the context of white-box testing, what is the primary purpose of API testing?
Select an answer first
14foundation · easy
Which scenario is an example of API integration testing?
Select an answer first
15expert · hard
A team is integrating a new payment API with an existing order API. The payment API is a third-party service with a sandbox environment. The team wants to automate integration tests in CI. Which approach best balances realism and reliability?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CTAL-TTA

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by ISTQB. “CTAL-TTA” is a trademark of its owner, used for identification only.