Security · interview question

What is the healthiest performance judgment around sql injection prevention?

Multiple choiceMediumchapter-17-curatedpremiumsecuritysql-injection-prevention

python

connection.execute(
    "SELECT id FROM orders WHERE id = ?",
    (order_id,),
)

Keep sql injection prevention implicit so the script stays short and hope the next engineer infers the rule.Delay clarity until production traffic reveals the edge case and then patch it under pressure.Measure before optimizing, then change the part that actually dominates cost instead of guessing from style alone.Solve the symptom with comments only and avoid changing the code shape around sql injection prevention.

Answer and explanation

Correct answer

C. Measure before optimizing, then change the part that actually dominates cost instead of guessing from style alone.

Why

Premature optimization is usually weaker than targeted optimization backed by measurement.

Test yourself on Security

A free test with instant, explained results. No account needed.

Start free test

All Security questions →

What is the healthiest performance judgment around sql injection prevention?

Correct answer

Why

More Security questions