AWS Certified Solutions Architect - Associate
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
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 of AWS 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?
Other
Community
UAnonymous
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.
Explanation:
Explanation
The correct answer is A because:
-
Management Account Activation: When using AWS Organizations, cost allocation tags must be activated from the management account to apply across all member accounts. This ensures the tag tracking works organization-wide.
-
User-Defined Cost Allocation Tag: The company is using a custom tag named "department" (not an AWS-defined tag like "aws:createdBy"). User-defined cost allocation tags must be activated to track costs by those tags.
-
Operational Efficiency: Activating the tag once from the management account is the most operationally efficient approach, as it automatically applies to all member accounts without needing separate configurations.
-
Cost Explorer Reporting: Once activated, Cost Explorer can group costs by the "department" tag across all accounts and filter specifically for EC2 consumption.
Why other options are incorrect:
- B: AWS-defined tags are pre-defined by AWS (like "aws:createdBy"), not custom tags like "department".
- C & D: Activating from member accounts would only apply to that specific account, not organization-wide, requiring separate activation for each account.
Key AWS Concepts:
- Cost Allocation Tags: Must be activated before AWS can track costs by those tags
- AWS Organizations: Management account controls organization-wide settings
- Cost Explorer: Can filter by service (EC2) and group by activated tags across all linked accounts