Q17 — AWS SAA-C03 Ch.12
Question 17 of 100 | ← Chapter 12
Q817. A company 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?
- A. Use On-Demand Instances for the production instances. Use Dedicated Hosts for the nonproduction instances on weekends only.
- B. Use Reserved Instances for the production instances and the nonproduction instances. Shut down the nonproduction instances when not in use.
- C. Use Compute Savings Plans for the production instances. Use On-Demand Instances for the nonproduction instances. Shut down the nonproduction instances when not in use. ✓
- D. Use Dedicated Hosts for the production instances. Use EC2 Instance Savings Plans for the nonproduction instances.
Correct Answer: C. Use Compute Savings Plans for the production instances. Use On-Demand Instances for the nonproduction instances. Shut down the nonproduction instances when not in use.
Explanation
Compute Savings Plans provide flexibility and cost savings for EC2 usage in exchange for a commitment to a consistent amount of compute usage (measured in dollars per hour) over a one or three-year term. By using Compute Savings Plans for the production instances, the company can benefit from cost savings while maintaining the constant usage required by customers in different time zones.For the nonproduction instances, using On-Demand Instances is appropriate since they are only used during business hours on weekdays. By utilizing On-Demand Instances, the company can pay only for the hours the nonproduction instances are running, reducing costs compared to using Reserved Instances that require a longer-term commitment.To further optimize costs, the nonproduction instances should be shut down when they are not in use, such as on weekends. This ensures that the company is not paying for unused resources.Using this combination of Compute Savings Plans for production instances, On-Demand Instances for nonproduction instances, and implementing shutdown schedules for nonproduction instances during weekends, the company can achieve cost optimization while still meeting its requirements.