AWS Certified Solutions Architect - Professional
Get started today
Ultimate access to all questions.
A SaaS company has developed a multi-tenant environment using shared Amazon DynamoDB tables and AWS Lambda functions for application services. They aim to implement a tiered subscription model based on resource consumption per tenant, identified by a unique tenant ID in each Lambda request. The company has an AWS Cost and Usage Report (CUR) in their AWS account and seeks to allocate DynamoDB costs accurately to each tenant. What solution offers the most granular view of DynamoDB costs per tenant with minimal operational effort?
A SaaS company has developed a multi-tenant environment using shared Amazon DynamoDB tables and AWS Lambda functions for application services. They aim to implement a tiered subscription model based on resource consumption per tenant, identified by a unique tenant ID in each Lambda request. The company has an AWS Cost and Usage Report (CUR) in their AWS account and seeks to allocate DynamoDB costs accurately to each tenant. What solution offers the most granular view of DynamoDB costs per tenant with minimal operational effort?
Explanation:
Option A is correct because it provides a straightforward way to allocate DynamoDB costs per tenant with minimal operational effort. By tagging each table with the tenant ID and enabling this tag as a cost allocation tag in the AWS Billing and Cost Management console, the company can immediately distinguish costs associated with each tenant. This approach leverages existing AWS capabilities like cost allocation tags and the AWS Cost and Usage Report (CUR), removing the need for additional log processing or custom calculations. While other options involve more complex setups and additional Lambda functions or custom metrics, Option A offers the most efficient and automated way to achieve the desired granularity in cost allocation.