MLA-C01 Question 425
Select 3You are a Machine Learning Engineer managing an AWS environment with multiple teams working on various ML projects. The organization is concerned about untracked spending in the AWS account. To improve cost tracking and allocation, you decide to use resource tagging. Which of the following are best practices for implementing an effective tagging strategy to control costs?
- A
Use a consistent naming convention for tags across all ML resources.
- B
Tag only high-cost resources such as GPU-based instances and skip tagging low-cost resources like S3 buckets.
- C
Use AWS Cost Allocation Tags and activate them in the AWS Billing and Cost Management console.
- D
Create tags that include information about the project, team, and environment (e.g., 'Project:Alpha', 'Team:DataScience', 'Environment:Dev').
- E
Rely solely on default AWS-generated tags for cost tracking, as they cover all necessary information.
Show answer and explanation
Correct answers: A, C, D
Explanation
To effectively track and allocate costs in AWS for an organization with multiple ML projects, it is essential to use consistent and meaningful tags. AWS Cost Allocation Tags provide a powerful mechanism for cost tracking, and detailed custom tags (e.g., project, team, environment) enable granular visibility into spending. Relying only on AWS-generated tags or tagging only certain resources limits the ability to gain complete cost insights.
- A. Correct.
Using a consistent naming convention ensures that all resources are tagged uniformly, making it easier to filter and analyze costs based on tags.
- B. Incorrect.
Tagging only high-cost resources is not sufficient, as low-cost resources can cumulatively contribute to significant expenses. It's important to tag all relevant resources for comprehensive cost tracking.
- C. Correct.
AWS Cost Allocation Tags are specifically designed to help track and allocate costs. Activating them in the Billing and Cost Management console ensures they are included in cost reports.
- D. Correct.
Creating tags with detailed information about the project, team, and environment helps in granular cost allocation and analysis, which is a best practice for managing multi-team or multi-project AWS accounts.
- E. Incorrect.
Default AWS-generated tags provide limited information and should not be relied upon solely for cost tracking. Custom tags are necessary to capture organization-specific details.