Context Analysis:
Higher-than-expected defects in a high-risk area indicate the need for additional testing to mitigate potential impacts.
Evaluation of Options:
A . Reassess the risk with a higher likelihood number:
Incorrect. While reassessment is useful, immediate action should prioritize more testing.
B . Reassess the risk with a higher impact number:
Incorrect. The impact may already be known, and more testing is the next practical step.
C . Concentrate more testing in the area because the risk is clearly higher:
Correct. Addressing higher-than-expected defects through focused testing ensures risks are adequately mitigated.
D . Concentrate less testing in the area because the defects are already found:
Incorrect. Higher defects warrant more testing, not less.
Syllabus Alignment:
ISTQB highlights increasing test efforts in high-risk areas with higher-than-expected defect levels (TM-1.3.4).
Reference:
ISTQB Advanced Level Test Management Syllabus (TM-1.3.4)

* Context Analysis:
* The scenario involves tight integration, architectural design, and data transformations, requiring detailed and structured approaches.
* Access to architectural documents and experienced testers (former developers) aligns with model- based and white-box techniques.
* Evaluation of Options:
* A. Model-based and white-box:
* Correct. Model-based testing leverages design documents, while white-box testing uses internal knowledge for detailed integration testing.
* B. Experience-based and black-box:
* Incorrect. This is less structured and doesn't utilize available design documentation or tester expertise.
* C. Risk-based and non-functional:
* Incorrect. Risk-based testing focuses on high-priority areas but doesn't leverage the design documents for integration specifics.
* D. Requirements-based and functional:
* Incorrect. While functional testing is relevant, requirements-based testing does not utilize internal system knowledge effectively.
* Syllabus Alignment:
* ISTQB emphasizes model-based and white-box testing as appropriate for systems with complex integrations (TM-1.2.6).
References:
ISTQB Advanced Level Test Management Syllabus (TM-1.2.6)

* Context Analysis:
* Requirements coverage must be defined during test planning to ensure tests align with all requirements from the start of the project.
* Evaluation of Options:
* A. Test planning:
* Correct. Coverage goals are established during planning to define test objectives and scope.
* B. Test monitoring:
* Incorrect. Monitoring tracks progress but doesn't define coverage.
* C. Test execution:
* Incorrect. Execution measures coverage but doesn't define it.
* D. Test completion:
* Incorrect. Completion reviews coverage metrics but doesn't define them.
* Syllabus Alignment:
* Test planning (TM-1.1.1) includes defining coverage goals and ensuring alignment with requirements.
References:
ISTQB Advanced Level Test Management Syllabus (TM-1.1.1)