Security · interview question

A bug appears around safe subprocess calls. What is the strongest first debugging move?

Multiple choiceMediumchapter-17-curatedpremiumsecuritysafe-subprocess-calls

python

import subprocess

subprocess.run(["python", "worker.py", "--mode", "sync"], check=True)

Solve the symptom with comments only and avoid changing the code shape around safe subprocess calls.Trace one concrete example, inspect the state transitions, and compare them to the intended rule before rewriting anything.Delay clarity until production traffic reveals the edge case and then patch it under pressure.Keep safe subprocess calls implicit so the script stays short and hope the next engineer infers the rule.

Answer and explanation

Correct answer

B. Trace one concrete example, inspect the state transitions, and compare them to the intended rule before rewriting anything.

Why

That approach is reliable because it creates evidence. 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 →

A bug appears around safe subprocess calls. What is the strongest first debugging move?

Correct answer

Why

More Security questions