API Testing CT-QDO Practice Questions (Page 2)

Questions 6–10

1. 6application · medium

   A team is debating whether to invest in API testing or focus only on UI end-to-end tests. They want to validate business logic and data formats early in the development cycle. What is the strongest argument for API testing?

   • AAPI tests are faster and more stable than UI tests, allowing earlier detection of defects in business logic.
   • BAPI tests validate the user interface design and visual elements.
   • CAPI tests replace the need for any UI testing, saving all UI test effort.
   • DAPI tests are easier to write than UI tests, so they require no maintenance.
   Reveal Solution Discussion Select an answer first
2. 7application · medium

   A QA team wants to automate API tests for a REST API. They need a tool that supports scripting for complex assertions and can be version-controlled. Which tool is best suited?

   • AA GUI-based API client that does not support scripting
   • BA network monitoring tool that logs API traffic
   • CA load testing tool that only generates traffic
   • DREST Assured (Java library)
   Reveal Solution Discussion Select an answer first
4. 8application · medium

   A DevOps team is building a CI pipeline for a microservices-based application. They want to catch service integration issues as early as possible, before the UI is ready for end-to-end tests. Which approach best aligns with this goal?

   • ARun API tests against deployed services in a staging environment after the UI tests complete.
   • BExecute API tests in the CI pipeline immediately after the services are built and deployed to a test environment.
   • CDefer API testing until after the UI is available so that tests cover the full user journey.
   • DPerform only manual API testing during the release phase to ensure accuracy.
   Reveal Solution Discussion Select an answer first
5. 9application · medium

   A team is developing a REST API that will be consumed by multiple external partners. They need to ensure that changes to the API do not break existing clients. Which type of API testing should they prioritize?

   • AFunctional testing to verify business logic correctness
   • BPerformance testing to verify response times under load
   • CIntegration testing to verify interactions between services
   • DContract testing to verify that the API still conforms to the agreed interface
   Reveal Solution Discussion Select an answer first
6. 10expert · hard

   A team is testing an API that returns large JSON payloads. They notice that some tests fail only when the payload contains certain data combinations. What is the best practice to handle this?

   • AReduce the payload size in tests to simplify assertions.
   • BUse data-driven testing with a variety of payloads, including edge cases.
   • CRun tests only with the most common payload to save time.
   • DSkip tests that fail intermittently and focus on stable tests.
   Reveal Solution Discussion Select an answer first