What is the benefit of explicit dependencies in module design?

• A. It makes dependencies implicit and harder to track.
• B. It keeps modules hidden from each other and eliminates the need for interfaces.
• C. It prevents modules from being updated independently.
• D. It clarifies what a module relies on, aiding maintenance.

Answer: (D)

Explicit dependencies mean a module clearly states what it needs to operate, usually through well-defined interfaces or contracts. This clarity lets you see exactly what the module relies on, which makes maintenance much easier: you can reason about changes with confidence, update a dependency or swap implementations without breaking the rest of the system, and verify compatibility with targeted tests. It also supports better testing because you can inject mocks or fakes for those dependencies, and it reduces hidden coupling so new team members can understand the system more quickly. In short, knowing what a module depends on keeps boundaries clear and makes ongoing maintenance and evolution safer and simpler.