In an iterative development model with close customer involvement and verbal communication of requirements, there is an inherent risk of changes in the system architecture. This is due to the evolving understanding of requirements and the potential for new requirements to emerge as the project progresses.
References:The ISTQB Advanced Level Test Manager syllabus emphasizes the importance of managing risks in iterative development models1. It suggests that test managers should be prepared for changes, including possible alterations to the system architecture, as part of the risk management process23. This approach ensures that the testing strategy remains flexible and responsive to changes throughout the development lifecycle.

Explanation/Reference:
Explanation:

An analytical test strategy is a test strategy that is based on the analysis of the factors that affect the quality of the software under test, such as the requirements, the risks, the complexity, or the criticality1. An analytical test strategy uses these factors to define the test objectives, scope, approach, and techniques, as well as to prioritize and allocate the test resources2. Reporting the test results as "Requirements tested, passed, and failed" implies that the testing is driven by the requirements, which are the specifications of the desired features and functions of the software under test. Testing based on the requirements is an example of an analytical test strategy, as it uses the requirements as the main factor to guide the testing activities. Therefore, option C is the correct answer. Option A is incorrect because a model-based test strategy is a test strategy that usesmodels to represent the desired behavior and structure of the software under test, and to derive test cases, test data, test procedures, and test oracles. A model-based test strategy does not necessarily report the test results as "Requirements tested, passed, and failed", as it may use other types of models, such as state diagrams, data flow diagrams, or decision tables, to generate and execute the tests. Option B is incorrect because an exploratory test strategy is a test strategy that uses the tester's knowledge, skills, and creativity to design and execute tests dynamically, without predefined test cases or test procedures. An exploratory test strategy does not report the test results as "Requirements tested, passed, and failed", as it does not follow a formal or structured testing process, but rather relies on the tester's intuition, experience, and feedback. Option D is incorrect because a reactive test strategy is a test strategy that uses the actual behavior and results of the software under test to design and execute tests, without prior knowledge or documentation of the software. A reactive test strategy does not report the test results as "Requirements tested, passed, and failed", as it does not have any requirements or specifications to compare the software against, but rather uses the software itself as the test basis. References: 1: ISTQB Glossary, Analytical Test Strategy 2: ISTQB Advanced Level Test Manager Syllabus, Section 1.1.1 : ISTQB Glossary, Requirement : ISTQB Advanced Level Test Manager Syllabus, Section 1.1.1 : ISTQB Glossary, Model-Based Testing : ISTQB Advanced Level Test Manager Syllabus, Section 1.1.1 : ISTQB Glossary, Exploratory Testing : ISTQB Advanced Level Test Manager Syllabus, Section 1.1.1 : ISTQB Glossary, Reactive Test Strategy : ISTQB Advanced Level Test Manager Syllabus, Section 1.1.1 : Test Strategy | ISTQB Glossary : Test Strategy - ISTQB not-for-profit association

Explanation/Reference:
Explanation: