A client from the banking industry operates its IBM Z environment in two data centers with a database of 10 kilometers (6.2 miles). Each data center has one IBM z14 and one DS8K storage system…

Question

Options

• AGDPS Metro Global Mirror
• BGDPS Metro HyperSwap Manager
• CGDPS Metro Global ?XRC
• DGDPS Global ?GM

• A
  28% (7)
• B
  48% (12)
• C
  16% (4)
• D
  8% (2)

Explanation

GDPS Metro HyperSwap Manager is correct because the scenario's defining requirement is near-continuous availability - and HyperSwap is the only GDPS technology that delivers this. It automatically redirects I/O to the secondary site without operator intervention and without a system IPL, achieving near-zero RTO. The existing 10km PPRC-enabled infrastructure maps perfectly to the Metro topology, and HyperSwap Manager supports adding a third site for long-distance disaster recovery through additional async replication.

Why the others fail:

• A (Metro Global Mirror): Global Mirror handles long-distance async replication, but this solution lacks the HyperSwap mechanism required for near-continuous availability - it provides DR, not HA.
• C (Metro Global XRC): XRC (Extended Remote Copy) is an older host-based async replication technology suited for long-distance DR, not for near-continuous availability in a metro configuration.
• D (Global GM): Pure Global Mirror addresses only the long-distance DR requirement and does nothing to provide near-continuous availability between the two existing metro sites.

Memory tip: Lock onto the phrase "near-continuous availability" - it's the exam's signal word for HyperSwap. Whenever you see that phrase alongside a metro distance (≤300km) and PPRC, the answer will involve HyperSwap Manager. Global Mirror = DR; HyperSwap = no-interruption HA.

No community discussion yet for this question.