Get App

Java: Which practice avoids a common mistake with JDBC and Prepared Statements?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with JDBC and Prepared Statements?

  1. Ignore the JDBC and Prepared Statements issue and rely on team discipline instead of APIs or contracts.
  2. Silence the JDBC and Prepared Statements problem by using raw types, broad catches, or shared mutable state.
  3. Do not concatenate raw user input into SQL and hope downstream validation will save the design.
  4. Prefer the version of JDBC and Prepared Statements that makes behavior less predictable as long as the code compiles.

Hint

Look for the option that protects correctness instead of hiding the problem.

Answer and rationale

Correct answer: C. Do not concatenate raw user input into SQL and hope downstream validation will save the design.

Do not concatenate raw user input into SQL and hope downstream validation will save the design. This is a common failure mode in real Java code and a frequent interview follow-up.

Track: Java