AWS Certified Solutions Architect – Associate (SAA-C03) — Question 448

A company uses AWS Organizations to run workloads within multiple AWS accounts. A tagging policy adds department tags to AWS resources when the company creates tags.

An accounting team needs to determine spending on Amazon EC2 consumption. The accounting team must determine which departments are responsible for the costs regardless ofAWS account. The accounting team has access to AWS Cost Explorer for all AWS accounts within the organization and needs to access all reports from Cost Explorer.

Which solution meets these requirements in the MOST operationally efficient way?

Answer options

• A. From the Organizations management account billing console, activate a user-defined cost allocation tag named department. Create one cost report in Cost Explorer grouping by tag name, and filter by EC2.
• B. From the Organizations management account billing console, activate an AWS-defined cost allocation tag named department. Create one cost report in Cost Explorer grouping by tag name, and filter by EC2.
• C. From the Organizations member account billing console, activate a user-defined cost allocation tag named department. Create one cost report in Cost Explorer grouping by the tag name, and filter by EC2.
• D. From the Organizations member account billing console, activate an AWS-defined cost allocation tag named department. Create one cost report in Cost Explorer grouping by tag name, and filter by EC2.

Correct answer: A

Explanation

To track custom tags like "department" in AWS Cost Explorer, they must be activated as user-defined cost allocation tags, because AWS-defined tags are reserved for AWS-generated metadata. Additionally, cost allocation tags for an AWS Organization must be enabled from the billing console of the management account to aggregate costs across all member accounts. Activating the tag in the management account and filtering the Cost Explorer report by EC2 while grouping by the department tag satisfies all requirements.