CTFL 5.2.3: Explain how product risk analysis may influence thoroughness and test scope
K2Syllabus section 5.2.3
3 original PrepBench practice questions for learning objective 5.2.3 of the CTFL 4.0 syllabus. Try the examples below and check each answer against its syllabus reference.
Practice questions
Question 1
A product risk analysis rates the payment module's risk level as high and the help pages' risk level as low. What does this result support?
- Giving both areas the same coverage so that the residual risk is spread evenly
- Using more rigorous test techniques and higher coverage on the payment module
- Dropping the help pages from the test scope because their risk level is not high
- Deferring the payment module until late, so the risk analysis can be repeated first
Show answer
- Giving both areas the same coverage so that the residual risk is spread evenlySpreading effort evenly is the opposite of focusing it to minimize residual product risk.
- Correct answer: Using more rigorous test techniques and higher coverage on the payment moduleTechnique choice and coverage to be achieved are set from the risk analysis results.
- Dropping the help pages from the test scope because their risk level is not highA low risk level is still a risk, and the analysis determines the scope rather than emptying it.
- Deferring the payment module until late, so the risk analysis can be repeated firstThe results are used to find critical defects as early as possible, so deferral works against them.
The goal of product risk analysis from a testing perspective is to focus the test effort so that the residual level of product risk is minimized. Its results are used to determine the test scope, the test levels and test types, the test techniques to be employed and the coverage to be achieved, to estimate the effort per task, and to prioritize testing in order to find the critical defects as early as possible.
Syllabus section 5.2.3
Question 2
Product risk analysis identifies a payment failure as high risk and a cosmetic alignment issue as low risk. How should these results influence testing?
- Prioritize tests for the payment risk and use the analysis to determine suitable scope, techniques, coverage, and effort
- Give both risks comparable test scope and effort because their product areas are tested in the same release
- Test the cosmetic issue first because it is quicker to exercise than the payment behavior
- Use the categories to group risks but leave the existing test scope and coverage unchanged
Show answer
- Correct answer: Prioritize tests for the payment risk and use the analysis to determine suitable scope, techniques, coverage, and effortHigher product risk drives priority and informs thoroughness and scope decisions.
- Give both risks comparable test scope and effort because their product areas are tested in the same releaseSharing a release does not override the different risk levels when setting scope and effort.
- Test the cosmetic issue first because it is quicker to exercise than the payment behaviorConvenience does not replace prioritization aimed at finding critical defects early.
- Use the categories to group risks but leave the existing test scope and coverage unchangedRisk categories support handling, while the assessed results also inform scope, coverage, and effort.
Product risk analysis can influence testing thoroughness and scope. Its results determine test scope, levels and types, techniques and coverage, effort, and test priority so that critical defects can be found as early as possible.
Syllabus section 5.2.3
Question 3
Product risk analysis finds a security risk that crosses several components and requires specialized testing. Which test-plan response best uses the analysis results?
- Keep the existing test levels and types, and record the risk for defect reporting after execution
- Use likelihood and impact to calculate the risk level, while leaving test scope and effort unchanged
- Group the risk with similar risks, and defer test selection until risk monitoring begins
- Select suitable test levels and types, set techniques and coverage, estimate effort, and consider further risk-reduction activities
Show answer
- Keep the existing test levels and types, and record the risk for defect reporting after executionRisk-analysis results can change test levels and types before execution rather than serving only later reporting.
- Use likelihood and impact to calculate the risk level, while leaving test scope and effort unchangedDetermining the risk level is part of assessment, but the result also informs scope and effort.
- Group the risk with similar risks, and defer test selection until risk monitoring beginsCategorization helps assign mitigation, but test selection is an immediate use of analysis results.
- Correct answer: Select suitable test levels and types, set techniques and coverage, estimate effort, and consider further risk-reduction activitiesThe results guide test scope and thoroughness and may identify additional risk-reduction activities.
Product risk analysis can influence testing thoroughness and scope. Its results are used to determine scope, test levels and types, techniques and coverage, effort, priority, and whether activities beyond testing can reduce the risk. The specialized cross-component risk therefore changes the test plan rather than merely being recorded or categorized.
Syllabus section 5.2.3
Original PrepBench practice material, not official exam questions or exam dumps. PrepBench is independent and is not affiliated with or endorsed by ISTQB®.