Security · interview question

Another engineer will maintain this code later. What choice helps the most around safe subprocess calls?

Multiple choiceMediumchapter-17-curatedpremiumsecuritysafe-subprocess-calls

Solve the symptom with comments only and avoid changing the code shape around safe subprocess calls.Make the rule obvious in names, flow, and boundaries so the next reader does not have to reverse-engineer your intent.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.

Answer and explanation

Correct answer

B. Make the rule obvious in names, flow, and boundaries so the next reader does not have to reverse-engineer your intent.

Why

Maintainability comes from explicit intent. Candidates who mention argument lists and boundaries sound safer to trust.

Test yourself on Security

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

Start free test

All Security questions →

Another engineer will maintain this code later. What choice helps the most around safe subprocess calls?

Correct answer

Why

More Security questions