CAST Defect Management Lifecycle 3 — Questions and Answers
Question 1: Severity in a defect report primarily measures what?
- The technical impact on the system (Correct answer)
- How quickly it must be fixed
- Who reported the defect
- The cost of the fix
Correct answer: The technical impact on the system
Severity reflects the degree of impact a defect has on system functionality.
Question 2: Priority in a defect report primarily measures what?
- The urgency of fixing it (Correct answer)
- The technical impact
- The number of affected modules
- The developer's workload
Correct answer: The urgency of fixing it
Priority indicates how urgently a defect should be addressed in the schedule.
Question 3: Which combination is most realistic: a spelling error on the company's homepage banner?
- Low severity, high priority (Correct answer)
- High severity, high priority
- High severity, low priority
- Low severity, low priority
Correct answer: Low severity, high priority
A cosmetic typo has low technical impact but high visibility, so it is often high priority.
Question 4: A rarely used admin report crashes only under an unusual data condition. Which classification fits best?
- High severity, low priority (Correct answer)
- Low severity, low priority
- High severity, high priority
- Low severity, high priority
Correct answer: High severity, low priority
A crash is high severity, but rare use of the feature makes it low priority.
Question 5: Who typically assigns the priority of a defect?
- The project/test lead or triage team (Correct answer)
- The build pipeline automatically
- Only the end user
- The QA automation tool
Correct answer: The project/test lead or triage team
Priority is usually set by a lead or triage team weighing business needs and schedule.
Question 6: What is the main purpose of a defect triage meeting?
- To review, prioritize, and assign defects (Correct answer)
- To write new test cases
- To deploy the release
- To generate code coverage reports
Correct answer: To review, prioritize, and assign defects
Triage meetings review open defects to set priority and assign owners.
Question 7: A 'Blocker' severity defect is best described as one that:
- Halts further testing or major functionality (Correct answer)
- Is only cosmetic
- Affects documentation only
- Has a simple workaround
Correct answer: Halts further testing or major functionality
A blocker prevents continued testing or use of major functionality, demanding immediate attention.
CAST Defect Management Lifecycle 3
Severity in a defect report primarily measures what?