Which actions are examples of a company’s effort to rightsize its AWS resources to control cloud costs?

Explanations:

Switching from Amazon RDS to Amazon DynamoDB is more about changing database technologies to accommodate specific use cases (NoSQL datasets) rather than directly resizing resources to control costs. While it may result in cost savings in certain scenarios, it does not represent a direct effort to optimize existing AWS resource utilization.

Basing the selection of Amazon EC2 instance types on past utilization patterns is a direct method to rightsize AWS resources. By analyzing historical usage data, companies can select instance types that match their workload requirements, potentially reducing costs by avoiding over-provisioning and ensuring they pay only for the capacity they actually need.

Using Amazon S3 Lifecycle policies to move infrequently accessed objects to lower-cost storage tiers is an effective strategy for controlling costs. This action optimizes storage expenses by automatically transitioning data to cheaper storage classes, reducing overall storage costs while maintaining data accessibility.

Using Multi-AZ deployments for Amazon RDS is primarily a high availability feature, ensuring that the database remains operational in case of failures. While it may indirectly help with operational costs by minimizing downtime, it does not directly contribute to right-sizing resources or controlling cloud costs, as it involves additional cost for standby resources.

Replacing existing Amazon EC2 instances with AWS Elastic Beanstalk is a shift to a managed service platform, which may simplify deployment and scaling but does not inherently control costs or rightsize resources. Elastic Beanstalk manages resources for you, but the underlying resource utilization may still be inefficient if not monitored or optimized properly.