An organization uses AWS Organizations with separate accounts for security and for logging. The SysOps administrator must implement a centralized alerting approach so that when any account’s resource metric crosses a defined threshold, an alert is generated. Which implementation satisfies this requirement?

CloudFormation StackSets allow you to deploy a common CloudFormation template across multiple accounts and Regions from a central administrator account. This is ideal for establishing consistent monitoring and alerting. By deploying CloudWatch alarms in each account that publish to a centralized SNS topic in the logging account, you achieve centralized alerting without duplicating the SNS topic in every account. Granting publish permissions ensures cross-account communication. Deploying individual stacks in each account is less efficient for managing numerous accounts. Scheduling Lambda functions in every account adds unnecessary operational overhead and cost compared to native CloudWatch alarms. Using a CloudFormation change set at the organization level is not a mechanism for deploying resources across accounts; change sets apply to existing stacks. SES is for email sending, not for receiving alerts from CloudWatch alarms.