ISTQB CTAL-TM Practice Test - Questions Answers, Page 3

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 software1.A reactive test strategy should be utilized for a project that uses a spiral development approach, which is a type of iterative/incremental approach that adds risk analysis and prototyping activities to each iteration2.A reactive test strategy is suitable for a spiral development approach because it allows for flexibility, adaptability, and creativity in the testing process, as well as for early feedback, risk reduction, and continuous improvement in the software development process3. Therefore, option D is the correct answer. Option A is incorrect because a model-based test strategy is a test strategy that uses models 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 may not work well with a spiral development approach, as it requires the availability and stability of the models, which may not be the case in a spiral development approach that involves frequent changes and refinements of the software under test. Option B is incorrect because a methodical test strategy is a test strategy that uses predefined test methods, techniques, and procedures to design and execute tests, such as equivalence partitioning, boundary value analysis, or decision table testing. A methodical test strategy may not work well with a spiral development approach, as it requires the availability and stability of the test basis, such as the requirements, specifications, or design documents, which may not be the case in a spiral development approach that involves frequent changes and refinements of the software under test. Option C is incorrect because a standard-compliant test strategy is a test strategy that follows a predefined set of standards, guidelines, or regulations to design and execute tests, such as ISO, IEEE, or CMMI.A standard-compliant test strategy may not work well with a spiral development approach, as it requires the compliance and consistency of the testing process, which may not be the case in a spiral development approach that involves frequent changes and refinements of the software under test.Reference:1: ISTQB Glossary, Reactive Test Strategy2: ISTQB Glossary, Spiral Model3: ISTQB Advanced Level Test Manager Syllabus, Section 1.1.1 :Spiral Model in Software Development Life Cycle - Software Testing Material:Spiral Model - Tools QA:Strategic Test Management - ISTQB not-for-profit association: ISTQB Glossary, Model-Based Testing : ISTQB Glossary, Methodical Test Strategy : ISTQB Glossary, Standard-Compliant Test Strategy :ISTQB Foundation Level #39 -- Test Approach and Strategy - Software Testing Mentor

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.

Reference: 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.

Determining the cost of external failures involves analyzing the impact of defects that escape into production. This includes the direct costs associated with fixing the defects, as well as the indirect costs such as customer dissatisfaction, damage to the company's reputation, and potential loss of business. By quantifying these costs, the Test Manager can illustrate the financial benefits of comprehensive testing in preventing high-cost external failures, thereby demonstrating its value as an investment rather than a cost overhead.

Reference: The ISTQB Advanced Level Test Manager documents provide guidelines on how to establish and use metrics to measure the effectiveness and efficiency of the testing process, including the cost of quality and the Return on Investment (ROI) for testing activities. These references support the rationale behind choosing option C as the verified answer.

The correct answer is C. Change and configuration management. This is because a smoke test is a type of test that checks the basic functionality and stability of a new build before proceeding to more detailed testing. A smoke test is an example of change and configuration management, which is the activity of controlling and tracking the changes made to the software and its configuration items throughout the software development lifecycle.Reference:Certified Tester Advanced Level Test Manager (CTAL-TM) - ISTQB not-for-profit association,ISTQB Test Manager Certification - ISTQB Exams Worldwide - ISTQB Official Registration,Managing the Test Team - ISTQB not-for-profit association

Test-driven development (TDD) is a core principle of Agile software development. In TDD, test cases are created before the code is written, and the code is developed to pass these tests.This approach emphasizes requirements and solutions evolving through collaborative effort and is a key practice in Agile methodologies12.

Reference: The Agile Alliance describes TDD as a style of programming tightly interwoven with coding, testing, and design, which is a fundamental aspect of Agile development3.Wikipedia also notes that TDD is related to the test-first programming concepts of extreme programming, an Agile methodology

This is because test-driven development (TDD) is a style of programming in which coding, testing, and design are tightly interwoven. TDD is a core principle of agile software development, which is an iterative and adaptive approach that values customer collaboration, working software, and responding to change.Agile AllianceReference:Certified Tester Advanced Level Test Manager (CTAL-TM) - ISTQB not-for-profit association,ISTQB Test Manager Certification - ISTQB Exams Worldwide - ISTQB Official Registration,What is Test Driven Development (TDD)? | Agile Alliance

The best action that the Test Manager can take prior to the start of the next test phase for the next release is to ensure that the correct stakeholders' participation during the risk assessment process. This is because the risk assessment process is crucial for identifying and prioritizing the risks that may affect the quality of the system, and allocating testing resources accordingly. The correct stakeholders are those who have the authority, knowledge, and interest in the system and its risks, and who can provide valuable input and feedback to the test team. By involving the correct stakeholders, the Test Manager can ensure that the risk-based test approach is aligned with the project objectives and the stakeholder expectations, and that the most critical areas are tested adequately.Reference:Certified Tester Advanced Level Test Manager (CTAL-TM) - ISTQB not-for-profit association,ISTQB Test Manager Certification - ISTQB Exams Worldwide - ISTQB Official Registration,Managing the Test Team - ISTQB not-for-profit association

Creating a cross-functional team to address the remaining risks is the best option, as it actively involves various stakeholders in the mitigation process. This approach allows for diverse perspectives and expertise to be applied to reduce both the likelihood of the risks occurring and their potential impact, without incurring excessive costs or ignoring the risks altogether.

Reference: The ISTQB Advanced Level Test Manager syllabus and related documents emphasize the importance of risk management throughout the testing process.It suggests that forming teams to address risks can be an effective strategy, as it leverages collective knowledge and resources to mitigate risks in a cost-effective manner

A depth-first risk-based testing technique is a method of prioritizing and executing test cases based on the risk level of the features or functions to be tested. In this technique, the test cases with the highest risk are executed first, followed by the test cases with lower risks. This ensures that the most critical and likely areas of failure are tested thoroughly and early in the testing process.Risk Based Testing: Approach, Matrix, Process & Examples - Guru99Reference:Certified Tester Advanced Level Test Manager (CTAL-TM) - ISTQB not-for-profit association,ISTQB Test Manager Certification - ISTQB Exams Worldwide - ISTQB Official Registration, [Analytical Test Strategy: A Comprehensive Guide - LambdaTest]