C1000-038 · Question #10
In an environment with one IBM z14 and one z/OS LPAR, what component would contribute to higher availability?
The correct answer is C. Parallel Sysplex. Parallel Sysplex is the correct choice because it is IBM's premier high-availability clustering architecture for z/OS, allowing multiple systems to work together as a single image - enabling workload balancing, automatic failover, and near-continuous operations. The question…
Question
In an environment with one IBM z14 and one z/OS LPAR, what component would contribute to higher availability?
Options
- ADual HMC setup
- BThree Phase Line cord
- CParallel Sysplex
- DRAIM Memory technology
How the community answered
(35 responses)- A3% (1)
- B6% (2)
- C83% (29)
- D9% (3)
Explanation
Parallel Sysplex is the correct choice because it is IBM's premier high-availability clustering architecture for z/OS, allowing multiple systems to work together as a single image - enabling workload balancing, automatic failover, and near-continuous operations. The question implies the need to expand beyond a single LPAR environment; implementing Parallel Sysplex addresses that gap directly.
Why the distractors are wrong:
- A (Dual HMC): A redundant Hardware Management Console protects your management access to the system, but if the z/OS LPAR itself fails, a second HMC does nothing to keep workloads running.
- B (Three Phase Line Cord): This is a power delivery component; while stable power matters, it's a prerequisite, not an availability architecture - it doesn't protect against software faults, planned outages, or workload peaks.
- D (RAIM Memory): RAIM (Redundant Array of Independent Memory) is a real z14 hardware feature that protects against memory failures, but it addresses a narrow hardware fault domain - it cannot recover from OS failures, application crashes, or planned maintenance windows the way Parallel Sysplex can.
Memory tip: Think of Parallel Sysplex as RAID for entire mainframe systems - just as RAID stripes data across multiple disks so one disk failure doesn't cause data loss, Sysplex spans workloads across multiple z/OS images so one system failure doesn't cause an outage. "Sysplex = System Complex = no single point of failure."
Topics
Community Discussion
No community discussion yet for this question.