Question 470
Which consideration should still be kept in mind when recommending AWS for this requirement? A team wants to select a lower-latency compute option while preserving a consistent user experience during rising demand.
Explanation
Correct Answer
The fastest individual resource can still be inefficient for an entire workload. This directly addresses the question rather than a different AWS use case. Performance efficiency aligns architecture and resource capabilities with observed workload needs. Recognize the requirement: Look for measured latency, concurrency, and suitability of resource choice. At a high level, evaluate compute options with representative workloads and scaling behavior. The intended outcome is: The service meets measured response objectives at its intended load. Keep in mind: The fastest individual resource can still be inefficient for an entire workload.
Incorrect Answers
Cost optimization includes measuring demand and selecting capacity commitment at an appropriate stage. That addresses a different mechanism; this question turns on The fastest individual resource can still be inefficient for.
Cost optimization is the Well-Architected pillar concerned with avoiding unnecessary spend. That observation may hold without resolving the relevant issue: The fastest individual resource can still be inefficient for.
Sustainability is the Well-Architected pillar focused on minimizing resource consumption and environmental impacts. It does not verify the requested outcome; here the decisive check concerns The fastest individual resource can still be inefficient for.