Examkin

Soru

Zorluk: OrtaReserved Instances and Savings Plans Optimization

An organization manages its cloud infrastructure using AWS Organizations with consolidated billing enabled. A SysOps administrator is tasked with optimizing compute costs for the following two distinct workloads:

1. A development workload consisting of Amazon EC2 m5.largem5.large instances that will be migrated to a serverless architecture using AWS Fargate and AWS Lambda over the next three months.
2. A production workload consisting of a steady-state fleet of Amazon EC2 c6i.xlargec6i.xlarge instances in the us−west−2us-west-2 region that is expected to remain unchanged for the next 1212 months.

Which of the following purchasing strategies should the administrator implement to maximize savings while minimizing the risk of unused commitments? (Select TWO.)

  1. Purchase a Compute Savings Plan to cover the development workload that is migrating to AWS Fargate and AWS Lambda.Cevap
  2. Purchase EC2 Instance Savings Plans targeting the c6ic6i instance family in the us−west−2us-west-2 region for the steady-state production workload.Cevap
  3. C
    Purchase EC2 Instance Savings Plans targeting the m5m5 instance family to cover the development workload during and after its migration.
  4. D
    Purchase Standard Regional Reserved Instances for the m5.largem5.large instances and modify them to cover the AWS Lambda functions after the migration is complete.
  5. E
    Purchase Compute Savings Plans under a member account and disable discount sharing so the commitment only applies to the EC2 instances in that account.

Cevap

Purchase a Compute Savings Plan to cover the development workload that is migrating to AWS Fargate and AWS Lambda, and purchase EC2 Instance Savings Plans targeting the c6ic6i instance family in the us−west−2us-west-2 region for the steady-state production workload.
Purchasing a Compute Savings Plan is correct for the development workload because Compute Savings Plans apply automatically to EC2, AWS Fargate, and AWS Lambda, regardless of changes in instance family, size, region, or compute service. Purchasing EC2 Instance Savings Plans targeting the c6ic6i instance family in us−west−2us-west-2 is correct for the production workload because it offers the highest discount for steady-state instances of a specific family in a single region when no changes to the family or region are expected.

Adım Adım Çözüm

1
Analyze the development workload requirements.
The development workload is currently on EC2 but is migrating to Fargate and Lambda. Compute Savings Plans are required here because they apply to EC2, Fargate, and Lambda, providing the necessary flexibility as the compute type changes.
Choosing a plan with broader scope avoids wasted commitments during architecture shifts.
2
Analyze the production workload requirements.
The production workload is steady-state, uses c6ic6i instances in us−west−2us-west-2, and will not change. EC2 Instance Savings Plans offer higher savings than Compute Savings Plans for a specific instance family in a specific region, making them the most cost-effective choice for this workload.
Matching the commitment type to the stability of the workload yields the highest discount.
3
Evaluate the incorrect options based on scope limits.
EC2 Instance Savings Plans and Reserved Instances do not apply to Lambda or Fargate services. Standard RIs cannot be converted to serverless commitments. Disabling consolidated billing sharing limits account scope but does not restrict resource type application.
Understanding scope boundaries helps identify and eliminate invalid configurations.

Anahtar Kavram

Selecting the optimal AWS Savings Plans type based on workload flexibility and stability requirements.
Tahmini Süre:2m 0s
Bu soruyu puanla

Konular

Reserved Instances and Savings Plans Optimization

Bu konudan daha fazla soru