The key principles of software testing include: i. Testing shows the presence of defects, not their absence. iv.
Defects cluster together. v. Testing is context dependent. vi. Beware of the pesticide paradox. vii. Absence of errors is a fallacy. These principles highlight the importance of recognizing the limitations and context of testing, as well as the potential for repeated tests to become less effective.

Confirmation testing is performed after a defect is fixed, and if such testing is successful then the regression tests that are relevant for such fix can be executed. Confirmation testing, also known as re-testing, is the process of verifying that a defect has been resolved by running the test case that originally detected the defect.
Confirmation testing is usually done before regression testing, which is the process of verifying that no new defects have been introduced in the software as a result of changes or fixes. Therefore, option D is the correct answer.
References: ISTQB Certified Tester Foundation Level Syllabus v4.01, Section 2.4.1, page 28; ISTQB Glossary v4.02, page 15.

In a formal review process, the recorder's role is typically responsible for documenting the findings of the review team, including action items, decisions, and recommendations. This ensures that there is an accurate record of what was discussed and agreed upon, facilitating follow-up and continuous improvement. Therefore, statement C is correct as per the ISTQB CTFL syllabus.

This answer is correct because identifying potential anomalies in the work product under review is one of the tasks the Author is responsible for, as part of a typical formal review. The Author is the person who creates the work product to be reviewed, such as a requirement specification, a design document, or a test case. The Author's tasks include preparing the work product for the review, identifying potential anomalies in the work product, and fixing the anomalies found in the work product after the review. References: ISTQB Glossary of Testing Terms v4.0, ISTQB Foundation Level Syllabus v4.0, Section 2.4.2.1

In software testing, risks are categorized into product risks and project risks. Product risks are associated with the potential of a product to fail in meeting its quality criteria. Project risks are related to potential issues that could affect the project's ability to deliver a product.
[i] is a project risk because it concerns the availability and adequacy of hardware resources for performance testing.
[ii] is a product risk because it pertains to a security and functionality issue within the web application.
[iii] is a project risk because it involves the availability of necessary requirements documentation for the testing process.
[iv] is a product risk because it relates to the system's functionality and data integrity after a failure.
Thus, statement A correctly classifies [ii] and [iv] as product risks and [i] and [iii] as project risks.