Fault Tree Analysis (FTA) is a technique used to analyze the causes of faults (defects). The technique visually models how logical relationships between failures, human errors, and external events can combine to cause specific faults to disclose1. FTA can help to determine the root cause of observed and potential failures by tracing back the fault events to their initiating causes and identifying the combinations of events that can lead to the fault occurrence2. Therefore, option A is the correct answer. Option B is incorrect because FTA is not used to select the pairs of items to be used in pairwise testing, which is a technique to generate test cases based on the combinations of two input parameters. Option C is incorrect because FTA is not a formal technique used to identify the likely effects of risks, which are uncertain events or conditions that may have a positive or negative impact on the project objectives. Option D is incorrect because FTA is not used to target defect-based testing, which is a testing technique that uses information about the types, causes, and locations of defects discovered in previous projects to guide the selection, creation, and prioritization of test cases. References: 1: Fault Tree Analysis | ISTQB Glossary 2: Fault Tree Analysis (FTA) - Software Testing Genius : ISTQB Glossary, Pairwise Testing : ISTQB Glossary, Risk : ISTQB Glossary, Defect-Based Test Technique : Fault Tree Analysis (FTA) - Software Testing Genius : Fault Tree Analysis | ISTQB Glossary

Explanation/Reference:
Explanation:

In stakeholder matrix categorization,Defendersare stakeholders who havelow influencebuthigh interest. End users usually have a strong interest in how the product performs, but less influence on project decisions.
"Stakeholders with high interest but low influence are likely to be end-users who rely on timely and accurate information." (Source: ISTQB Advanced Level Test Manager Syllabus 2012, Section 1.4.1) Thus,Option Bis correct.

* 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).
References:
ISTQB Advanced Level Test Management Syllabus (TM-1.3.4)

Explanation/Reference:
Explanation: