A cruise ship's network infrastructure is failing as compartments flood sequentially. Network routes must be dynamically reconfigured as servers literally go underwater. The system prioritizes passenger communication and emergency services over crew Netflix access. Maintain network connectivity while the physical infrastructure sinks beneath the waves. The system must implement emergency protocols while gracefully degrading non-essential services. Your task: Keep the Wi-Fi alive as the ship goes Titanic—cutting off Netflix to the crew while streaming SOS in 4K to panicking influencers.
Why You're Doing This
This tests network resilience, dynamic routing, and priority-based resource allocation under catastrophic failure conditions. You're building a system that must maintain critical functionality while systematically losing infrastructure.
Take the W
✓ Maintains emergency communications as long as possible
✓ Prioritizes passenger safety over non-essential services
✓ Gracefully degrades network capabilities as infrastructure is lost
Hard L
✗ Loses emergency communications while maintaining entertainment
✗ Fails to reconfigure as infrastructure becomes unavailable
✗ Ignores flooding progression in network planning
Edge Cases
⚠ Bridge flooding before passenger areas
⚠ Equipment failing faster than flooding timeline
⚠ Passenger panic overwhelming communication channels
⚠ Rescue coordination requiring specific network configurations
Input Format:
Flooding status and equipment condition reports
Expected Output:
Network topology decision with priority allocations