Explanation
Design for automated recovery from failure is a core well-architected design principle in cloud computing because:
- Resilience: Cloud applications should automatically detect failures and recover without manual intervention
- High Availability: Automated recovery ensures minimal downtime and maintains service continuity
- Cloud Best Practice: This aligns with AWS Well-Architected Framework's Reliability pillar
- Cost Efficiency: Reduces the need for manual intervention and operational overhead
Why other options are incorrect:
- Keep static data closer to compute resources: While this can improve performance, it's not a fundamental design principle
- Provision resources for peak capacity: This is actually an anti-pattern in cloud computing; you should provision for average usage and scale as needed
- Use tightly coupled components: This creates dependencies that reduce flexibility and resilience, which contradicts cloud best practices