Context Analysis:

Deployment readiness depends on understanding the risk of releasing the software. The metrics provided include execution, design, defect counts, and coverage but do not quantifyresidual risk, which reflects remaining risks post-testing.

Evaluation of Options:

A. Number of tests passed:

Incorrect. While important, it doesn't directly provide insight into the remaining risk.

B. Number of defects outstanding:

Incorrect. Though critical, it’s only one aspect of assessing readiness and doesn’t provide the full picture of residual risk.

C. Residual risk:

Correct. Residual risk quantifies untested areas and unresolved issues, vital for decision-making.

D. Planned vs actual cost of testing:

Incorrect. While useful for process evaluation, it’s not directly tied to deployment readiness.

Syllabus Alignment:

The syllabus emphasizes risk-based approaches, highlighting residual risk as a critical deployment readiness metric (TM-1.3.4).

Competence in Handling Non-Standard Requirements:

Methodical competence refers to the ability to systematically analyze and interpret information, even when it is unconventional or unstructured.

The tester needs to refine their skills in identifying and deriving testable requirements from the available data.

Evaluation of Options:

A(Professional competence) refers to domain knowledge but does not address the specific challenge.

Bis correct as it pertains to systematically working through unconventional requirements.

C(Social competence) andD(Personal competence) do not address the analytical challenge.

References and Syllabus Alignment:

Methodical competence is emphasized under "Test Management Skills" in the ISTQB syllabus (TM-3.1.1)???.

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.