H13-821_V3.0 · Question #280
When designing the system architecture, in order to make complex business modules cooperate more closely and achieve parallelism of multiple tasks, the architecture should be as tightly coupled as…
The correct answer is B. False. Option B is correct because tight coupling is a design anti-pattern, not a goal. In well-designed systems, loose coupling between modules allows teams to develop, test, deploy, and scale components independently, which is what actually enables true parallelism and agility…
Question
When designing the system architecture, in order to make complex business modules cooperate more closely and achieve parallelism of multiple tasks, the architecture should be as tightly coupled as possible.
Options
- ATrue
- BFalse
How the community answered
(25 responses)- A24% (6)
- B76% (19)
Explanation
Option B is correct because tight coupling is a design anti-pattern, not a goal. In well-designed systems, loose coupling between modules allows teams to develop, test, deploy, and scale components independently, which is what actually enables true parallelism and agility. Tight coupling creates hidden dependencies that force modules to change together, slowing development and making failures cascade across the system. Option A is wrong because it misidentifies tight coupling as a means to achieve cooperation and parallelism, when in reality coordination between modules should happen through well-defined interfaces and contracts, not shared internals or direct dependencies.
Memory tip: Think of coupling like power outlets - a standard plug interface (loose coupling) lets any device work independently, while hardwiring every appliance together (tight coupling) means fixing one breaks them all.
Topics
Community Discussion
No community discussion yet for this question.