Get App

Java: When should a Java developer choose JDBC and Prepared Statements deliberately?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

When should a Java developer choose JDBC and Prepared Statements deliberately?

  1. Choose JDBC and Prepared Statements mainly when you want to postpone validation and fix problems manually later.
  2. Use prepared statements for user input, repeated queries, and any workflow where SQL parameters change per call.
  3. Choose JDBC and Prepared Statements whenever you want the code to look more advanced, even if the design gets less clear.
  4. Choose JDBC and Prepared Statements only to avoid modeling domain rules explicitly in Java code.

Hint

Think about the production scenario where the choice genuinely improves the code.

Answer and rationale

Correct answer: B. Use prepared statements for user input, repeated queries, and any workflow where SQL parameters change per call.

Use prepared statements for user input, repeated queries, and any workflow where SQL parameters change per call. Interviewers often ask this to see whether you can connect the concept to real design decisions.

Track: Java