Q82 — AWS SAA-C03 Ch.17

Question 82 of 89 | ← Chapter 17

Q1382. A financial company processes transactions from multiple payment providers by using its AWS infrastructure. The company needs to implement a system that sends high-value transactions to a fraud detection service. The system must route failed transactions to a retry queue. The system must also copy international transactions to a compliance monitoring system and archive all transactions for audit purposes.Which solution will meet these requirements with the LEAST operational overhead?

Correct Answer: C. Use Amazon EventBridge Pipes to filter the events and route the events to different target systems.

Explanation

Let's analyze each option to determine which one meets the requirements with the least operational overhead:Option AAmazon EventBridge input transformers: Input transformers in Amazon EventBridge are mainly used to modify the structure of an event before it is processed further. While they can change the event format, they are not well - suited for the complex routing and filtering requirements described in the scenario. Basic filtering on event types is not sufficient to handle the different routing rules for high - value transactions, failed transactions, international transactions, and archiving. This option would require additional components and more complex logic to achieve the desired functionality, resulting in higher operational overhead.Option BSeparate Amazon EventBridge event buses for each payment provider: Creating separate event buses for each payment provider adds significant complexity to the system. It would require managing multiple event buses, each with its own set of rules and configurations. This approach would increase the operational overhead as it becomes more difficult to monitor, maintain, and update the system. Additionally, it may not be the most efficient way to handle the common routing and filtering requirements across different payment providers.Option CAmazon EventBridge Pipes: Amazon EventBridge Pipes is a feature that allows you to filter events and route them to different target systems in a simple and efficient way. You can define filters based on event attributes, and then specify the target for each filtered set of events. For example, you can filter for high - value transactions and route them to the fraud detection service, filter for failed transactions and route them to the retry queue, filter for international transactions and route them to the compliance monitoring system, and set up a separate rule to archive all transactions. This approach provides a centralized and straightforward way to handle the different routing requirements with minimal configuration and operational overhead.Option DAmazon EventBridge event bus with multiple rules: While it is possible to create an event bus with multiple rules and use event pattern matching for the provided conditions, managing multiple rules on a single event bus can become complex as the number of requirements increases. Each rule needs to be carefully configured to avoid conflicts and ensure that events are routed correctly. As the system evolves and new requirements are added, it can be challenging to maintain and update the rules without introducing errors. This approach may result in higher operational overhead compared to using Amazon EventBridge Pipes. Based on the above analysis, the solution that will meet the requirements with the least operational overhead is to use Amazon EventBridge Pipes to filter the events and route the events to different target systems. So the answer is C.