Which of the following statements about fault seeding tools is correct?

• A. Fault seeding tools insert defects into the source code to test the input checking capabilities of the software.
• B. Fault seeding tools insert defects into the source code to support the application of specification-based test design techniques.
• C. Fault seeding tools insert defects into the source code to check the effectiveness of testing.
• D. Fault seeding tools insert defects into the source code to check the level of maintainability of the software.

Which of the following is a common technical issue that can result in an automation project failing?

• A. Not returning the system to a pre-defined state after completing the execution of a suite of automated tests
• B. Having to manually plan how to handle software failures in a test automation design
• C. Technical Test Analysts not developing business domain expertise for keyword-driven testing
• D. Automated tests uncovering a higher than expected rate of defects in the software under test

Which of the following statements about Application Programming Interface (API) testing is TRUE?

• A. Combinatorial testing cannot be applied to API testing
• B. APIs are loosely coupled, so timing glitches will not happen
• C. API testing cannot be applied to distributed systems
• D. API testing may require the use of specialized tools

You are a senior Technical Test Analyst on a new government project for the Air Force. The software you are testing is used to control the hydraulics for the landing gear for a supersonic, stealth aircraft. You are responsible for organizing the white-box testing that will be performed for this project.
Which of the following would be the most appropriate technique to apply in this situation?

• A. Maximum condition / multiple decision coverage
• B. Modified condition / decision coverage
• C. Multiple condition coverage
• D. Decision / condition coverage

A project to replace your company's sales and merchandising system has begun. The old system is still in production but is poorly documented and expensive to maintain: changing it has often produced a large quantity of defects. The new version will be developed using modern techniques and technology.
Requirements include:
* Loading sales data, sent electronically from the stores each evening, into a central database where it is then available for other applications.
* Producing sales reports for the merchandisers, whose job is to manage stock levels in stores.
* Predictions of future demand for each product, based on a combination of sales history and forecasting parameters.
Requirements 1 and 2 are satisfied by the existing system and will be rewritten with no significant changes.
Requirement 3 is new: these forecasting reports will be run overnight, and users will request them by entering simple parameters online during the day.
The sales data are loaded in an overnight batch run. There have been problems at peak periods when this run has taken longer than scheduled, so that dependent jobs could not finish before the start of the working day.
As a Technical Test Analyst, you have been asked to contribute to the project's Master Test Plan. The key stakeholders are:
* The Merchandising Manager, who wants parameter entry to be quick and easy.
* The Data Centre Manager, who requires the new batch jobs to take less time than the old ones.
No specific performance requirements have been given, either for the batch jobs or for online parameter entry.
Which TWO of the following will BEST meet the objectives of the stakeholders?

• A. Agree acceptance criteria for modifiability, modularity, and reusability, and measure these for change requests implemented after development begins.
• B. Conduct performance testing on the forecasting report parameter data entry features, in parallel with functional system testing.
• C. Conduct performance testing on the data load and report creation, in parallel with functional system testing.
• D. Agree acceptance criteria for performance of the forecasting report parameter data entry features, based on operational profile models.
• E. Agree acceptance criteria for performance of the data load and report creation, based on a quantified improvement over the current system.