Zombie Apocalypse Xtreme DevOps

Par 8

Question 31advancedSheet 1750822302

Deep Breath

A distributed system must continue operating while servers are literally being eaten by zombies. The load balancer prioritizes routes based on server survival probability and zombie infestation levels. Infected servers send increasingly incoherent responses before going dark permanently. Your task: Maintain system uptime while servers are consumed by the undead horde.

Why You're Doing This

You're building a load balancer that must adapt to rapidly degrading infrastructure with predictable failure patterns. This tests dynamic resource allocation, failure prediction, graceful degradation, and disaster recovery planning. It's like AWS Auto Scaling but your instances are being literally consumed by external threats.

Take the W

✓ Routes traffic away from zombie-infected infrastructure
✓ Predicts server failure based on infection progression
✓ Maintains service availability during infrastructure loss

Hard L

✗ Routes traffic to obviously compromised servers
✗ Fails to account for infection spread patterns
✗ Complete service failure due to poor resource management

Edge Cases

⚠ All servers infected but some still partially functional
⚠ Zombie-immune server administrator continuing maintenance during apocalypse
⚠ Network infrastructure physically destroyed by zombie hordes
⚠ Successful zombie cure requiring rapid infrastructure restoration
⚠ Zombie servers forming their own malicious botnet with undead intelligence

Input Format:

server_status_array, zombie_metrics_object, traffic_requirements_config

Expected Output:

routing_decision_algorithm with health_monitoring_system

Example:

[{status:"healthy", coherence:0.95}, {status:"nibbled", coherence:0.7}], zombie_density:"high" → route_to_healthy_only(), monitor_degradation(), prepare_fallback_systems()

Input Format:

server_health_vector, infection_probability_matrix, load_distribution_requirements

Expected Output:

optimal_routing_weights, failure_prediction_timeline, resource_allocation_strategy

Example:

health=[1.0, 0.6, 0.1], infection_rate=0.3/hour, load=balanced_distribution → weights=[0.8, 0.2, 0.0], failure_time=3.2_hours, strategy=graceful_degradation

Hints

💡 Zombie progression: healthy → scratched → nibbled → infected → zombie_server → offline
💡 Infection spread follows network topology and physical proximity
💡 Early evacuation preserves more infrastructure than fighting inevitable doom

← Question 30 Question 32 →