The application of the Redundant Implementation pattern helps increase the autonomy of:

Question

Options

• Aredundantly deployed services
• Bservice agents that perform load-balanced access to services that are not redundantly deployed
• Ccompositions that compose redundantly deployed services
• Dcore service logic contained within services that do not rely on the redundantly deployed service

• A
  89% (16)
• B
  6% (1)
• D
  6% (1)

Explanation

The Redundant Implementation pattern increases autonomy by deploying multiple instances of a service, ensuring that no single point of failure can bring down the service or anything depending on it. A is correct because the redundantly deployed services themselves gain autonomy - if one instance fails, others continue operating independently. C is correct because compositions that orchestrate these redundant services also gain autonomy; they are no longer blocked by the failure of a single service instance and can route around failures transparently.

B is wrong because load-balanced access to non-redundant services defeats the purpose - the underlying service is still a single point of failure, so autonomy is not meaningfully increased. D is wrong because services that don't interact with the redundant service are entirely unaffected by the pattern; their autonomy is neither helped nor harmed.

Memory tip: Think in two rings - the redundant service itself (A) is the inner ring, and the compositions that wrap it (C) are the outer ring. The pattern radiates autonomy outward from the redundant service to its consumers, but stops there - unrelated services (D) and services accessing non-redundant endpoints (B) are outside the pattern's reach.

No community discussion yet for this question.