A security architect is establishing high availability and resilience specifications for a mission-critical infrastructure deployment. Match each resiliency requirement or architectural challenge on the left with its corresponding technical mechanism or metric on the right.
- Eliminating single points of failure across web servers while seamlessly preserving active user sessions during node outagesStateful Load Balancing with VIP failover
- Defining the maximum tolerable duration of data loss measured in time prior to an unplanned service disruptionRecovery Point Objective (RPO)
- Preventing data corruption caused by concurrent writes when heartbeat communication fails between cluster nodesNode Fencing / STONITH (Shoot The Other Node In The Head)
- Providing storage-level disk redundancy allowing continuous operations despite a single drive failureRAID 5 / RAID 1 array configuration
Answer
The correct pairings are: 1. Preserving active user sessions across web server outages matches with Stateful Load Balancing with VIP failover; 2. Maximum tolerable duration of data loss matches with Recovery Point Objective (RPO); 3. Preventing data corruption during heartbeat failure matches with Node Fencing / STONITH; 4. Disk redundancy for continuous operation matches with RAID 5 / RAID 1 array configuration.
Each requirement directly aligns with its corresponding architectural control: RPO defines acceptable data loss interval; stateful load balancing preserves persistent connections across redundant nodes; STONITH node fencing prevents split-brain corruption in active-active/active-passive clusters; and RAID provides local disk fault tolerance.
Step-by-Step Solution
Key Concept
Resilience, High Availability, and Redundancy Mechanisms