An organization has hundreds of AWS accounts grouped into OUs for each engineering team. Each OU owns multiple accounts. The solutions architect must provide each OU with a breakdown of usage costs across the accounts that OU owns. Which solution meets this requirement?

The correct solution is to create a single AWS Cost and Usage Report (CUR) from the AWS Organizations management account. This is because CURs generated from the management account consolidate billing data for all member accounts within the organization, providing a comprehensive view of costs. Teams can then use Amazon QuickSight to visualize this data, filtering by OU or account to see their specific breakdown. Creating a CUR for each OU using RAM is incorrect because RAM is for resource sharing, not for generating consolidated billing reports. Creating a CUR in each member account is inefficient and doesn't provide a consolidated view, requiring teams to aggregate reports manually. Using AWS Systems Manager for CURs and OpsCenter dashboards is incorrect; Systems Manager is for operational management, not for generating or visualizing billing reports like CURs.