Security · interview question
What is the clearest sign that code around safe subprocess calls should be refactored?
Multiple choiceMediumchapter-17-curatedpremiumsecuritysafe-subprocess-calls
Answer and explanation
Correct answer
B. When the rule is no longer easy to trace, explain, or change without breaking nearby behavior.
Why
A refactor is justified when the code stops communicating its intent. Call subprocesses with explicit argument lists and clear error handling instead of shell-interpolated strings.
Test yourself on Security
A free test with instant, explained results. No account needed.
More Security questions
- What is the healthiest performance judgment around secrets management?
- What is the clearest sign that code around secrets management should be refactored?
- Which boundary choice best fits log redaction in a maintainable Python system?
- If input validation fails in production, what handling philosophy is strongest?
- Which response shows the healthiest evidence-first mindset around input validation?
- When is log redaction being used in the wrong way?