The absence-of-errors fallacy is one of the seven testing principles mentioned in the ISTQB syllabus. This principle states that even if no defects are found in the software, it does not guarantee that the software is usable and meets the user needs and expectations. By involving users early in the development process through practices like prototyping, the team can gather feedback to ensure that the software aligns with user expectations, thereby addressing the risk of this fallacy.

To determine the correct execution order that minimizes the number of configuration switches and respects the dependencies, we need to consider the following:
* Initial Configuration:CONF1.
* Dependencies:
* TC1 depends on nothing.
* TC2 depends on TC4.
* TC3 depends on TC4.
* TC4 depends on nothing.
* TC5 depends on TC1.
* Configuration Requirements:
* TC1 requires CONF2.
* TC2 requires CONF2.
* TC3 requires CONF1.
* TC4 requires CONF1.
* TC5 requires CONF2.
Given the initial configuration is CONF1, start with test cases that can run on CONF1 and respect the dependencies. Then switch to CONF2 only when necessary. The optimal order to minimize configuration switches is:
* Start withTC4(no dependencies, CONF1).
* Continue withTC3(depends on TC4, CONF1).
* Switch to CONF2.
* ExecuteTC2(depends on TC4, CONF2).
* Continue withTC1(no dependencies, CONF2).
* Finally, executeTC5(depends on TC1, CONF2).
Therefore, the correct order is:
* TC4(CONF1)
* TC3(CONF1)
* TC2(CONF2)
* TC1(CONF2)
* TC5(CONF2)
Thus, the answer isA. TC4, TC3, TC2, TC1, TC5.

Checklist-based testingusesspecific test conditions(B) that help testers ensure key aspects are validated. The checklist items can be derived from past defects, requirements, or regulatory standards.
* (A) is incorrectbecause general guidelines lack specificity.
* (C) is incorrectbecause checklists can be used for both manual and automated testing.
* (D) is incorrectbecause checklists are useful for both functional and non-functional testing (e.g., security, performance).
Checklistshelp ensure completenesswithout enforcingstrictly scriptedexecution.
Reference:ISTQB CTFL v4.0 Syllabus, Section 4.4.3 - Checklist-Based Testing

The minimum number of test cases needed to cover the full decision table associated with this scenario is 6.
This is because the decision table has 4 conditions (type of customer and amount of sale) and 4 actions (bonus percentage). The conditions have 2 possible values each (Basic or Premium, and G1, G2 or G3), so the total number of combinations is 2 x 2 x 2 x 2 = 16. However, not all combinations are valid, as some of them are contradictory or impossible. For example, a sale cannot be both less than 300 euros and greater than 2000 euros at the same time. Therefore, we need to eliminate the invalid combinations and keep only the valid ones. The valid combinations are:
Type of customer
Amount of sale
Bonus percentage
Basic
G1
3%
Basic
G2
5%
Basic
G3
7%
Premium
G1
5%
Premium
G2
7%
Premium
G3
10%
These 6 combinations cover all the possible values of the conditions and actions, and they are the minimum number of test cases needed to cover the full decision table.
ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents,

Exploratory testing is characterized by its reliance on the skills and experience of the tester. The effectiveness of exploratory testing depends heavily on the tester's ability to design and execute tests based on their intuition and knowledge of the application. This type of testing is often performed without predefined test cases, making the individual tester's expertise crucial.
References:
* ISTQB CTFL Syllabus V4.0, Section 4.4 on experience-based testing techniques, including exploratory testing, which highlights the importance of the tester's skills.