A SysOps administrator must set up notifications for whenever combined billing exceeds a certain threshold for all AWS accounts within a company. The administrator has set up AWS Organizations and ena

Question

Options

• AIn the payer account: Enable billing alerts in the Billing and Cost Management console;
• BIn each account: Enable billing alerts in the Billing and Cost Management console; set up a
• CIn the payer account: Enable billing alerts in the Billing and Cost Management console; set up
• DIn the payer account: Enable billing alerts in the Billing and Cost Management console; set up

• A
  4% (1)
• B
  11% (3)
• C
  7% (2)
• D
  79% (22)

Explanation

Option D is correct because with AWS Organizations and Consolidated Billing, billing alerts for combined spending must be configured in the payer (management) account - specifically, you enable billing alerts in that account's Billing and Cost Management console, then create a CloudWatch alarm in the payer account targeting the consolidated billing metric, with an SNS topic to deliver the notification.

Why the distractors fail:

• A is incomplete - enabling billing alerts alone does nothing; you still need a CloudWatch alarm and SNS notification configured to actually trigger and send the alert.
• B is wrong on the account scope - enabling alerts and creating alarms in each individual account monitors per-account spend, not the combined total, which defeats the purpose of Consolidated Billing.
• C is likely wrong on a specific detail - commonly because it places the CloudWatch alarm in the wrong region (billing metrics only exist in us-east-1) or omits the SNS notification step.

Memory tip: Think "PAYer account PAYs attention" - because Consolidated Billing rolls all charges up to the payer account, that's the only place AWS exposes the combined billing CloudWatch metric. Individual accounts simply don't have visibility into the aggregate total.

No community discussion yet for this question.