What are the metrics describing GDPS Continuous Availability?

Question

Options

• ATwo or more active data centers in extended distance, RPO<1m and RTO<1m
• BTwo active data centers in extended distance, RPO>1m and RTO>1h
• CTwo data centers in metropolitan distance, RPO=0 and RTO=0
• DSingle data center, RPO=0

• A
  93% (28)
• B
  3% (1)
• D
  3% (1)

Explanation

Option A is correct because GDPS Continuous Availability is designed for extended-distance configurations with two or more active sites, delivering near-zero recovery objectives - RPO and RTO both under one minute - enabling workloads to survive a site failure with minimal disruption.

Why the distractors fail:

• B is wrong on the recovery metrics: RTO>1h is disaster recovery territory, not continuous availability, and RPO>1m reflects asynchronous replication (like Global Mirror), not CA.
• C describes GDPS Metro Mirror - synchronous replication achieves RPO=0 and RTO=0, but only across metropolitan distances, not extended distance.
• D is simply a single data center with no geographic redundancy, which is the opposite of what any GDPS solution provides.

Memory tip: Think of "Continuous Availability" as almost perfect but not quite - unlike synchronous Metro Mirror which hits the absolute zero mark, CA uses asynchronous-style stretched clustering over longer distances, so you get sub-minute (< 1m) rather than zero for both RPO and RTO. The phrase "CA = Close but not zero, at a Distance" can help you distinguish it from Metro Mirror's perfect zeros.

No community discussion yet for this question.