Definition: This task is about creating an unanswerable question based on a given passage. Construct a question that looks relevant to the given context but is unanswerable. Following are a few suggestions about how to create unanswerable questions:
(i) create questions which require satisfying a constraint that is not mentioned in the passage
(ii) create questions which require information beyond what is provided in the passage in order to answer
(iii) replace an existing entity, number, date mentioned in the passage with other entity, number, date and use it in the question
(iv) create a question which is answerable from the passage and then replace one or two words by their antonyms or insert/remove negation words to make it unanswerable.
Input: Passage: The practice of component interface testing can be used to check the handling of data passed between various units, or subsystem components, beyond full integration testing between those units. The data being passed can be considered as "message packets" and the range or data types can be checked, for data generated from one unit, and tested for validity before being passed into another unit. One option for interface testing is to keep a separate log file of data items being passed, often with a timestamp logged to allow analysis of thousands of cases of data passed between units for days or weeks. Tests can include checking the handling of some extreme data values while other interface variables are passed as normal values. Unusual data values in an interface can help explain unexpected performance in the next unit. Component interface testing is a variation of black-box testing, with the focus on the data values beyond just the related actions of a subsystem component.
Output:
What can be used to check the databases passed between units?