Risk Assessment & Management Flashcards
7 cards from real Software Testing practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Risk Assessment & Management flashcards as text
Which risk identification technique involves reviewing historical defect data and post-mortem reports from previous projects?
Answer: Lessons-learned review
Lessons-learned reviews mine past project data to surface patterns of risk that are likely to recur.
Risk-based test prioritization primarily aims to maximize which outcome given limited testing time?
Answer: Defect detection rate in high-risk areas
Risk-based prioritization focuses testing effort on areas with the highest probability and impact of failure to catch critical defects first.
A risk workshop attendee suggests a risk that the team unanimously considers highly unlikely AND low impact. The appropriate action is to:
Answer: Add it to the risk register and monitor it
Even low-likelihood, low-impact risks belong in the risk register so they can be monitored for changes in status.
Which qualitative risk analysis output is used to rank risks so teams can decide which to address first?
Answer: Risk probability-impact matrix
The probability-impact matrix plots risks on a grid and produces a ranked priority list without requiring numerical monetary data.
During test execution, a tester discovers a previously unknown risk in a module rated 'low risk.' What should happen immediately?
Answer: Re-evaluate the risk rating and update the risk register
Risk registers are living documents; newly discovered risks must be assessed and the register updated to reflect the current risk profile.
What is the primary purpose of a risk trigger in project risk management?
Answer: To serve as an early warning indicator that a risk is about to occur
A risk trigger is a condition or event that signals a risk is imminent, allowing the team to activate the contingency plan.
Which statement best describes the difference between a risk and an issue in software testing?
Answer: A risk is a potential future problem; an issue is a problem that has already occurred
A risk is uncertain and may or may not happen in the future, while an issue is a risk that has materialized and is actively impacting the project.