CTFL_Syll_4.0 Exam Dumps : ISTQB Certified Tester Foundation Level (CTFL) v4.0

Exploratory testing is an experience-based testing technique where test design and test execution occur simultaneously. It is characterized by the tester actively exploring the application, using their intuition and experience to uncover defects. Exploratory testing sessions are often guided by test charters, which are brief documents outlining the test objectives, scope, and areas to be explored during the session.

These test charters provide a flexible framework that directs the tester's exploration without being overly prescriptive, allowing testers to adapt and investigate new areas as they uncover issues. This approach is particularly useful in dynamic and complex systems where predefined test cases might not cover all scenarios.

Comprehensive and Detailed Explanation From Exact Extract:

This question applies theState Transition Testingtechnique.

Let’s evaluateOption Dstep-by-step:

NORMAL MODE → DEGRADED MODE:✅Valid on“FAILURE DETECTED”

DEGRADED MODE → NORMAL MODE:✅Valid on“ALL FAILURES CLEARED”

NORMAL MODE → DIAGNOSTIC MODE:✅Valid on“SELF DIAGNOSTIC INITIATED”

DIAGNOSTIC MODE → DEGRADED MODE:❌Invalid– there isno defined transitionfrom DIAGNOSTIC MODE directly to DEGRADED MODE.

According to the state diagram, DEGRADED MODE can only be entered:

From NORMAL MODE (on FAILURE DETECTED), or

Not from DIAGNOSTIC MODE at all.

This violates the rule:

“State transition testing uses a model where test cases are designed to execute valid and invalid transitions.”

(ISTQB CTFL Syllabus v4.0, Section 4.2.4 – State Transition Testing, Page 40)

Thus, OptionDcontains aninvalid transition, making it the correct answer.

Test automationimproves efficiency and accuracy, butit does NOT eliminate manual testing (D).

(A) is correctbecause automationspeeds up execution.

(B) is correctas automated tests produceconsistent and unbiased results.

(C) is correctbecause automationreduces human errors in repetitive tests.

However,manual testing remains essential for exploratory testing, usability testing, and complex test scenarios.