Which solution will meet these requirements?
Configure the company’s email server to forward notification email messages that are sent to the AWS account root user email address to all users in the organization.
Configure all AWS account root user email addresses as distribution lists that go to a few administrators who can respond to alerts. Configure AWS account alternate contacts in the AWS Organizations console or programmatically.
Configure all AWS account root user email messages to be sent to one administrator who is responsible for monitoring alerts and forwarding those alerts to the appropriate groups.
Configure all existing AWS accounts and all newly created accounts to use the same root user email address. Configure AWS account alternate contacts in the AWS Organizations console or programmatically.
Explanations:
Forwarding emails from the root user to all users in the organization could lead to information overload and security concerns. Notifications are meant for account administrators, and this approach doesn’t ensure that only relevant users receive them.
Using distribution lists for root user emails allows notifications to be sent to designated administrators who can manage alerts effectively. Additionally, configuring alternate contacts ensures that critical notifications are routed to the right individuals, aligning with the requirement to limit notifications to account administrators.
Sending all root user emails to a single administrator creates a single point of failure. If that administrator is unavailable, notifications may be missed. This does not align with the requirement to ensure all future notifications are seen by relevant administrators.
Using the same root user email for all accounts reduces accountability and could lead to confusion regarding ownership and management of notifications. It also doesn’t utilize alternate contacts effectively to ensure that only administrators receive alerts.