AWS Well-Architected Performance Efficiency Design Principles
Which design principle aligns with performance efficiency pillar of the AWS Well-Architected Framework?
Community Votes
68% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests recall of the specific five design principles for Performance Efficiency; the common trap is confusing general scaling strategies with the defined architectural paradigms like serverless.
This question tests the five design principles of the AWS Well-Architected Framework's Performance Efficiency pillar, specifically identifying 'Use serverless architectures' as the correct principle. The page clarifies why horizontal scaling is categorized differently in this specific context.
Many learners select 'Scaling horizontally' because it is a performance technique, but it is not one of the five explicitly named design principles for this pillar in the official documentation.
Community Discussion (15 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
According to the AWS Well-Architected Framework documentation, the Performance Efficiency pillar has five specific design principles: Democratize advanced technologies, Go global in minutes, Use serverless architectures, Experiment more often, and Consider mechanical sympathy. Option A directly matches one of these core principles, which emphasizes delegating operational overhead to managed services to focus on value-adding activities.Why the Other Options Are Wrong
Option B (Scaling horizontally) is a valid strategy for achieving performance efficiency, but it is listed under the 'Reliability' or 'Performance Efficiency' implementation guidance rather than being one of the five high-level design principles. Option C relates to the Operational Excellence or Cost Optimization pillars. Option D (Using managed services) is a benefit of serverless but is not the principle name itself. While B contributes to efficiency, A is the specific principle defined by AWS.Community Comment Notes
The community is split between A and B. Users supporting A cite the official AWS blog and documentation listing 'Use serverless architectures' as a primary principle. Users supporting B argue that horizontal scaling is fundamental to performance. However, the consensus among experts aligns with the literal text of the framework's design principles list, favoring the explicit naming convention used in AWS training materials.Official Reference
Exam Strategy
Memorize the five distinct design principles for each of the six Well-Architected pillars. Do not confuse implementation strategies (like auto-scaling) with the overarching design principles (like serverless).
Frequently Asked Questions
Why isn't 'Scale horizontally' a design principle?
Horizontal scaling is an implementation strategy or tactic. The design principles are broader architectural concepts like 'Use serverless architectures' that guide how you approach building systems.
What are the other four Performance Efficiency principles?
The other four are: Democratize advanced technologies, Go global in minutes, Experiment more often, and Consider mechanical sympathy.
Related Analysis
Practice All CLF-C02 Questions
Access 120 questions with complete answers and detailed explanations.
View Full CLF-C02 Practice Test →