AWS Certified Solutions Architect – Professional — Question 903
A company is building a hybrid solution between its existing on-premises systems and a new backend in AWS. The company has a management application to monitor the state of its current IT infrastructure and automate responses to issues. The company wants to incorporate the status of its consumed AWS services into the application. The application uses an HTTPS endpoint to receive updates.
Which approach meets these requirements with the LEAST amount of operational overhead?
Answer options
- A. Configure AWS Systems Manager OpsCenter to ingest operational events from the on-premises systems. Retire the on-premises management application and adopt OpsCenter as the hub.
- B. Configure Amazon EventBridge (Amazon CloudWatch Events) to detect and react to changes for AWS Health events from the AWS Personal Health Dashboard. Configure the EventBridge (CloudWateh Events) event to publish a message to an Amazon Simple Notification Service (Amazon SNS) topic and subscribe the topic to the HTTPS endpoint of the management application.
- C. Modify the on-premises management application to call the AWS Health API to poll for status events of AWS services.
- D. Configure Amazon EventBridge (Amazon CloudWatch Events) to detect and react to changes for AWS Health events from the AWS Service Health Dashboard. Configure the EventBridge (CloudWateh Events) event to publish a message to an Amazon Simple Notification Service (Amazon SNS) topic and subscribe the topic to an HTTPS endpoint for the management application with a topic filter corresponding to the services being used.
Correct answer: B
Explanation
Option B is correct because the AWS Personal Health Dashboard specifically tracks events and status changes for the AWS services actually consumed by the account, and routing these via Amazon EventBridge and Amazon SNS provides a serverless, push-based integration to the HTTPS endpoint with minimal overhead. Option A is incorrect because retiring an active on-premises application involves high operational overhead. Option C requires custom polling code, which is less efficient than event-driven push architectures. Option D is incorrect because the Service Health Dashboard shows the status of all AWS services globally, requiring unnecessary filtering compared to the Personal Health Dashboard.