Question

1. which method of finding errors is most useful to identify logic errors? *

a. creating new test cases
b. hand-tracing
c. rerunning the program with different inputs to see the impact on outputs
d. running a simulation

1. attempting to access an invalid index in a list results in what type of error? * 1 po

a. logic error
b. overflow error
c. runtime error
d. syntax error

1. what is an example of event - driven programming? * 1 point

a. prompting a user to type in a response
b. using constants for data values in place of variables
c. a mobile device that orients to a new position
d. a microphone transmitting audio data to a program

Explanation:

Question 16

To identify logic errors, hand - tracing (going through the code step - by - step manually) is very effective. Creating new test cases is more for finding other types of errors or validating functionality. Rerunning with different inputs is good for seeing output changes but not the best for logic errors. Running a simulation is not the primary method for logic error identification.

When we try to access an invalid index in a list, this error occurs while the program is running. A logic error is about flawed logic in the code's algorithm. An overflow error is related to exceeding the capacity of a data type. A syntax error is about violating the language's syntax rules. So, it's a runtime error.

Event - driven programming is based on events (like a change in position of a mobile device). Prompting a user for a response is more of an input operation. Using constants instead of variables is a coding style choice. A microphone transmitting audio data is a data input process, not event - driven in the sense of reacting to an event like device orientation change.

Answer:

B. Hand - tracing

Question 17