Amazon SAA-C03 Exam - Topic 12 Question 29 Discussion

Actual exam question for Amazon's SAA-C03 exam

Question #: 29
Topic #: 12

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

AFrom 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.

BFrom 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.

CFrom 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.

DFrom 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.

Show Suggested 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

by Lorean at Feb 11, 2024, 10:46 AM

Limited Time Offer

25%

Off

Get Premium SAA-C03 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Ozell

3 months ago

D sounds right, but I'm not sure about using member accounts for this.

upvoted 0 times

...

Oliva

3 months ago

I disagree, C is too complicated for what they need.

upvoted 0 times

...

Janae

4 months ago

Wait, can we really access all reports from the management account?

upvoted 0 times

...

Leota

4 months ago

I think B is better since it uses AWS-defined tags.

upvoted 0 times

...

Carissa

4 months ago

Option A seems like the best choice for tagging.

upvoted 0 times

...

Karl

4 months ago

I vaguely recall that AWS-defined tags might be easier to manage, but I’m not completely confident about which option is the most efficient for this case.

upvoted 0 times

...

Daron

4 months ago

I practiced a similar question where we had to filter costs by tags in Cost Explorer. I think grouping by tag name is definitely the right approach.

upvoted 0 times

...

Karol

4 months ago

I’m a bit unsure about whether to activate the tag from the management account or a member account. I feel like it should be the management account, but I could be wrong.

upvoted 0 times

...

Leatha

5 months ago

I remember we discussed the difference between user-defined and AWS-defined cost allocation tags. I think we need to use the right type for this scenario.

upvoted 0 times

...

Percy

5 months ago

The question mentions that the company already has a tagging policy that adds department tags, so I think the most efficient approach would be to use the existing AWS-defined tag rather than creating a new one.

upvoted 0 times

...

Erinn

5 months ago

Hmm, I'm a bit confused about whether we need to use a user-defined or AWS-defined tag. I'll have to review the details of the question again to make sure I understand the requirements.

upvoted 0 times

...

Cherilyn

5 months ago

This seems straightforward - I think the key is to activate the department tag at the Organizations management account level, and then create the cost report in Cost Explorer to group by that tag.

upvoted 0 times

...

Verdell

5 months ago

I like the idea of creating the cost report in Cost Explorer to filter by EC2 and group by the department tag. That should give the accounting team the visibility they need across all the AWS accounts.

upvoted 0 times

...

Alida

5 months ago

Hmm, I'll need to think this through carefully. The key is making sure the returned order sales type is set up correctly to reference the original sales order details. I'll need to review the Dynamics 365 documentation on that.

upvoted 0 times

...

Paris

5 months ago

I'm a bit confused about the Release Planning and Release Retrospective. Are those part of the Scrum framework or something else?

upvoted 0 times

...

Marjory

2 years ago

Interesting perspectives! It seems like different candidates have different preferences based on their understanding of the operation efficiency.

upvoted 0 times

...

Quentin

2 years 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

2 years 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

2 years ago

Why do you think option C is better, Lennie?

upvoted 0 times

...

Lennie

2 years ago

I disagree, I believe option C is the better choice.

upvoted 0 times

...

Marjory

2 years ago

I think the accounting team should go with option A.

upvoted 0 times

...

Helene

2 years 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

2 years 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

2 years 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

2 years 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

2 years 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

2 years 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

2 years ago

I think option A is better because we can define our own tags for better customization.

upvoted 0 times

...

Jovita

2 years 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

2 years ago

Yeah, that sounds like the right approach. We can easily track spending by department with that.

upvoted 0 times

...

Felicia

2 years 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

2 years 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

...