A system will be developed to support the administration of table-tennis tournaments. The following requirements for the enrolment of entrants have been provided:
R1. High. The administrator shall be able to enter the entrant's name, address, phone number/s (mobile and/or home), email and social media handles. Validation rules for these data items are provided separately.
R2. High. The administrator shall be able to enter the entrant's current world ranking (up to 250) and their relationship with the tournament sponsors (i.e. clothing / equipment / endorsement).
R3. High. The administrator shall be able to enter the entrant's attendance history at previous events (i.e.
finalist / played / withdrew during event / withdrew before event).
R4. Medium. From the entrant's address the system shall derive whether or not the entrant lives locally and, on the basis of that combined with other rules that are provided separately, shall suggest how much of the tournament's overall prize fund should be offered to the entrant as their individual attendance fee.
R5. Low. The administrator should be able to change the suggested attendance fee and the system should then deduct this from the remaining prize fund balance accordingly.
You have been asked to review the requirements using perspective-based reading, from your viewpoint as the TA who will be writing functional correctness system test cases. Assume that the other rules referred to by requirements R1 and R4 have been reviewed and are satisfactorily testable. Which conclusion would you reach?

• A. All of the requirements are fully testable
• B. Two of the requirements are not fully testable
• C. Three of the requirements are not fully testable
• D. One of the requirements is not fully testable

You are assigned to an Agile team as a Test Analyst. In most ways, the team seems to be working well.
Iteration planning goes smoothly because the user stories are good quality. Most defects that are found by testing are fixed in the same iteration and those that do go live are not causing significant dissatisfaction amongst stakeholders. However, the team is unhappy because the Defect Removal Efficiency rate, measured for each iteration, is less than 80%.
What would be the MOST effective contribution by you as a TA, to improve the situation?

• A. Reviewing requirements
• B. Defect data collection and evaluation
• C. Participating in root cause analysis
• D. Participating in retrospectives

You are working on a project to replace an old sales and merchandising system with a new system that will be based on modern platforms. The old system is still in production but is poorly documented and expensive to maintain. The new version will be developed using modern technology. The main requirements for the system are that it shall:
* Load sales data, sent electronically from the stores each evening, into a central database.
* Produce actual sales reports for the merchandisers, whose job is to manage stock levels in stores.
* Produce sales forecast reports based on a combination of sales history and forecasting parameters. The parameters will be entered by the merchandisers into a browser-based front end and the reports will be produced overnight. The users will be able to see the reports next day, on screen or in print, by requesting this through the browser.
Requirements 1 and 2 are satisfied by the existing system and will be rewritten with no significant changes.
Requirement 3 is new and has been clearly specified.
The entry of forecasting parameters and of requests to see the reports will be low volume, but the Merchandising Manager is concerned about usability because the forecasting parameters are complex.
Which test charter would be BEST for the initial exploratory testing of requirement 3?

• A. Explore the report request entry features With their requirements specification To discover any usability issues
• B. Explore the actual sales report production features With examples of the current reports To discover any adverse impact of requirement 3 on requirement 2
• C. Explore the forecasting parameter entry features With their requirements specification To discover any usability issues
• D. Explore the forecasting parameter entry features With their requirements specification To discover any performance issues

You are testing the functional correctness of an application which generates quotes for motor insurance. The amount of the quote is governed by a combination of the following factors:
* Type of Cover, can be: comprehensive, third party damage only, or third party damage + fire and theft
* Vehicle Engine Size, can be: < 1500cc, < 2000cc, < 2500cc, > =2500cc
* Driving Licence Type, can be: fully qualified, or student driver
* Vehicle Storage Type, can be: locked garage, or unlocked private place, or public place
* Time Since Last Claim, can be: < 1year, < 2yrs, < 3yrs, > =3yrs
In order to achieve full PAIRWISE coverage, how many combinations must be tested?

• A. 36
• B. 16
• C. 12
• D. 288

In your role as a Test Analyst for the development of a business application, you asked the Product Owner to help you understand how the various product risks would affect the users.
Which product risk management activity was this?

• A. Risk identification
• B. Risk control
• C. Risk mitigation
• D. Risk assessment