Level of Automation CT-ATT Practice Questions (Page 4)

Questions 16–20

1. 16foundation · easy

   What is the main implication of the test automation pyramid for balancing automation effort?

   • AIntegration tests should be the largest group because they verify system interactions
   • BThe majority of tests should be end-to-end to validate real user scenarios
   • CAll levels should have an equal number of tests to ensure comprehensive coverage
   • DMost effort should go into fast, low-level tests, with fewer high-level end-to-end tests
   Reveal Solution Discussion Select an answer first
2. 17application · medium

   A team has a test automation suite with 500 unit tests, 50 integration tests, and 200 end-to-end tests. The end-to-end tests take over an hour to run and are frequently flaky. According to the test automation pyramid, what is the most likely problem?

   • AThe number of end-to-end tests is disproportionately high compared to the lower levels
   • BThe number of unit tests is too low to provide adequate coverage
   • CThe integration tests are not sufficient to catch integration issues
   • DThe team should replace all end-to-end tests with unit tests
   Reveal Solution Discussion Select an answer first
4. 18application · medium

   A team is developing a microservices-based application where each service has its own database. They want to automate tests to catch integration issues early. The team has limited time in the CI pipeline and wants to maximize the value of each test run. Which level of automation should they prioritize?

   • AUnit tests for each service that mock all other services and the database
   • BIntegration tests that verify interactions between two or more services using test doubles for external dependencies
   • CAcceptance tests that validate business rules through the user interface
   • DSystem-level end-to-end tests that exercise the full user journey across all services
   Reveal Solution Discussion Select an answer first
5. 19foundation · easy

   Which statement best describes the purpose of unit-level test automation?

   • ATo verify that individual components or modules work correctly in isolation
   • BTo check the interactions between integrated modules and external systems
   • CTo validate end-to-end business scenarios across the entire system
   • DTo confirm that the system meets business requirements from the user's perspective
   Reveal Solution Discussion Select an answer first
6. 20foundation · easy

   A team is automating tests for a system with complex user workflows and high business value. Which automation level should they focus on to maximize value?

   • AUnit-level automation, because it is the cheapest to create and maintain
   • BSystem-level automation, because it tests the entire system
   • CIntegration-level automation, because it checks data flow between components
   • DAcceptance-level automation, because it directly validates the workflows that matter to users
   Reveal Solution Discussion Select an answer first