SOA-C02 · Question #562
A company has internal hybrid applications that have resources in the AWS Cloud and on premises. Users report that the applications sometimes are not available. The company has configured an Amazon…
The correct answer is C. Create an AWS Lambda function. Configure the CloudWatch alarm to directly invoke the Lambda. Option C is correct because CloudWatch alarms support direct Lambda invocation as an alarm action, and Lambda can execute custom code to call the internal ticketing tool's API - making it the only option that actually creates a ticket in a proprietary system without additional…
Question
A company has internal hybrid applications that have resources in the AWS Cloud and on premises. Users report that the applications sometimes are not available. The company has configured an Amazon CloudWatch alarm to monitor the tunnel status of its AWS Site-to-Site VPN connection. A SysOps administrator must implement a solution that creates a high-priority ticket in an internal ticketing tool when the VPN tunnel is down. Which solution will meet this requirement?
Options
- ACreate an Amazon Simple Notification Service (Amazon SNS) topic for the CloudWatch alarm.
- BCreate an Amazon Simple Queue Service (Amazon SQS) queue as the target for the
- CCreate an AWS Lambda function. Configure the CloudWatch alarm to directly invoke the Lambda
- DCreate an Amazon EventBridge rule that monitors the VPN tunnel directly. Configure the ticketing
How the community answered
(33 responses)- A3% (1)
- B9% (3)
- C73% (24)
- D15% (5)
Explanation
Option C is correct because CloudWatch alarms support direct Lambda invocation as an alarm action, and Lambda can execute custom code to call the internal ticketing tool's API - making it the only option that actually creates a ticket in a proprietary system without additional components.
Option A (SNS) is wrong because SNS only sends notifications (email, SMS, HTTP webhooks) - it has no built-in mechanism to create tickets in a custom internal tool. SNS alone stops short of the required action.
Option B (SQS) is wrong on two levels: CloudWatch alarms cannot directly target SQS queues (they natively support SNS and Lambda), and even if they could, SQS only queues messages - it doesn't execute any logic to create a ticket.
Option D (EventBridge) is wrong because the VPN tunnel is already being monitored by the existing CloudWatch alarm; adding a redundant EventBridge rule monitoring the same resource is unnecessary complexity, and the option doesn't specify how a ticket actually gets created.
Memory tip: Whenever an exam question involves integrating an AWS event with a custom internal system or proprietary tool, Lambda is almost always the answer - it's the universal adapter that bridges AWS events to any external API or business logic.
Topics
Community Discussion
No community discussion yet for this question.