Get App

Python: What deeper point about subprocess and Shell Boundary Safety should a senior Python developer mention?

Difficulty:

Hard

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

What deeper point about subprocess and Shell Boundary Safety should a senior Python developer mention?

  1. At senior level, the right answer is that subprocess and Shell Boundary Safety exists mostly for historical syntax reasons.
  2. Senior answers mention command injection risk, environment control, and why subprocess calls belong at explicit infrastructure seams.
  3. At senior level, Python removes the tradeoffs around subprocess and Shell Boundary Safety, so design choices barely matter in practice.
  4. At senior level, any approach to subprocess and Shell Boundary Safety is equally correct if it passes one small local test.

Hint

Look beyond syntax and explain the runtime, API, or design consequence.

Answer and rationale

Correct answer: B. Senior answers mention command injection risk, environment control, and why subprocess calls belong at explicit infrastructure seams.

Senior answers mention command injection risk, environment control, and why subprocess calls belong at explicit infrastructure seams. This is the kind of tradeoff-aware answer senior interviews usually expect.

Track: Python