The correct choice is Compute Savings Plans, EC2 Instance Savings Plans. These two Savings Plans let LumaBridge Analytics commit to a predictable hourly spend that applies across Amazon EC2, AWS Fargate, and AWS Lambda and they differ in flexibility and discount depth.

The Compute Savings Plans provide the broadest flexibility and automatically apply to usage across EC2, AWS Fargate, and AWS Lambda regardless of instance family, instance size, Region, operating system, or tenancy. This makes the compute plan the best fit when the goal is a consistent hourly commitment that covers multiple compute services. The EC2 Instance Savings Plans deliver larger discounts but require a commitment to a specific EC2 instance family within a Region so they are less flexible than the compute plan.

Instance Savings Plans, Storage Savings Plans is incorrect because there is no Storage Savings Plan and the term Instance Savings Plans is not the correct product name since Savings Plans are focused on compute usage only.

Reserved Instances Savings Plans, EC2 Instance Savings Plans is incorrect because Reserved Instances are a separate purchase model and the phrase Reserved Instances Savings Plans does not describe an AWS Savings Plans type.

Compute Savings Plans, Storage Savings Plans is incorrect because no Storage Savings Plan exists and storage services such as Amazon S3 and EBS are not covered by Savings Plans.

Full AWS Practitioner Certification Question