A company uses Amazon SageMaker Studio to develop an ML model. The company has a single SageMaker Studio domain. An ML engineer needs to implement a solution that provides an automated alert when Sage

Question

Options

• AAdd resource tagging by editing the SageMaker user profile in the SageMaker domain. Configure
• BAdd resource tagging by editing the SageMaker user profile in the SageMaker domain. Configure
• CAdd resource tagging by editing each user's IAM profile. Configure AWS Cost Explorer to send an
• DAdd resource tagging by editing each user's IAM profile. Configure AWS Budgets to send an alert

• A
  12% (5)
• B
  74% (31)
• C
  5% (2)
• D
  10% (4)

Explanation

Option B is correct because it combines the two right tools for this job: resource tagging via the SageMaker user profile (which propagates tags automatically to all compute resources that user launches, enabling accurate cost attribution) and AWS Budgets (which is specifically designed to trigger automated alerts when spending crosses a defined threshold).

Why the distractors fail:

• A also uses SageMaker user profile tagging (correct approach) but pairs it with AWS Cost Explorer, which is an analysis and visualization tool - it does not send automated threshold alerts.
• C uses IAM profiles for tagging (wrong layer) plus Cost Explorer (wrong tool for alerts) - a double miss.
• D gets Budgets right (correct alerting tool) but applies tags at the IAM profile level, which does not propagate to SageMaker-launched compute resources the way SageMaker user profile tags do.

Memory tip: Think "SageMaker tags stay in SageMaker" - configure tagging where the resources live (the SageMaker user profile), not at the IAM layer. Then remember Budgets = alerts, Cost Explorer = analysis; if the question says "alert when costs reach X," the answer always involves AWS Budgets.

No community discussion yet for this question.