DOP-C02 Resilient Cloud Solutions Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Cache-aside pattern

  Why it's wrong here

  Cache-aside pattern (also known as lazy loading) improves read throughput by having the application first check a cache, then fall back to the underlying data store on a miss, and populate the cache on reads or writes. While it reduces database pressure and latency, it provides no failure detection or isolation for a downstream service; a failing dependency still sees calls proceed unabated, so it does nothing to prevent cascading failures.

• ✗

  Saga pattern

  Why it's wrong here

  Saga pattern coordinates distributed transactions across multiple services by breaking them into local transactions with compensating actions, ensuring eventual consistency without a distributed transaction manager. It addresses data consistency and atomicity concerns, but it is not a resilience pattern for failure isolation; it does not stop or limit calls to a failing service, so it cannot prevent the failure from propagating to other components.

• ✓

  Circuit breaker pattern

  Why this is correct

  Circuit breaker pattern monitors calls to a remote service and maintains three states—closed, open, and half-open—progressing to open when failure thresholds are exceeded, at which point subsequent calls fail fast without attempting the network operation. This prevents a failing service from being overwhelmed and stops the same repeated errors from saturating caller resources, thereby breaking the chain of cascading failures and giving the dependency time to recover.

• ✗

  Throttling pattern

  Why it's wrong here

  Throttling pattern (or rate limiting) intentionally caps the number of requests or concurrent operations a service can handle, often using queues to smooth bursts and protect the service from overload. However, throttling applies limits uniformly regardless of a dependency's health; it reduces load but does not distinguish a failing upstream service or divert traffic away from it, so it doesn't prevent cascading failures in a microservices mesh.

• ✓

  Bulkhead pattern

  Why this is correct

  Bulkhead pattern isolates each downstream dependency or service into its own thread pool, connection pool, or other resource partition, based on the ship-building design of watertight compartments. If one service exhausts or fails its pool, other pools remain unaffected, limiting the blast radius of the failure; this is a form of resource-level fault containment that complements circuit breakers.

Go deeper

Related to this question