MLA-C01 Practice Question 20: Cost Allocation Tags
AWS Certified Machine Learning Engineer – Associate (MLA-C01) · Test 2 · question 10 of 10
Three data science teams share one AWS account (not part of an organization) for SageMaker AI training jobs, processing jobs, and endpoints. Finance wants to see each team's monthly SageMaker AI spend in AWS Cost Explorer. An engineer has already added a team tag to every new SageMaker AI resource, but a week later Cost Explorer still offers no way to group or filter costs by team.
What must be done?
Show answer and explanation
Answer:
Tagging a resource is only half the job. A tag becomes a *cost allocation tag* only after it is activated in the Billing and Cost Management console; AWS states that both user-defined and AWS-generated tags must be activated before they can appear in Cost Explorer or on a cost allocation report. After activation, which can take up to 24 hours to appear, the team key can be used to group and filter SageMaker AI costs. Activation is done from the management account of an organization or, as here, from a standalone account.
Option A does not match how billing works. A domain is a Studio construct, not a billing dimension, and separate domains do not by themselves itemize training or endpoint charges by team.
Option B is the most common misconception. Tags do not become cost allocation tags on their own, no matter how long you wait; without activation they never appear.
Option C describes the wrong tool. Trusted Advisor checks surface optimization opportunities such as idle resources; they are not a tag-based cost breakdown.
References: Organizing and tracking costs using AWS cost allocation tags; Using user-defined cost allocation tags