AD0-E724 · Question #27
Which of the following is NOT a core principle of modular design in Adobe Commerce?
The correct answer is B. Inheritance over Composition. "Inheritance over Composition" is NOT a core modular design principle - in fact, it's the opposite of what modern modular architectures (including Adobe Commerce) recommend. The preferred principle is Composition over Inheritance, because inheritance creates tight coupling betwee
Question
Which of the following is NOT a core principle of modular design in Adobe Commerce?
Options
- AHigh Cohesion
- BInheritance over Composition
- CLow Coupling
- DSingle Responsibility
How the community answered
(22 responses)- A9% (2)
- B73% (16)
- C5% (1)
- D14% (3)
Explanation
"Inheritance over Composition" is NOT a core modular design principle - in fact, it's the opposite of what modern modular architectures (including Adobe Commerce) recommend. The preferred principle is Composition over Inheritance, because inheritance creates tight coupling between classes, making modules harder to replace or extend independently.
The three distractors are all genuine modular design principles:
- High Cohesion (A) means each module should have a focused, well-defined responsibility - keeping related logic together.
- Low Coupling (C) means modules should depend on each other as little as possible, so changes in one don't cascade through others.
- Single Responsibility (D) means each class or module should have exactly one reason to change - a cornerstone of clean modular architecture.
Memory tip: Think of the acronym SCL - Single responsibility, Cohesion, Low coupling - as the three real principles. "Inheritance over Composition" is a classic OOP anti-pattern trap; if an answer sounds like it encourages tighter class hierarchies, it's likely the wrong one for a question about modularity.
Topics
Community Discussion
No community discussion yet for this question.