Pegasystems Certified Lead System Architect (CLSA) PEGACPLSA23V1 Question # 11 Topic 2 Discussion

Comprehensive and Detailed Explanation From Exact Extract:

High-availability (HA) architecture in Pega, as described in Pega Academy’sLead System Architect Missionand thePega Certified Lead System Architect Study Guide, is designed to ensure continuous service by mitigating single points of failure. Failover mechanisms are critical for maintaining service continuity in mission-critical applications like online banking.

Option A (Incorrect): Regular data backups via a Job Scheduler every five minutes are important for data recovery but do not address runtime single points of failure. Backups are a recovery mechanism, not an HA principle, per theHigh-Availabilitymodule.

Option B (Incorrect): A single administrative access group increases the risk of common cause failures (e.g., misconfiguration affecting all nodes) rather than avoiding them. HA requires isolated configurations, as noted in theSecurity Designmodule.

Option C (Correct): Implementing reliable failover ensures that if a node fails, the system transitions to a backup node without data loss, maintaining service continuity. Pega’s HA architecture supports failover through clustering and load balancing, as documented in theHigh-Availability Configurationsection.

Option D (Incorrect): While detectability of failures via health monitoring tools is important, it is a supporting mechanism, not the primary principle for mitigating single points of failure. Failover is the core HA strategy, per thePega Platform Architecturemodule.