White-box testing, also known as structural testing, involves testing the internal structures or workings of an application, as opposed to its functionality (which is tested by black-box testing). The correct statement about white-box testing is that it helps find defects by measuring aspects such as statement coverage.

Statement Coverage: White-box testing techniques like statement coverage measure whether each statement in the code has been executed at least once. This helps ensure that all parts of the code are tested and can reveal defects in areas that might not be reached by black-box testing alone.

Other statements are less accurate in the context of white-box testing:

Specifications being vague: White-box testing is code-focused, not requirement-focused. If specifications are vague, it affects both white-box and black-box testing. The main advantage of white-box testing is that it allows testers to create tests based on the code's structure and logic.

Requirements-based coverage: This is typically associated with black-box testing, which derives tests from specifications and requirements. White-box testing, on the other hand, derives tests from the code itself.

Focus on defects rather than failures: Both white-box and black-box testing aim to identify defects, but white-box testing does this through code coverage and examining the code paths directly. It does not focus exclusively on defects rather than failures; it is just another method to identify potential issues.

A product risk is a risk that affects the quality or timeliness of the software product being developed or tested1.Product risks are related to the requirements, design, implementation, verification, and maintenance of the software product2.

The risk of the sub-contractor failing to meet his commitment is a product risk, as it could cause a delay in the completion of the testing required for the current cycle, which in turn could affect the release date of the product.The release date is an important aspect of the product quality, as it reflects the customer satisfaction and the market competitiveness of the product3.

The other options are not correct because:

A . It is not true that any risk associated with development timeline is a product risk.Some risks could be project risks, which are risks that affect the management or control of the software project, such as budget, resources, schedule, or communication1. For example, a risk of losing a key project stakeholder is a project risk, not a product risk.

B . It is not true that the risk is no longer a risk for the Test Manager since an independent party is managing it.The Test Manager is still responsible for ensuring that the testing activities are completed according to the test plan and the quality objectives4.The Test Manager should monitor and control the sub-contractor's performance and communicate with him regularly to identify and mitigate any potential issues or deviations5.

C .It is not clear what is meant by ''object'' in this option, but it could be interpreted as the software system under test or the test object6. In any case, the risk is not an object risk, as it does not affect the successful completion of the object, but rather the successful completion of the testing of the object.An object risk could be a risk that affects the functionality, reliability, usability, efficiency, maintainability, or portability of the software system under test2. For example, a risk of the software system having a high complexity or a low testability is an object risk, not a product risk.

Reference=

1ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 97

2ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 98

3ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 99

4ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 100

5ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 101

6ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 102

The business-facing quadrant that supports the team is focused on tests that validate the system against user stories. These tests ensure that the system delivers the value and functionality described by the user stories, which are central to agile methodologies.

ISTQB CTFL Syllabus V4.0, Section 5.1.7 on the testing quadrants, particularly the business-facing tests that support the team and are based on user stories.

During the review planning phase of a formal review process, decisions are made regarding which standards and procedures will be followed. This planning ensures that the review process is structured, consistent, and aligned with organizational or project-specific guidelines, thereby enhancing the effectiveness and reliability of the review outcomes.

In branch testing, a conditional branch represents a decision point in the software program where the flow of execution can take different paths based on specific conditions. For example, this could be an 'if-else' statement, a 'switch-case' statement, or loops where different execution paths are taken depending on the evaluated condition. This type of testing ensures that all possible paths and conditions are executed at least once, which helps in identifying any potential defects in different branches of the code.