Security · interview question

What is the healthiest performance judgment around safe subprocess calls?

Multiple choiceMediumchapter-17-curatedpremiumsecuritysafe-subprocess-calls

python

import subprocess

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

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

Answer and explanation

Correct answer

B. 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 safe subprocess calls?

Correct answer

Why

More Security questions