An enterprise manages many AWS accounts under AWS Organizations and wants every member account's usage rolled up so the combined volume can qualify for tiered volume discounts on certain services. Which capability of AWS Organizations delivers this pooled pricing benefit?
- AConsolidated billing, which aggregates usage across all member accounts so combined volume can reach lower tiered pricing. Correct
- BCost allocation tags, which attach labels to individual resources so charges can be grouped by department or project on the bill.
- CService control policies, which set guardrails on which AWS actions and services member accounts are permitted to use.
- DAWS Cost Explorer, which charts each account's historical spend through interactive graphs for reviewing past consumption.
Why A is correct: Consolidated billing in AWS Organizations combines the usage of all member accounts into one payer account, and that pooled volume can reach the lower tiers of tiered pricing, which is the benefit the enterprise wants.
Why B is wrong: Cost allocation tags only break down and categorise existing charges by label and do not pool usage across accounts to earn volume discounts, so they do not provide the aggregated pricing benefit described.
Why C is wrong: Service control policies govern permissions across accounts and have no role in aggregating usage for pricing, so although they belong to Organizations they do not deliver volume discounts.
Why D is wrong: Cost Explorer reports and visualises spend that has already happened but does not combine account usage to qualify for tiered volume pricing, so it does not provide the pooled discount.