Root Causes CT-ATLAS Practice Questions (Page 3)

Questions 11–15

1. 11application · medium

   A Scrum team notices that the same type of defect keeps reappearing in different user stories across multiple sprints. The team holds a retrospective and wants to identify the underlying cause rather than just fixing each occurrence. Which approach would best help the team uncover the root cause?

   • AConduct a 5 Whys session, asking 'why' iteratively until the team reaches a systemic cause.
   • BReview the test cases to ensure they cover all possible input combinations.
   • CCreate a Pareto chart to rank the defects by frequency and focus on the most common one.
   • DAssign a developer to fix the defects as they appear and track the time spent.
   Reveal Solution Discussion Select an answer first
2. 12foundation · easy

   During a retrospective, the team identifies that a recurring integration failure is caused by incomplete test data setup. What is the root cause in this scenario?

   • AIncomplete test data setup
   • BLack of automated tests
   • CThe integration failure itself
   • DThe test environment being too slow
   Reveal Solution Discussion Select an answer first
4. 13application · medium

   A team discovers that a defect was caused by a miscommunication between the product owner and the developers. The team wants to apply root cause analysis to prevent this from recurring. Which action is most aligned with the root cause?

   • AImplement a practice of having the product owner clarify acceptance criteria during sprint planning.
   • BIncrease the number of status meetings to improve communication.
   • CCreate a shared document for all project decisions.
   • DAsk the developers to write more detailed code comments.
   Reveal Solution Discussion Select an answer first
5. 14application · medium

   After a production incident, a team performs a root cause analysis and discovers that the defect was introduced because the acceptance criteria for a user story were ambiguous. The team wants to prevent similar issues in future sprints. What is the most effective next step?

   • AAsk the product owner to write more detailed user stories in the future.
   • BAdd a definition of ready checklist that requires unambiguous acceptance criteria before a story enters a sprint.
   • CSchedule a special retrospective after every production incident.
   • DIncrease the number of testers on the team to catch more defects during testing.
   Reveal Solution Discussion Select an answer first
6. 15application · medium

   A team is experiencing intermittent test failures that are difficult to reproduce. They suspect the failures are caused by test data contamination but are not sure. Which root cause analysis technique would be most effective in this situation?

   • AAsk the testers to manually verify the functionality each time a failure occurs.
   • BUse a fishbone diagram to categorize potential causes such as data, environment, and code.
   • CImmediately rewrite the test cases to be more robust.
   • DRun the tests repeatedly until they pass and then close the issue.
   Reveal Solution Discussion Select an answer first