A company is running applications on Amazon EC2 instances in the same AWS account for several different projects. The company wants to track the infrastructure costs for each of the projects separately. The company must conduct this tracking with the least possible impact to the existing infrastructure and with no additional cost.
What should the company do to meet these requirements?
A . Use a different EC2 instance type for each project.
B . Publish project-specific custom Amazon CloudWatch metrics for each application.
C . Deploy EC2 instances for each project in a separate AWS account.
D . Use cost allocation tags with values that are specific to each project.
Answer: D
Explanation:
The correct answer is D because cost allocation tags are a way to track the infrastructure costs for each of the projects separately. Cost allocation tags are key-value pairs that can be attached to AWS resources, such as EC2 instances, and used to categorize and group them for billing purposes. The other options are incorrect because they do not meet the requirements of the question. Use a different EC2 instance type for each project does not help to track the costs for each project, and may impact the performance and compatibility of the applications. Publish project-specific custom Amazon CloudWatch metrics for each application does not help to track the costs for each project, and may incur additional charges for using CloudWatch. Deploy EC2 instances for each project in a separate AWS account does help to track the costs for each project, but it impacts the existing infrastructure and incurs additional charges for using multiple accounts.
Reference: Using Cost Allocation Tags
Latest CLF-C02 Dumps Valid Version with 370 Q&As
Latest And Valid Q&A | Instant Download | Once Fail, Full Refund