CLI Design · interview question
Which boundary choice best fits runnable project shape in a maintainable Python system?
Multiple choiceHardchapter-6-curatedpremiumcli-designrunnable-project-shape
Answer and explanation
Correct answer
C. Keep the concern close to the data or API boundary that owns it instead of scattering it across unrelated helpers.
Why
Responsibility should follow ownership. When the concern lives near the right boundary, the system is easier to test and explain.
Test yourself on CLI Design
A free test with instant, explained results. No account needed.
More CLI Design questions
- Which response shows the healthiest evidence-first mindset around runnable project shape?
- Another engineer will maintain this code later. What choice helps the most around environment configuration?
- A teammate submits shaky runnable project shape code. Which review comment is the strongest?
- A senior interviewer asks for one tradeoff behind argparse and commands. What is the strongest follow-up?
- Another engineer will maintain this code later. What choice helps the most around runnable project shape?
- What assumption should be made explicit when working with runnable project shape?