Exam AWS Certified Solutions Architect - Professional SAP-C02 topic 1 question 450 discussion

Correct: D The option talks about LEAST operational complexity not LEAST operational overhead. Option B is quite complex

LEAST operational complexity, considering the report already is available in the bucket: B. After the initial setup, the process is fully automatic, which means the operational complexity involving separate actions by account managers isn't needed.

Option D: Individual Cost and Usage Reports per account Each account sets up its own Cost and Usage Report Data is automatically isolated by account Direct integration with Athena Simple one-time setup per account No custom code or complex sharing mechanisms The answer is D. Option D has the least operational complexity because: It uses native AWS functionality without custom code Data isolation is automatic (each account only sees its own data) Once set up, it runs automatically with no maintenance Each account can directly query their data with Athena Scales easily as new accounts are added

Multiple accounts since multiple business units has their own account. So, it is complex to do it in each member account rather than lambda solution in option B.

It is easy to setup CUR. B works but unnecessarily complicated.

After the initial setup of the S3 event, Lambda function, and bucket policy modifications, the process becomes fully automatic, minimizing the ongoing operational complexity involving separate actions by account managers.

A Lambda-based solution for sharing Cost and Usage Reports, while powerful, introduces significant operational complexity due to the need to manage and maintain multiple AWS services and components. This includes Lambda functions, S3 events, S3 bucket policy, etc. The solution requires ongoing code maintenance, careful configuration management, and monitoring of multiple services, making it more complex than simpler alternatives like setting up individual CURs in member accounts. While it offers flexibility and automation capabilities, the added complexity might outweigh the benefits for basic cost-sharing requirements across AWS accounts.

Configures an S3 event that triggers a Lambda function every time a new file arrives in the central Cost and Usage Report bucket. The Lambda function extracts each member account's data from the central report. Stores the extracted data under separate prefixes for each member account in Amazon S3. Modifies the S3 bucket policy to grant access to each member account's prefix. By automating this process, Option B minimizes operational complexity while ensuring that each member account has access to its own cost and usage data without requiring manual setup or maintenance.

Already its mentioned the consolidated billing report is available in centralized bucket. Here if option D has to be chosen, then the Cost and Usage report have to be configured in individual accounts seperately again at individual accounts, which could add operational complexity, hence Option B seems to be right.

In addition to what user Dgix commented, the fact that the S3 bucket must be in the account that creates the CUR does not make option B unfeasible. On the contrary, this option already assumes that the initial configuration of the bucket and the processing of the CUR report happen in the management account. Option B remains the recommended solution because it: Automates the data segmentation process. Ensures compliance with documentation by keeping the S3 bucket in the management account. Simplifies access control by using bucket policies to ensure that each account sees only its own data. Meets the requirement of lower operational complexity by centralizing the processing of the CUR. Therefore, even with the restriction that the S3 bucket must be in the management account, option B remains the best choice to meet the business requirements with the least operational effort.

B sounds like quite the adventure.

B would be very complex to parse the incoming files and separate by prefix. Then managing all the individual prefix shares. For that reason D seems like a better choice. Also the question mentions having the right permissions setup so they can configure their own CUR.

Answer: Option D First Reason: The Cost and Usage Report (CUR) cannot be set up for cross-account delivery. According to the AWS documentation, “The account that creates the Cost and Usage Report must also own the Amazon S3 bucket that AWS sends the reports to.” This means each account must set up its own S3 bucket to receive its respective CUR. https://docs.aws.amazon.com/cur/latest/userguide/cur-consolidated-billing.html Second Reason: The question asks for the solution with the least operational complexity. Option D simplifies the process by allowing each account to independently manage its own CUR setup without requiring complex configurations or custom Lambda functions.

After some investigation, I found A could be a suitable choice, however it lacks a few details By using AWS RAM, you can share the S3 bucket (or specific prefixes within the bucket) containing the Cost and Usage Report with the member accounts. Each member account can set up Athena queries to access and analyze their own cost and utilization data from the shared S3 bucket. This approach ensures that each business unit can view its own data without accessing other units' data. B: too complicated C: Cost Explorer doesn't provide the raw cost and usage data that might be needed for detailed analysis with Athena. D: multiple Cost and Usage Reports, one for each account => out

The question asks for LEAST operational complexity But it seems that only the most complex option can solve the problem

Why B? The question talk about LEAST operations. D for me

The most straightforward option