A company's application runs on Amazon EC2 instances and uses AWS Lambda functions. Production runs constantly because of global customers. Nonproduction development environments run in a different AWS account and are used only during business hours on weekdays; they're idle on weekends. The company wants to optimize costs. Which solution is MOST cost-effective?

The correct solution optimizes costs by leveraging different pricing models for varying workloads. Compute Savings Plans offer significant discounts (up to 66%) for a consistent compute usage commitment, making them ideal for the constantly running production environment. For nonproduction instances, which are used intermittently, On-Demand Instances are suitable because you pay only for the compute capacity you use, with no long-term commitment. Shutting down these instances when not in use further reduces costs by stopping billing for compute time. Incorrect options: Using On-Demand for production is less cost-effective than Savings Plans for a constant workload. Dedicated Hosts are expensive and unnecessary for nonproduction environments that are only used during business hours. Reserved Instances for nonproduction instances would be wasteful if the instances are shut down frequently, as you pay for the reservation regardless of usage. Dedicated Hosts for production are generally more expensive and provide specific licensing benefits not mentioned as a requirement. EC2 Instance Savings Plans for nonproduction instances would still incur costs during idle periods unless explicitly shut down, and On-Demand combined with shutdown is more flexible for intermittent use.