Examkin

Question

Difficulty: MediumCost Allocation Tags and Resource Tagging Strategies

A SysOps Administrator uses AWS CloudFormation StackSets to deploy infrastructure templates containing a resource-level tag with the key `BillingDept` across multiple target AWS accounts in AWS Organizations. The administrator verifies that the tags are successfully applied to all deployed resources. However, when opening AWS Cost Explorer in the organization's management account, the `BillingDept` tag is not available to filter or group the cost data.

Which action must the administrator take to resolve this issue?

  1. Access the AWS Billing and Cost Management console from the organization's management account, and activate the `BillingDept` tag as a cost allocation tag.Answer
  2. B
    Access the AWS Billing and Cost Management console individually in each target member account, and activate the `BillingDept` tag as a cost allocation tag.
  3. C
    Wait for the next consolidated billing cycle to finalize, as tags applied to existing resources require a new invoice generation to become active.
  4. D
    Configure AWS Resource Access Manager (RAM) to share the `BillingDept` tag metadata from the member accounts with the management account.

Answer

Access the AWS Billing and Cost Management console from the organization's management account, and activate the BillingDept tag as a cost allocation tag.
Activating the tag in the management account's Billing and Cost Management console is required because user-defined cost allocation tags do not automatically become active for billing reports upon creation. They must be explicitly activated by the management account of the organization to start appearing in AWS Cost Explorer.

Step-by-Step Solution

1
Identify where the cost allocation tags are centrally managed in a multi-account organization.
The management account is determined to be the central point of configuration for consolidated billing and Cost Explorer settings.
Cost Explorer filters and billing reports for the entire organization are run from the management account.
2
Determine the activation status of the new custom tag.
Realize that custom tags are not active for cost allocation automatically upon resource tagging or template deployment.
AWS requires explicit opt-in activation for user-defined tags to be processed by the billing engine.
3
Perform the activation of the tag in the Billing console of the management account.
The tag is marked as active under the Cost Allocation Tags section.
Once activated, AWS starts tracking costs associated with this tag, and the tag becomes available in Cost Explorer within 24 hours.

Key Concept

User-defined cost allocation tags must be manually activated in the management account of an AWS Organization to be visible in Cost Explorer.
Rate this question

Topics

Cost Allocation Tags and Resource Tagging Strategies

More questions from this topic