Security · interview question

Which move is the best default when safe subprocess calls becomes part of this workflow?

Multiple choiceMediumchapter-17-curatedpremiumsecuritysafe-subprocess-calls

Keep safe subprocess calls 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.Call subprocesses with explicit argument lists and clear error handling instead of shell-interpolated strings.Solve the symptom with comments only and avoid changing the code shape around safe subprocess calls.

Answer and explanation

Correct answer

C. Call subprocesses with explicit argument lists and clear error handling instead of shell-interpolated strings.

Why

Call subprocesses with explicit argument lists and clear error handling instead of shell-interpolated strings. That is the stronger engineering move because candidates who mention argument lists and boundaries sound safer to trust. String-built shell commands invite injection and make quoting bugs harder to reason about.

Test yourself on Security

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

Start free test

All Security questions →

Which move is the best default when safe subprocess calls becomes part of this workflow?

Correct answer

Why

More Security questions