VisionWorks is evaluating upfront commitments to reduce SageMaker compute costs and must understand how SageMaker Savings Plans compare to EC2 Savings Plans in scope and terms. Select TWO statements that correctly describe SageMaker Savings Plans.

The first correct statement accurately describes the commitment terms and payment options for SageMaker Savings Plans, which are standard for many AWS commitment-based pricing models. The second correct statement clarifies the scope, indicating that SageMaker Savings Plans are specific to SageMaker compute services (training, hosting, processing) and do not extend to general EC2 instances or other AWS services. The incorrect option "SageMaker Savings Plans automatically apply to EC2 instance usage across the account in addition to SageMaker usage" is wrong because SageMaker Savings Plans are distinct from EC2 Savings Plans and do not cover general EC2 usage. The option "SageMaker Savings Plans are applied retroactively to any usage in the previous 12 months when the plan is purchased" is incorrect because Savings Plans apply to future usage from the purchase date, not retroactively. The option "SageMaker Savings Plans work exactly like Reserved Instances and require explicitly assigning a plan to each SageMaker endpoint" is incorrect because Savings Plans are more flexible than Reserved Instances, automatically applying to eligible usage without requiring explicit assignment to specific resources.