Exam Bundle

This preventive step mitigates a different project risk (syllabus section 4.2): A travel claim uses conditions 'flight cancelled' and 'replacement provided', with compensation depending on their combination; the tester groups all cancellation cases into one partition. The targeted safeguard for the current case is: Use a boundary matrix with minimum and maximum rows and adjacent values.

This preventive step mitigates a different project risk (syllabus section 4.2): A loyalty engine has an 'expired' terminal status but the QA suite never tests attempts to redeem a reward after expiration. The targeted safeguard for the current case is: Use a boundary matrix with minimum and maximum rows and adjacent values.

This preventive step mitigates a different project risk (syllabus section 4.4): A travel tester remembers a previous midnight time-zone defect and deliberately explores booking at 23:59 around daylight saving changes. The targeted safeguard for the current case is: Use a boundary matrix with minimum and maximum rows and adjacent values.

This choice is a useful response to a different testing situation (section 4.2, Black-Box Test Techniques): A warehouse selector accepts product weights in integer grams 100–500, but one test contains 99.5 grams even though the interface accepts only integers. The present problem instead depends on: A missing condition combination can conceal a faulty AND versus OR decision.

This choice is a useful response to a different testing situation (section 4.2, Black-Box Test Techniques): A fraud workflow has states Review, Approved, and Rejected, but testers verify all outbound transitions only from Review and never attempt approval after rejection. The present problem instead depends on: A missing condition combination can conceal a faulty AND versus OR decision.

This choice is a useful response to a different testing situation (section 4.5, Collaboration-based Test Approaches): A product team writes acceptance examples for the happy path only and discovers after release that malformed address input crashes shipping label creation. The present problem instead depends on: A missing condition combination can conceal a faulty AND versus OR decision.

This result may validate another testing scenario: A date picker accepts reservations from tomorrow through 30 days ahead, but the tester uses fixed dates that become invalid as the calendar advances. It does not establish the required result for this case: A $150 Premium order receives no rebate while a $250 Premium order receives the rebate.

This result may validate another testing scenario: A loyalty engine has an 'expired' terminal status but the QA suite never tests attempts to redeem a reward after expiration. It does not establish the required result for this case: A $150 Premium order receives no rebate while a $250 Premium order receives the rebate.

This result may validate another testing scenario: A developer sees 100% statement coverage on an eligibility function but the rejection branch that contains no executable statements is never taken. It does not establish the required result for this case: A $150 Premium order receives no rebate while a $250 Premium order receives the rebate.

This principle could explain a different testing issue: A numeric invoice reference accepts exactly eight digits, but the team tests a few eight-digit values and does not challenge the format's alphabetic and length restrictions. The present case is better explained by: A missing condition combination can conceal a faulty AND versus OR decision.

This principle could explain a different testing issue: A warehouse order can move Created to Paid to Shipped, yet tests attempt Created to Shipped and treat any rejection as a defect. The present case is better explained by: A missing condition combination can conceal a faulty AND versus OR decision.

This principle could explain a different testing issue: A tester relies on a checklist of historic outages and misses a newly required age boundary in a registration feature. The present case is better explained by: A missing condition combination can conceal a faulty AND versus OR decision.

This preventive step mitigates a different project risk (syllabus section 4.2): A music service supports Trial, Paid and Cancelled memberships, and its tests jump directly to Cancelled by setting database state, missing the cancellation event's side effects. The targeted safeguard for the current case is: Check each feasible combination against the specified Boolean action.

This preventive step mitigates a different project risk (syllabus section 4.2): A booking API allows 1–6 passengers, and a developer asserts that 1, 3, 6, and 7 prove three-value boundary coverage. The targeted safeguard for the current case is: Check each feasible combination against the specified Boolean action.

This preventive step mitigates a different project risk (syllabus section 4.5): A restaurant app story describes table booking but omits what happens if two customers reserve the last table simultaneously. The targeted safeguard for the current case is: Check each feasible combination against the specified Boolean action.

This choice is a useful response to a different testing situation (section 4.2, Black-Box Test Techniques): A delivery app supports parcel weight 0.1–30.0 kg, yet testing uses only many ordinary weights in the middle of the range. The present problem instead depends on: Confusing OR with AND changes outputs for mixed condition combinations.

This choice is a useful response to a different testing situation (section 4.2, Black-Box Test Techniques): A subscription form accepts plans for 1–12 months, but the suite tests 2, 3 and 4 months while never testing an invalid number. The present problem instead depends on: Confusing OR with AND changes outputs for mixed condition combinations.

This choice is a useful response to a different testing situation (section 4.5, Collaboration-based Test Approaches): A transport app team's Gherkin check asserts only that the booking page loads, though the story requires a fare quote to match luggage choices. The present problem instead depends on: Confusing OR with AND changes outputs for mixed condition combinations.

This result may validate another testing scenario: A safety alert system moves from Warning to Critical after three consecutive sensor breaches, but tests inject just one breach and assume the transition must occur. It does not establish the required result for this case: Orders with only active subscription and only high value each receive free delivery as specified.

This result may validate another testing scenario: A promo engine gives different discounts for cart totals below $50, $50–$99.99, and at least $100, while cases only verify $75. It does not establish the required result for this case: Orders with only active subscription and only high value each receive free delivery as specified.

This result may validate another testing scenario: A developer sees 100% statement coverage on an eligibility function but the rejection branch that contains no executable statements is never taken. It does not establish the required result for this case: Orders with only active subscription and only high value each receive free delivery as specified.

This principle could explain a different testing issue: A pricing page offers a 10% rebate only when membership is Premium and purchase value is at least $200, yet the case set excludes Premium orders below the threshold. The present case is better explained by: Confusing OR with AND changes outputs for mixed condition combinations.

This principle could explain a different testing issue: A date picker accepts reservations from tomorrow through 30 days ahead, but the tester uses fixed dates that become invalid as the calendar advances. The present case is better explained by: Confusing OR with AND changes outputs for mixed condition combinations.

This principle could explain a different testing issue: A tester discovers a severe navigation problem during a chartered exploratory session but stops investigating because the issue is not in the prewritten script. The present case is better explained by: Confusing OR with AND changes outputs for mixed condition combinations.

This preventive step mitigates a different project risk (syllabus section 4.2): A delivery app supports parcel weight 0.1–30.0 kg, yet testing uses only many ordinary weights in the middle of the range. The targeted safeguard for the current case is: Translate business conditions into explicit truth tables before implementation.

This preventive step mitigates a different project risk (syllabus section 4.2): A tax product has three region codes with different calculation policies, but testers classify all supported codes into one equivalence partition because they pass validation. The targeted safeguard for the current case is: Translate business conditions into explicit truth tables before implementation.

This preventive step mitigates a different project risk (syllabus section 4.5): A flight booking story says refunds must complete within seven days, but a test expects exactly seven days instead of verifying the maximum permitted time. The targeted safeguard for the current case is: Translate business conditions into explicit truth tables before implementation.

This choice is a useful response to a different testing situation (section 4.2, Black-Box Test Techniques): A purchase form classifies coupon strings as blank, valid format, and invalid format, but a tester labels every rejected blank string as a new unique partition. The present problem instead depends on: Some condition combinations are impossible or irrelevant and need justified constraints in decision tables.

This choice is a useful response to a different testing situation (section 4.2, Black-Box Test Techniques): A delivery app supports parcel weight 0.1–30.0 kg, yet testing uses only many ordinary weights in the middle of the range. The present problem instead depends on: Some condition combinations are impossible or irrelevant and need justified constraints in decision tables.

This choice is a useful response to a different testing situation (section 4.5, Collaboration-based Test Approaches): A product owner writes the user story 'As a customer I want faster checkout' with no measurable behavior, and developers and testers assume different interpretations. The present problem instead depends on: Some condition combinations are impossible or irrelevant and need justified constraints in decision tables.

This result may validate another testing scenario: A warehouse order can move Created to Paid to Shipped, yet tests attempt Created to Shipped and treat any rejection as a defect. It does not establish the required result for this case: The decision table coverage report distinguishes feasible combinations from excluded contradictory conditions.

This result may validate another testing scenario: An invoice discount rule differs between new and returning customers only when a coupon is valid, but testers verify each condition independently and miss their interaction. It does not establish the required result for this case: The decision table coverage report distinguishes feasible combinations from excluded contradictory conditions.

This result may validate another testing scenario: A tester wants to use source control-flow information to verify each conditional outcome, but mistakenly classifies the approach as black-box because the API response is still observable. It does not establish the required result for this case: The decision table coverage report distinguishes feasible combinations from excluded contradictory conditions.