Debugging Quiz: Finding What Is Broken

Debugging: Finding What Is Broken offers ten conceptual questions, with no calculations. Every answer is explained.

Free, with no sign-up.

For High school students and adults reviewing the topic.

About 12 minutes. 10 questions.

How does it work?

  1. Choose one answer, then check it.

What will you get?

Review a score and an explanation for every answer.

Question 1A user reports that a result is wrong, but the written requirement matches the output. What should the investigator clarify first?
Question 2In a calculation, a valid statement subtracts a fixed amount when the requirement calls for a percentage reduction. What type of fault is this?
Question 3After a programmer changes a condition, a dependency, and a cache, a failing case passes. Which causal conclusion is justified?
Question 4An intermittent failure depends on the order in which two requests arrive. What makes the investigation repeatable?
Question 5During an investigation, a developer needs variable values at a particular instruction while execution is paused. Which tool serves that purpose?
Question 6A repair has been understood and checked. Which artifact best protects against its recurrence?
Question 7A crash is hidden by replacing a missing required address with an empty string. What investigation remains?
Question 8On a colleague’s machine, a failure occurs but does not occur on the developer’s. Which comparison is useful?
Question 9A robot’s failing motion could damage nearby equipment. How should the team investigate safely?
Question 10An unfamiliar program gives a wrong result at a documented interface. What is a focused starting approach?

Answer every question to see and share your score.

Read the topic guide