C is correct. This is a generic testing tool that would still be useful in a mobile application project. A and B are specific tools that would be designed for use for the specific project. D might work but most generic performance testing tools don't work well for mobile applications because of their inability to work with simulators and provide the variability in network connections.

D is correct since it appears that people download it and never use it, perhaps because it takes so long to complete the download and the initial launch. This may not be the real problem, but it is certainly the first area to look at during testing. A and B are incorrect because the users are not actually using the software and wouldn't see these issues. C might be a problem leading to D being a symptom.

C is correct per the syllabus. A is probably not a goal since products come and go and long-term maintainability of the test framework may be a poor investment. B is not correct because known vendors may not produce tools that support the latest technologies. D is not correct because a lightweight risk analysis is more likely used than a formal risk analysis process.

D is correct as it tests each condition with invalid too low, valid and invalid too high values. A is incorrect because it doesn't consider the list save capabilities and it doesn't test the invalid values for the list. B is incorrect because it is doing BVA which results in too many tests for minimum coverage with EP. C is incorrect because it does not sufficiently test the save feature.