SAA-C03 · Question #42
A company's application is deployed on Amazon EC2 instances and uses AWS Lambda functions for an event-driven architecture. The company uses nonproduction development environments in a different AWS…
The correct answer is C. Use Compute Savings Plans for the production instances. Use On-Demand Instances for the. Compute Savings Plansoffer the most flexible and cost-effective solution for the production instances, as they provide significant savings (up to 66%) for both EC2 and AWS Lambda usage, while allowing flexibility in the type of instance family, size, and even region. For…
Question
A company's application is deployed on Amazon EC2 instances and uses AWS Lambda functions for an event-driven architecture. The company uses nonproduction development environments in a different AWS account to test new features before the company deploys the features to production. The production instances show constant usage because of customers in different time zones. The company uses nonproduction instances only during business hours on weekdays. The company does not use the nonproduction instances on the weekends. The company wants to optimize the costs to run its application on AWS. Which solution will meet these requirements MOST cost-effectively?
Options
- AUse On-Demand Instances (or the production instances. Use Dedicated Hosts for the
- BUse Reserved instances for the production instances and the nonproduction instances Shut down
- CUse Compute Savings Plans for the production instances. Use On-Demand Instances for the
- DUse Dedicated Hosts for the production instances. Use EC2 Instance Savings Plans for the
How the community answered
(16 responses)- B6% (1)
- C88% (14)
- D6% (1)
Explanation
Compute Savings Plansoffer the most flexible and cost-effective solution for the production instances, as they provide significant savings (up to 66%) for both EC2 and AWS Lambda usage, while allowing flexibility in the type of instance family, size, and even region. For nonproduction instances, usingOn-Demand Instancesensures you only pay for the instances when they are running, and shutting them down during off-hours further optimizes cost. Key AWS features: Compute Savings Plans: Provide savings based on consistent usage, making it ideal for production environments with steady load. On-Demand Instances: Suitable for nonproduction environments that are used intermittently. Shutting them down when not in use avoids unnecessary costs. AWS Documentation: According to AWS's cost optimization best practices, using a combination of Savings Plans for production and On-Demand Instances for nonproduction environments that are used sparingly results in optimal cost savings.
Community Discussion
No community discussion yet for this question.