Multiple ChoiceBeginner 45s
Module boundary enforcement via build
A team wants to guarantee that module A never imports module B's internal packages. What is the most robust enforcement?
Options
- 1A code review checklist instructing reviewers to manually watch for forbidden imports
- 2A comment in the README stating that module A must never import module B internals
- 3A weekly manual audit of module imports performed by the team lead across the codebase
- 4Build-time architecture tests / compiler-level access rules that fail CI on forbidden dependencies
Think you can answer under pressure?
Get matched and answer live questions in 3-minute 1v1 battles. Elo ranking, badge tiers and bragging rights on the line.