← All CAST Flashcard Decks

Defect Management Lifecycle Flashcards

21 cards from real CAST practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.

Read the first 20 Defect Management Lifecycle flashcards as text
  1. A tester logs a defect but cannot reliably reproduce it on later attempts. What status best fits this defect?

    Answer: Cannot Reproduce

    When a defect cannot be consistently reproduced, it is marked 'Cannot Reproduce' pending more information.

  2. Who is primarily responsible for verifying that a fixed defect is actually resolved before it is closed?

    Answer: The tester who reported it

    The reporting tester typically re-tests the fix to confirm resolution before closing.

  3. A defect is marked 'Deferred.' What does this most likely mean?

    Answer: The fix is postponed to a future release

    'Deferred' means the team agreed to address the defect in a later release rather than the current one.

  4. Which document or field captures the exact steps needed to recreate a defect?

    Answer: Steps to reproduce

    The 'steps to reproduce' field gives developers the precise sequence to trigger the defect.

  5. When two testers report the same underlying issue separately, the later report should be marked as what?

    Answer: Duplicate

    A second report of an already-logged issue is closed as a 'Duplicate' and linked to the original.

  6. A developer reviews a reported defect and determines the application behaves as designed. What status applies?

    Answer: Rejected / Not a Defect

    If behavior matches the requirements, the defect is rejected as 'Not a Defect' or 'Working as Designed'.

  7. What is the correct status transition immediately after a developer completes a code change to address a defect?

    Answer: Fixed / Ready for Retest

    After fixing, the defect moves to 'Fixed/Ready for Retest' so the tester can verify it.

  8. Severity in a defect report primarily measures what?

    Answer: The technical impact on the system

    Severity reflects the degree of impact a defect has on system functionality.

  9. Priority in a defect report primarily measures what?

    Answer: The urgency of fixing it

    Priority indicates how urgently a defect should be addressed in the schedule.

  10. Which combination is most realistic: a spelling error on the company's homepage banner?

    Answer: Low severity, high priority

    A cosmetic typo has low technical impact but high visibility, so it is often high priority.

  11. A rarely used admin report crashes only under an unusual data condition. Which classification fits best?

    Answer: High severity, low priority

    A crash is high severity, but rare use of the feature makes it low priority.

  12. Who typically assigns the priority of a defect?

    Answer: The project/test lead or triage team

    Priority is usually set by a lead or triage team weighing business needs and schedule.

  13. What is the main purpose of a defect triage meeting?

    Answer: To review, prioritize, and assign defects

    Triage meetings review open defects to set priority and assign owners.

  14. A 'Blocker' severity defect is best described as one that:

    Answer: Halts further testing or major functionality

    A blocker prevents continued testing or use of major functionality, demanding immediate attention.

  15. Why is a defect linked back to the original test case that found it?

    Answer: To provide traceability and context

    Linking to the test case gives traceability between requirements, tests, and defects.

  16. A defect previously marked 'Closed' is found again in a later build. What status should it receive?

    Answer: Reopened

    A recurring closed defect is 'Reopened' and linked to its original record.

  17. What is the primary goal of root cause analysis in defect management?

    Answer: To identify why the defect occurred and prevent recurrence

    Root cause analysis finds the underlying reason so similar defects can be prevented.

  18. Which metric measures the percentage of defects removed before a release ships?

    Answer: Defect Removal Efficiency

    Defect Removal Efficiency (DRE) measures the share of defects caught before release.

  19. Defect density is typically calculated as the number of defects per what?

    Answer: Unit of size (e.g., KLOC or function point)

    Defect density is defects divided by a size measure such as thousand lines of code.

  20. A defect's 'age' in the lifecycle is best defined as:

    Answer: Time elapsed since it was first reported

    Defect age measures how long a defect has been open since it was reported.

How this page was made: written with AI tools and published by Nathan Beja, founder of Practice Test Geeks, who is responsible for its content. Exam facts are checked against the official sources listed below. Not reviewed by a subject-matter expert. Editorial policy

Sources & references

Exam facts on this page (fees, format, dates, passing scores) are checked against these official sources; the date is our last check. Editorial policy

  1. seo.nlx.org — Passing score, time limit · verified Oct 2026
  2. pge.com — Retake policy · verified Oct 2026
  3. eei.org — Test delivery, eligibility, score release, score validity · verified Oct 2026