Multiple Choice Questions on Bugs in Code for Elementary

📚 Quick Study Guide

• 🐞 What is a Bug? A bug is an error in your code that makes it not work as expected. Think of it like a typo, but for computers!
• 🔍 Syntax Errors: These are like grammar mistakes in your code. The computer doesn't understand what you're trying to say. Example: Misspelling a keyword like `whille` instead of `while`.
• 🧮 Logic Errors: These are errors in your thinking! The code runs, but it doesn't do what you want. Example: Adding instead of subtracting when you need to find the difference.
• 💡 Debugging: Debugging is the process of finding and fixing bugs in your code. Think of it like being a detective for your program!
• 📝 Common Debugging Tools: Print statements (to see what your code is doing), debuggers (special tools that step through your code), and rubber duck debugging (explaining your code to a rubber duck!).
• ✅ Testing: Always test your code! Try different inputs and see if it gives the correct output. This helps you catch bugs early.

🧪 Practice Quiz

1. What is a bug in computer code?
   1. A cute insect that lives in your computer.
   2. An error that causes the code to not work correctly.
   3. A feature that makes the code run faster.
   4. A type of computer virus.
2. Which type of error is like a grammar mistake in your code?
   1. Logic Error
   2. Runtime Error
   3. Syntax Error
   4. Semantic Error
3. What is the process of finding and fixing bugs called?
   1. Coding
   2. Debugging
   3. Compiling
   4. Designing
4. If your code runs, but gives the wrong answer, what type of error is it likely to be?
   1. Syntax Error
   2. Logic Error
   3. Compiler Error
   4. Hardware Error
5. What is a common debugging tool that involves explaining your code to an inanimate object?
   1. Print Statement Debugging
   2. Rubber Duck Debugging
   3. Debugger Tool
   4. Code Review
6. Why is testing important in coding?
   1. It makes the code look nicer.
   2. It helps catch bugs early.
   3. It makes the code run faster.
   4. It is not important.
7. Which of the following is NOT a common debugging technique?
   1. Using print statements
   2. Explaining your code to a rubber duck
   3. Ignoring errors until they go away
   4. Using a debugger