Which architecture design principle describes the need to isolate failures between dependent components in the AWS Cloud?

Question

Options

• AUse a monolithic design.
• BDesign for automation.
• CDesign for single points of failure.
• DLoosely couple components.

• A
  4% (1)
• B
  7% (2)
• D
  89% (24)

Explanation

Loosely coupling components is the correct principle because it ensures that failures in one component do not cascade or propagate to dependent components - each service or module operates as independently as possible, with well-defined interfaces (like queues or APIs) acting as buffers between them. A monolithic design (A) is the opposite approach, tightly binding all components together so that a failure in one part can bring down the entire system. Designing for automation (B) is a valid AWS principle focused on reducing manual effort and enabling self-healing, but it does not specifically address isolating failures between components. Designing for single points of failure (C) is actually an anti-pattern - AWS best practice is to eliminate single points of failure, not design for them.

Memory Tip: Think of loose coupling like electrical circuit breakers in your home - if one circuit fails, the others keep working. Tight coupling (monolithic) is like one master switch that takes everything down. "Loose = Isolated, Tight = Domino effect."

No community discussion yet for this question.