Which guideline is a well-architected design principle for building cloud applications?
Keep static data closer to compute resources.
Provision resources for peak capacity.
Design for automated recovery from failure.
Use tightly coupled components.
Explanations:
While keeping static data closer to compute resources can improve performance, it is not a primary design principle outlined in the AWS Well-Architected Framework. The focus is more on optimizing data accessibility and performance rather than strictly geographical proximity.
Provisioning resources for peak capacity can lead to inefficient resource utilization and increased costs. The Well-Architected Framework emphasizes using auto-scaling and other methods to optimize resource usage instead of over-provisioning for peak demand.
Designing for automated recovery from failure is a key principle of the AWS Well-Architected Framework. It encourages developers to build applications that can recover automatically from failures, ensuring high availability and resilience.
Using tightly coupled components can lead to reduced flexibility and scalability. The Well-Architected Framework advocates for loose coupling to allow for easier updates, maintenance, and scalability of cloud applications.