Which guideline is a well-architected design principle tor 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 for well-architected cloud applications.
Provisioning resources for peak capacity can lead to inefficiencies and increased costs; instead, cloud architectures should scale based on demand.
Designing for automated recovery from failure is essential for cloud applications, ensuring high availability and resilience by minimizing downtime and manual intervention.
Using tightly coupled components can lead to reduced flexibility and scalability; well-architected designs favor loosely coupled components for better maintainability and scalability.