A customer is planning a Disaster Recovery solution based upon two data centers, located within 80 km of each other. In case of a disaster, zero data loss coupled with automated recovery is a…

Question

Options

• ASRDF Hardware Based Global Mirror with FlashCopy
• BGDPS Metro and FlashCopy
• CGDPS Hardware Based Global Mirror with Hyperswap
• DGDPS Metro and Hyperswap

• A
  16% (5)
• B
  19% (6)
• C
  6% (2)
• D
  58% (18)

Explanation

GDPS Metro uses synchronous replication, meaning every write is committed to both sites simultaneously - guaranteeing zero data loss (RPO = 0). Hyperswap provides the automated failover, transparently switching workloads to the secondary site without operator intervention, satisfying the automated recovery requirement. The 80 km distance is comfortably within Metro Mirror's synchronous replication range (~300 km limit).

Why the distractors fail:

• A (SRDF + FlashCopy): SRDF is Dell EMC technology, not IBM GDPS. Global Mirror is asynchronous, meaning data loss is possible. FlashCopy is a point-in-time snapshot, not an automated failover mechanism.
• B (GDPS Metro + FlashCopy): Metro Mirror satisfies zero data loss, but FlashCopy cannot automate recovery - it's a local copy tool, not a failover solution.
• C (GDPS Global Mirror + Hyperswap): Global Mirror is asynchronous replication, which introduces a potential data loss window (non-zero RPO), violating the zero data loss requirement.

Memory tip: Match each requirement to a technology - "Metro = synchronous = zero loss" and "Hyperswap = auto-swap = automated recovery." Whenever you see both RPO=0 and automated failover together, the answer must pair Metro (synchronous) with Hyperswap (automation).

No community discussion yet for this question.