A company is running a workload in the AWS Cloud. Which AWS best practice ensures the MOST cost-effective architecture for the workload?

Question

Options

• ALoose coupling
• BRightsizing
• CCaching
• DRedundancy

• B
  92% (23)
• C
  4% (1)
• D
  4% (1)

Explanation

Rightsizing for Cost-Effective Architecture

Rightsizing (B) is correct because it directly addresses cost optimization by matching the size and type of AWS resources (such as EC2 instances) to the actual workload requirements - eliminating waste from over-provisioned resources and avoiding performance issues from under-provisioned ones. AWS specifically promotes rightsizing as a core pillar of its Cost Optimization best practice framework.

Why the distractors are wrong:

• Loose coupling (A) improves resilience and scalability by reducing dependencies between components, but is primarily an architectural/reliability practice, not a cost-optimization strategy
• Caching (C) can reduce costs indirectly by lowering database load, but its primary purpose is improving performance, not directly optimizing cost
• Redundancy (D) improves availability and fault tolerance, but actually increases costs by duplicating resources

Memory Tip: Think of "Right"sizing as paying the "right" price - you only pay for exactly what you need. If the question asks about cost, think Rightsizing first. The other options are great practices but serve different primary purposes (resilience, performance, and availability).

No community discussion yet for this question.