Question

Difficulty: Very hardAWS Pricing Calculator

A financial technology company is planning to migrate its legacy on-premises payment processing platform to a serverless architecture on AWS using AWS Lambda, Amazon DynamoDB, and Amazon S3. The finance team requires an initial estimation of the monthly operational costs for this proposed architecture, including comparisons of various pricing options, before any AWS resources are provisioned. Which of the following tasks can be accomplished using the AWS Pricing Calculator to meet these requirements? (Select TWO.)

  1. Estimate the monthly operational costs of the serverless architecture by inputting hypothetical usage metrics, such as estimated Lambda invocations and DynamoDB read/write capacity units.Answer
  2. Evaluate the cost difference between different pricing models, such as choosing On-Demand versus Provisioned Capacity with commitments for DynamoDB.Answer
  3. C
    Connect to AWS Budgets to automatically enforce cost limits and disable Lambda functions if the estimated spending threshold is exceeded.
  4. D
    Analyze the hourly granularity of the projected costs by generating a hypothetical AWS Cost & Usage Report (CUR) before resource creation.
  5. E
    Retrieve historical utilization logs from on-premises servers to automatically populate the pricing inputs for the serverless compute resources.

Answer

The team can estimate the monthly operational costs by inputting hypothetical usage metrics (such as Lambda invocations and DynamoDB capacity units) and evaluate the cost difference between different pricing models (such as On-Demand versus Provisioned Capacity).
The AWS Pricing Calculator is designed for estimating future cloud costs based on hypothetical parameters. It allows users to estimate monthly costs by inputting expected usage metrics (like Lambda invocation numbers or database capacity units) and compare various pricing structures (such as On-Demand versus Provisioned Capacity) to identify the most cost-effective strategy before launching the workloads.

Step-by-Step Solution

1
Determine the phase of the resource lifecycle described in the scenario.
The workload is in the pre-deployment phase, meaning no AWS resources have been provisioned yet.
Cost estimation needs differ depending on whether the workload is active or hypothetical.
2
Identify the tools capable of modeling hypothetical configurations.
The AWS Pricing Calculator is the correct tool for estimating costs based on hypothetical resource shapes and usage details.
It allows entering planned configuration metrics like Lambda execution counts and DynamoDB capacity to generate an estimate.
3
Evaluate pricing model comparisons within the planning tool.
The AWS Pricing Calculator allows comparing On-Demand versus commitment-based pricing options to find the most cost-effective approach.
This directly fulfills the requirement to compare various pricing options before provisioning.
4
Eliminate post-deployment monitoring and reporting tools.
AWS Budgets and the AWS Cost & Usage Report are excluded because they rely on actual post-deployment tracking and billing logs.
These tools cannot model hypothetical resources or ingest on-premises logs to generate pricing estimates.

Key Concept

AWS Pricing Calculator features and usage boundaries for pre-deployment cost modeling
Estimated Time:2m 0s
Rate this question