ISTQB CTFL v4.0 Practice Test 18
Question 170
A foundation-level tester investigates: A nightly CI job runs static analysis but release engineers manually ignore its findings and no test evidence is linked to promotion. Which TWO complementary steps together provide the most appropriate response and a direct test of its effectiveness? Select TWO answers.
- Add appropriate automated checks at pipeline stages and enforce deployment quality gates while retaining exploratory and other necessary manual work.
- Review changed artifacts, dependency graph, retired features, prior incident patterns and selected test coverage for affected behavior.
- Assume any green build task is sufficient release evidence and that introducing automation eliminates the need for human testing judgment.
- Test specified functional behaviors and select relevant nonfunctional characteristics such as performance, usability, security and reliability.
- Inspect pipeline runs, gate conditions, failure-to-promotion behavior and manual test evidence for risks not covered by automation.
Explanation
Correct Answers
A:This is the appropriate testing Recommended action: Add appropriate automated checks at pipeline stages and enforce deployment quality gates while retaining exploratory and other necessary manual work. The case involves A nightly CI job runs static analysis but release engineers manually ignore its findings and no test evidence is linked to promotion.
E:This check addresses the issue: Inspect pipeline runs, gate conditions, failure-to-promotion behavior and manual test evidence for risks not covered by automation. The test should distinguish observed facts from the assumption that assume any green build task is sufficient release evidence and that introducing automation eliminates the need for human testing judgment. The intended testing outcome is: The pipeline blocks known failing changes and promotes only builds meeting documented testing and release conditions.
Incorrect Answers
B:This is a misconception related to a different testing issue, namely Maintenance testing and change impact analysis, and is not the most direct assumption behind this case. Here, A nightly CI job runs static analysis but release engineers manually ignore its findings and no test evidence is linked to promotion.
C:This shortcut is unsafe: Assume any green build task is sufficient release evidence and that introducing automation eliminates the need for human testing judgment. It neglects the relevant behavior: DevOps feedback benefits from continuous testing and automation but tools need meaningful criteria and do not eliminate other testing activities. In this scenario: foundation-level tester investigates: A nightly CI job runs static analysis but release engineers manually ignore its findings and no test evidence is linked to promotion.
D:This is a misconception related to a different testing issue, namely Functional and nonfunctional test types, and is not the most direct assumption behind this case. Here, A nightly CI job runs static analysis but release engineers manually ignore its findings and no test evidence is linked to promotion.
Question 171
A test analyst considers this real project scenario: A team discovers conflicting user-story conditions only during system testing, although a tester flagged them at refinement. Which testing action BEST addresses the stated issue? Select ONE best answer.
- Use component tests for isolated units and component integration tests for interfaces and interactions among components.
- Adapt test levels, timing, feedback and documentation to the lifecycle, testing relevant work products as soon as they are available.
- Assume shift-left means replacing all late system tests with early reviews and that retrospectives are complete without follow-up actions.
- Bring reviews and suitable checks earlier, then use retrospectives to choose, implement and evaluate concrete testing improvements.
Explanation
Correct Answer
D:This is the appropriate testing action: Bring reviews and suitable checks earlier, then use retrospectives to choose, implement and evaluate concrete testing improvements. The case involves A team discovers conflicting user-story conditions only during system testing, although a tester flagged them at refinement.
Incorrect Answers
A:This is an appropriate consideration for a different situation (Component and component integration test levels), but it does not directly resolve the one given here. Here, A team discovers conflicting user-story conditions only during system testing, although a tester flagged them at refinement. The necessary control or test is: Bring reviews and suitable checks earlier, then use retrospectives to choose, implement and evaluate concrete testing improvements.
B:This is an appropriate consideration for a different situation (SDLC model influence on test activities), but it does not directly resolve the one given here. Here, A team discovers conflicting user-story conditions only during system testing, although a tester flagged them at refinement. The necessary control or test is: Bring reviews and suitable checks earlier, then use retrospectives to choose, implement and evaluate concrete testing improvements.
C:That option would assume shift-left means replacing all late system tests with early reviews and that retrospectives are complete without follow-up actions, but it addresses a different concern. It follows the principle that Shift-left means earlier testing and quality activities; retrospectives improve process when findings produce owned measurable actions.
Question 172
In a software test-design exercise, the following case arises: A team discovers conflicting user-story conditions only during system testing, although a tester flagged them at refinement. Which principle of software testing BEST explains the problem? Select ONE best answer.
- A test level has distinct objectives, scope and test basis; component correctness does not establish correct communication between components.
- Functional tests ask what the system does; nonfunctional tests evaluate how well it behaves under selected quality characteristics.
- Shift-left means earlier testing and quality activities; retrospectives improve process when findings produce owned measurable actions.
- Assume shift-left means replacing all late system tests with early reviews and that retrospectives are complete without follow-up actions.
Explanation
Correct Answer
C:This is the relevant underlying rule: Shift-left means earlier testing and quality activities; retrospectives improve process when findings produce owned measurable actions. In the situation described, A team discovers conflicting user-story conditions only during system testing, although a tester flagged them at refinement.
Incorrect Answers
A:This is an appropriate consideration for a different situation (Component and component integration test levels), but it does not directly resolve the one given here. Here, A team discovers conflicting user-story conditions only during system testing, although a tester flagged them at refinement.
B:This is an appropriate consideration for a different situation (Functional and nonfunctional test types), but it does not directly resolve the one given here. Here, A team discovers conflicting user-story conditions only during system testing, although a tester flagged them at refinement. The necessary control or test is: Bring reviews and suitable checks earlier, then use retrospectives to choose, implement and evaluate concrete testing improvements.
D:That option would assume shift-left means replacing all late system tests with early reviews and that retrospectives are complete without follow-up actions, but it addresses a different concern. The practical response is to bring reviews and suitable checks earlier, then use retrospectives to choose, implement and evaluate concrete testing improvements.
Question 173
A release manager requests independent testing evidence: A team discovers conflicting user-story conditions only during system testing, although a tester flagged them at refinement. Which specific test or review evidence MOST directly establishes what happened? Select ONE best answer.
- Compare the delivery model, earliest available test basis, actual test start dates and defect feedback delay.
- Assume shift-left means replacing all late system tests with early reviews and that retrospectives are complete without follow-up actions.
- Inspect early review outputs, recurring defect patterns, agreed improvement tasks and later evidence that the tasks reduced rework.
- Inspect full-system transactions plus external API exchanges, failure paths, partner contracts and reconciliation evidence.
Explanation
Correct Answer
C:This directly verifies the issue: Inspect early review outputs, recurring defect patterns, agreed improvement tasks and later evidence that the tasks reduced rework. The test should distinguish observed facts from the assumption that assume shift-left means replacing all late system tests with early reviews and that retrospectives are complete without follow-up actions.
Incorrect Answers
A:This is an appropriate consideration for a different situation (SDLC model influence on test activities), but it does not directly resolve the one given here. Here, A team discovers conflicting user-story conditions only during system testing, although a tester flagged them at refinement.
B:This shortcut is unsafe: Assume shift-left means replacing all late system tests with early reviews and that retrospectives are complete without follow-up actions. It neglects the relevant behavior: Shift-left means earlier testing and quality activities; retrospectives improve process when findings produce owned measurable actions.
D:This is an appropriate consideration for a different situation (System and system integration test levels), but it does not directly resolve the one given here. Here, A team discovers conflicting user-story conditions only during system testing, although a tester flagged them at refinement.
Question 174
A software quality workshop reviews this situation: A team discovers conflicting user-story conditions only during system testing, although a tester flagged them at refinement. Which observed result BEST demonstrates that the testing activity met its stated objective? Select ONE best answer.
- Each increment or development stage receives timely suitable testing and risk feedback before dependent work accumulates.
- The calculation is correct by itself and its component interface exchanges valid data with dependent software.
- Assume shift-left means replacing all late system tests with early reviews and that retrospectives are complete without follow-up actions.
- Ambiguous conditions are resolved before costly build and process improvements are demonstrated rather than only discussed.
Explanation
Correct Answer
D:This is the observable acceptance result: Ambiguous conditions are resolved before costly build and process improvements are demonstrated rather than only discussed. It follows from the testing approach: Bring reviews and suitable checks earlier, then use retrospectives to choose, implement and evaluate concrete testing improvements.
Incorrect Answers
A:This is an appropriate consideration for a different situation (SDLC model influence on test activities), but it does not directly resolve the one given here.
B:This is an appropriate consideration for a different situation (Component and component integration test levels), but it does not directly resolve the one given here. The necessary control or test is: Bring reviews and suitable checks earlier, then use retrospectives to choose, implement and evaluate concrete testing improvements.
C:This shortcut is unsafe: Assume shift-left means replacing all late system tests with early reviews and that retrospectives are complete without follow-up actions. It neglects the relevant behavior: Shift-left means earlier testing and quality activities; retrospectives improve process when findings produce owned measurable actions. For the scenario (A team discovers conflicting user-story conditions only during system testing, although a tester flagged them at refinement.), the required evidence is: Inspect early review outputs, recurring defect patterns, agreed improvement tasks and later evidence that the tasks reduced rework.
Question 175
A defect investigation documents this situation: A team discovers conflicting user-story conditions only during system testing, although a tester flagged them at refinement. Which misleading assumption about shift-left testing and retrospectives MOST directly contributes to this problem and should be rejected? Select ONE best answer.
- Assume shift-left means replacing all late system tests with early reviews and that retrospectives are complete without follow-up actions.
- Assume testing a complete application in isolation also proves every partner or external system interface behaves correctly.
- Assume adding unit tests after implementing a feature is automatically the same practice as writing tests before the production code.
- Assume a successful business-output assertion proves acceptable response time, security and usability under all conditions.
Explanation
Correct Answer
A:The correct principle is: Shift-left means earlier testing and quality activities; retrospectives improve process when findings produce owned measurable actions.
Incorrect Answers
B:This is a misconception related to a different testing issue, namely System and system integration test levels, and is not the most direct assumption behind this case. Here, A team discovers conflicting user-story conditions only during system testing, although a tester flagged them at refinement.
C:This is a misconception related to a different testing issue, namely Test-first development and TDD feedback, and is not the most direct assumption behind this case. Here, A team discovers conflicting user-story conditions only during system testing, although a tester flagged them at refinement.
D:This is a misconception related to a different testing issue, namely Functional and nonfunctional test types, and is not the most direct assumption behind this case. Here, A team discovers conflicting user-story conditions only during system testing, although a tester flagged them at refinement.
Question 176
A tester and product owner review the following behavior: After repeated escaped defects, a sprint retrospective lists complaints but never selects a measurable preventive experiment. Which testing action BEST addresses the stated issue? Select ONE best answer.
- Adapt test levels, timing, feedback and documentation to the lifecycle, testing relevant work products as soon as they are available.
- Bring reviews and suitable checks earlier, then use retrospectives to choose, implement and evaluate concrete testing improvements.
- Assume shift-left means replacing all late system tests with early reviews and that retrospectives are complete without follow-up actions.
- Run confirmation tests for the reported defect and risk-based regression tests for unaffected behavior potentially impacted by the change.
Explanation
Correct Answer
B:This is the appropriate testing action: Bring reviews and suitable checks earlier, then use retrospectives to choose, implement and evaluate concrete testing improvements. The case involves After repeated escaped defects, a sprint retrospective lists complaints but never selects a measurable preventive experiment.
Incorrect Answers
A:This is an appropriate consideration for a different situation (SDLC model influence on test activities), but it does not directly resolve the one given here. Here, After repeated escaped defects, a sprint retrospective lists complaints but never selects a measurable preventive experiment. The necessary control or test is: Bring reviews and suitable checks earlier, then use retrospectives to choose, implement and evaluate concrete testing improvements.
C:This shortcut is unsafe: Assume shift-left means replacing all late system tests with early reviews and that retrospectives are complete without follow-up actions. It neglects the relevant behavior: Shift-left means earlier testing and quality activities; retrospectives improve process when findings produce owned measurable actions. For the scenario (After repeated escaped defects, a sprint retrospective lists complaints but never selects a measurable preventive experiment.), the required evidence is: Inspect early review outputs, recurring defect patterns, agreed improvement tasks and later evidence that the tasks reduced rework.
D:This is an appropriate consideration for a different situation (Confirmation testing and regression testing), but it does not directly resolve the one given here. Here, After repeated escaped defects, a sprint retrospective lists complaints but never selects a measurable preventive experiment. The necessary control or test is: Bring reviews and suitable checks earlier, then use retrospectives to choose, implement and evaluate concrete testing improvements.
Question 177
During test preparation, a team encounters the following issue: After repeated escaped defects, a sprint retrospective lists complaints but never selects a measurable preventive experiment. Which principle of software testing BEST explains the problem? Select ONE best answer.
- Assume shift-left means replacing all late system tests with early reviews and that retrospectives are complete without follow-up actions.
- System testing evaluates the integrated system; system integration testing focuses on interactions between systems and external services.
- Test-first development uses executable expectations to guide work; the order and feedback cycle distinguish TDD from retroactive unit testing.
- Shift-left means earlier testing and quality activities; retrospectives improve process when findings produce owned measurable actions.
Explanation
Correct Answer
D:This is the relevant underlying rule: Shift-left means earlier testing and quality activities; retrospectives improve process when findings produce owned measurable actions. In the situation described, After repeated escaped defects, a sprint retrospective lists complaints but never selects a measurable preventive experiment.
Incorrect Answers
A:This shortcut is unsafe: Assume shift-left means replacing all late system tests with early reviews and that retrospectives are complete without follow-up actions.
B:This is an appropriate consideration for a different situation (System and system integration test levels), but it does not directly resolve the one given here. Here, After repeated escaped defects, a sprint retrospective lists complaints but never selects a measurable preventive experiment. The necessary control or test is: Bring reviews and suitable checks earlier, then use retrospectives to choose, implement and evaluate concrete testing improvements.
C:This is an appropriate consideration for a different situation (Test-first development and TDD feedback), but it does not directly resolve the one given here. Here, After repeated escaped defects, a sprint retrospective lists complaints but never selects a measurable preventive experiment. The necessary control or test is: Bring reviews and suitable checks earlier, then use retrospectives to choose, implement and evaluate concrete testing improvements.
Question 178
During iteration planning and quality review, this issue appears: After repeated escaped defects, a sprint retrospective lists complaints but never selects a measurable preventive experiment. Which specific test or review evidence MOST directly establishes what happened? Select ONE best answer.
- Inspect early review outputs, recurring defect patterns, agreed improvement tasks and later evidence that the tasks reduced rework.
- Review changed artifacts, dependency graph, retired features, prior incident patterns and selected test coverage for affected behavior.
- Review approved business acceptance criteria, representative user outcomes, backup recovery drills and support monitoring tests.
- Assume shift-left means replacing all late system tests with early reviews and that retrospectives are complete without follow-up actions.
Explanation
Correct Answer
A:This check addresses the issue: Inspect early review outputs, recurring defect patterns, agreed improvement tasks and later evidence that the tasks reduced rework. The test should distinguish observed facts from the assumption that assume shift-left means replacing all late system tests with early reviews and that retrospectives are complete without follow-up actions.
Incorrect Answers
B:This is an appropriate consideration for a different situation (Maintenance testing and change impact analysis), but it does not directly resolve the one given here. Here, After repeated escaped defects, a sprint retrospective lists complaints but never selects a measurable preventive experiment.
C:This is an appropriate consideration for a different situation (Acceptance testing and operational readiness), but it does not directly resolve the one given here. Here, After repeated escaped defects, a sprint retrospective lists complaints but never selects a measurable preventive experiment.
D:This shortcut is unsafe: Assume shift-left means replacing all late system tests with early reviews and that retrospectives are complete without follow-up actions. For the scenario (After repeated escaped defects, a sprint retrospective lists complaints but never selects a measurable preventive experiment.), the required evidence is: Inspect early review outputs, recurring defect patterns, agreed improvement tasks and later evidence that the tasks reduced rework.
Question 179
A project team is deciding how to test this condition: After repeated escaped defects, a sprint retrospective lists complaints but never selects a measurable preventive experiment. Which observed result BEST demonstrates that the testing activity met its stated objective? Select ONE best answer.
- Functional outcomes are correct and prioritized quality characteristics meet explicitly defined measurable thresholds.
- Assume shift-left means replacing all late system tests with early reviews and that retrospectives are complete without follow-up actions.
- The original failure no longer occurs and impacted related workflows continue to behave correctly after the change.
- Ambiguous conditions are resolved before costly build and process improvements are demonstrated rather than only discussed.
Explanation
Correct Answer
D:This is the observable acceptance result: Ambiguous conditions are resolved before costly build and process improvements are demonstrated rather than only discussed. It follows from the testing approach: Bring reviews and suitable checks earlier, then use retrospectives to choose, implement and evaluate concrete testing improvements. The case is: After repeated escaped defects, a sprint retrospective lists complaints but never selects a measurable preventive experiment.
Incorrect Answers
A:This is an appropriate consideration for a different situation (Functional and nonfunctional test types), but it does not directly resolve the one given here. Here, After repeated escaped defects, a sprint retrospective lists complaints but never selects a measurable preventive experiment. The necessary control or test is: Bring reviews and suitable checks earlier, then use retrospectives to choose, implement and evaluate concrete testing improvements.
B:It neglects the relevant behavior: Shift-left means earlier testing and quality activities; retrospectives improve process when findings produce owned measurable actions. For the scenario (After repeated escaped defects, a sprint retrospective lists complaints but never selects a measurable preventive experiment.), the required evidence is: Inspect early review outputs, recurring defect patterns, agreed improvement tasks and later evidence that the tasks reduced rework.
C:This is an appropriate consideration for a different situation (Confirmation testing and regression testing), but it does not directly resolve the one given here. Here, After repeated escaped defects, a sprint retrospective lists complaints but never selects a measurable preventive experiment.
Question 180
A foundation-level tester investigates: After repeated escaped defects, a sprint retrospective lists complaints but never selects a measurable preventive experiment. Which TWO complementary steps together provide the most appropriate response and a direct test of its effectiveness? Select TWO answers.
- Bring reviews and suitable checks earlier, then use retrospectives to choose, implement and evaluate concrete testing improvements.
- Review approved business acceptance criteria, representative user outcomes, backup recovery drills and support monitoring tests.
- For TDD, write a small test expressing desired behavior, observe failure, implement the minimum change, then refactor while tests remain green.
- Inspect early review outputs, recurring defect patterns, agreed improvement tasks and later evidence that the tasks reduced rework.
- Assume shift-left means replacing all late system tests with early reviews and that retrospectives are complete without follow-up actions.
Explanation
Correct Answers
A:This is the appropriate testing Recommended action: Bring reviews and suitable checks earlier, then use retrospectives to choose, implement and evaluate concrete testing improvements. The case involves After repeated escaped defects, a sprint retrospective lists complaints but never selects a measurable preventive experiment.
D:This check addresses the issue: Inspect early review outputs, recurring defect patterns, agreed improvement tasks and later evidence that the tasks reduced rework. The test should distinguish observed facts from the assumption that assume shift-left means replacing all late system tests with early reviews and that retrospectives are complete without follow-up actions. The intended testing outcome is: Ambiguous conditions are resolved before costly build and process improvements are demonstrated rather than only discussed.
Incorrect Answers
B:This is a misconception related to a different testing issue, namely Acceptance testing and operational readiness, and is not the most direct assumption behind this case. Here, After repeated escaped defects, a sprint retrospective lists complaints but never selects a measurable preventive experiment.
C:This is a misconception related to a different testing issue, namely Test-first development and TDD feedback, and is not the most direct assumption behind this case. Here, After repeated escaped defects, a sprint retrospective lists complaints but never selects a measurable preventive experiment.
E:This shortcut is unsafe: Assume shift-left means replacing all late system tests with early reviews and that retrospectives are complete without follow-up actions. It neglects the relevant behavior: Shift-left means earlier testing and quality activities; retrospectives improve process when findings produce owned measurable actions. In this scenario: A foundation-level tester investigates: After repeated escaped defects, a sprint retrospective lists complaints but never selects a measurable preventive experiment.