Which disaster recovery pattern involves two sites both actively handling traffic to improve availability?

Which disaster recovery pattern involves two sites both actively handling traffic to improve availability?

• A. Active-active across sites
• B. Active-passive failover
• C. Hot standby
• D. Cold standby

Answer: (A)

The pattern being tested is when two sites both actively handle traffic to improve availability. In this setup, production workloads run at both locations at the same time, with traffic split between them via a load balancer. Keeping both sites live means there’s no single point of failure for user requests, so if one site experiences an issue, the other can continue serving with little or no downtime. Synchronous or near-synchronous replication is often used to keep data consistent between sites, which helps maintain seamless operation during failures. Why this is the best fit: it directly describes both sites actively processing requests, delivering higher availability and resilience than configurations where only one site handles traffic at a time. It also supports load distribution and faster failover because both sites are already in production. Compared to other patterns, those involve having one site idle or on standby. An active-passive failover keeps one site serving while the other waits; a hot standby keeps a backup ready to take over but not necessarily handling traffic in parallel, depending on the setup; a cold standby is offline until a disaster occurs and is not serving traffic at all.

The pattern being tested is when two sites both actively handle traffic to improve availability. In this setup, production workloads run at both locations at the same time, with traffic split between them via a load balancer. Keeping both sites live means there’s no single point of failure for user requests, so if one site experiences an issue, the other can continue serving with little or no downtime. Synchronous or near-synchronous replication is often used to keep data consistent between sites, which helps maintain seamless operation during failures.

Why this is the best fit: it directly describes both sites actively processing requests, delivering higher availability and resilience than configurations where only one site handles traffic at a time. It also supports load distribution and faster failover because both sites are already in production.

Compared to other patterns, those involve having one site idle or on standby. An active-passive failover keeps one site serving while the other waits; a hot standby keeps a backup ready to take over but not necessarily handling traffic in parallel, depending on the setup; a cold standby is offline until a disaster occurs and is not serving traffic at all.