BlackFriday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon Exam SAA-C03 Topic 12 Question 29 Discussion

Actual exam question for Amazon's SAA-C03 exam
Question #: 29
Topic #: 12
[All SAA-C03 Questions]

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'?

Show Suggested Answer Hide Answer
Suggested Answer: B

This solution meets the following requirements:

It is operationally efficient, as it only requires one activation of the cost allocation tag and one creation of the cost report from the management account, which has access to all the member accounts' data and billing pReference.

It is consistent, as it uses the AWS-defined cost allocation tag named department, which is automatically applied to resources when the company creates tags using the tagging policy enforced by AWS Organizations. This ensures that the tag name and value are the same across all the resources and accounts, and avoids any discrepancies or errors that might arise from user-defined tags.

It is informative, as it creates one cost report in Cost Explorer grouping by the tag name, and filters by EC2. This allows the accounting team to see the breakdown of EC2 consumption and costs by department, regardless of the AWS account. The team can also use other features of Cost Explorer, such as charts, filters, and forecasts, to analyze and optimize the spending.


Using AWS cost allocation tags - AWS Billing

User-defined cost allocation tags - AWS Billing

Cost Tagging and Reporting with AWS Organizations

Contribute your Thoughts:

Marjory
5 months ago
Interesting perspectives! It seems like different candidates have different preferences based on their understanding of the operation efficiency.
upvoted 0 times
...
Quentin
5 months ago
I see your point, Lennie. But I personally prefer option D because it uses an AWS-defined cost allocation tag.
upvoted 0 times
...
Lennie
5 months ago
Option C allows the accounting team to activate the cost allocation tag in the member account, which could make tracking costs easier.
upvoted 0 times
...
Marjory
5 months ago
Why do you think option C is better, Lennie?
upvoted 0 times
...
Lennie
5 months ago
I disagree, I believe option C is the better choice.
upvoted 0 times
...
Marjory
6 months ago
I think the accounting team should go with option A.
upvoted 0 times
...
Helene
7 months ago
That's a good point. Option B does seem the most efficient, since we don't have to worry about setting up the tags in each member account. Plus, the AWS-defined tag should work seamlessly with Cost Explorer.
upvoted 0 times
...
Mattie
7 months ago
Okay, let's think this through. I'm leaning towards option B, where we activate the AWS-defined 'department' tag from the Organizations management account. That way, we can get the reports we need without having to manage the tag creation in each individual member account.
upvoted 0 times
...
Lamonica
7 months ago
Yeah, I agree. The key is to use the AWS Organizations feature and the cost allocation tags. We need to activate the 'department' tag and then create a cost report in Cost Explorer to get the desired results.
upvoted 0 times
Iesha
6 months ago
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.
upvoted 0 times
...
Julian
7 months ago
No, I believe option A is more efficient as it should be done from the management account to have a centralized view.
upvoted 0 times
...
Hollis
7 months ago
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.
upvoted 0 times
...
Lucina
7 months ago
I think option A is better because we can define our own tags for better customization.
upvoted 0 times
...
Jovita
7 months ago
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.
upvoted 0 times
...
Lindsey
7 months ago
Yeah, that sounds like the right approach. We can easily track spending by department with that.
upvoted 0 times
...
Felicia
7 months ago
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.
upvoted 0 times
...
...
Hershel
7 months ago
Hmm, this question seems pretty straightforward. We need to determine the most operationally efficient way to track Amazon EC2 costs by department across multiple AWS accounts.
upvoted 0 times
...

Save Cancel