Exam AWS Certified Solutions Architect - Associate SAA-C03 All Questions

View all questions & answers for the AWS Certified Solutions Architect - Associate SAA-C03 exam

Exam AWS Certified Solutions Architect - Associate SAA-C03 topic 1 question 739 discussion

Exam question from Amazon's AWS Certified Solutions Architect - Associate SAA-C03

Question #: 739
Topic #: 1

[All AWS Certified Solutions Architect - Associate SAA-C03 Questions]

A company is building a new application that uses serverless architecture. The architecture will consist of an Amazon API Gateway REST API and AWS Lambda functions to manage incoming requests.

The company wants to add a service that can send messages received from the API Gateway REST API to multiple target Lambda functions for processing. The service must offer message filtering that gives the target Lambda functions the ability to receive only the messages the functions need.

Which solution will meet these requirements with the LEAST operational overhead?

A. Send the requests from the API Gateway REST API to an Amazon Simple Notification Service (Amazon SNS) topic. Subscribe Amazon Simple Queue Service (Amazon SQS) queues to the SNS topic. Configure the target Lambda functions to poll the different SQS queues.
B. Send the requests from the API Gateway REST API to Amazon EventBridge. Configure EventBridge to invoke the target Lambda functions.
C. Send the requests from the API Gateway REST API to Amazon Managed Streaming for Apache Kafka (Amazon MSK). Configure Amazon MSK to publish the messages to the target Lambda functions.
D. Send the requests from the API Gateway REST API to multiple Amazon Simple Queue Service (Amazon SQS) queues. Configure the target Lambda functions to poll the different SQS queues.

Show Suggested Answer

Suggested Answer: A 🗳️

by Andy_09 at Feb. 5, 2024, 8:53 p.m.

Disclaimers:

- ExamTopics website is not related to, affiliated with, endorsed or authorized by Amazon.
- Trademarks, certification & product names are used for reference only and belong to Amazon.

Comments

Submit Cancel

Kezuko

Highly Voted 1 year, 3 months ago

Selected Answer: A

"message filtering" = SNS

upvoted 15 times

...

AMEJack

Highly Voted 7 months, 1 week ago

Selected Answer: B

The question is asking about one service. If you choose A, you need to build 3 services one per each SNS topic. Also, creating one Event Bridge with rules to forward to the target Lambda is easier than creating 3 topics with 3 SQS queues. The answer is definetly B.

upvoted 5 times

...

GOTJ

Most Recent 3 months, 3 weeks ago

Selected Answer: A

I'm discarding option "B" for the following reasons 1. You can't send "requests" (messages) to EventBridge, at least not directly as option suggests. There must be an event involved in the process 2. Lack of configuration regarding to discrete Lambda invocations Option "A", by its side, also lacks of the necessary configuration for discrete lambda invocation (use of subscriptor filter), but in my opinion is closer to what company needs: https://docs.aws.amazon.com/sns/latest/dg/sns-message-filtering.html So my vote goes to "A".

upvoted 1 times

...

Chen77

4 months, 2 weeks ago

Selected Answer: A

SNS supports fan-out: API Gateway sends messages to an SNS topic, which then forwards to multiple SQS queues. Message filtering with SNS: SNS allows each SQS queue to receive only the relevant messages, reducing unnecessary processing. SQS queues decouple workloads: Lambda functions pull messages only when ready, ensuring efficient and scalable processing.

upvoted 2 times

...

zdi561

4 months, 3 weeks ago

Selected Answer: B

A and B both can do message filtering but A only filters message by attributes and B can do filtering by message content too, and B is simpler

upvoted 1 times

...

hilker1983

6 months ago

Selected Answer: B

LEAST operational overhead -> B better than A

upvoted 1 times

...

Denise123

6 months, 1 week ago

Selected Answer: B

The answer is B. On the other hand, the solution involving Amazon SNS, Amazon SQS, and Lambda polling (Option A) introduces more moving parts and operational overhead: It requires managing and configuring multiple services (SNS, SQS, and Lambda). Lambda functions need to continuously poll SQS queues, which can be less efficient and introduce additional latency. Scaling and managing SQS queues and their associated resources (e.g., dead-letter queues) add operational complexity. While the SNS-SQS-Lambda solution is still valid and widely used, the EventBridge-Lambda integration offers a more streamlined and serverless-native approach, aligning better with the company's serverless architecture goals and minimizing operational overhead.

upvoted 1 times

...

LeonSauveterre

6 months, 2 weeks ago

Selected Answer: B

EventBridge applies filtering rules and invokes the appropriate Lambda functions directly, just like SNS + SQS. Option B is definitely "the LEAST operational overhead". While there’s a 5-target-per-rule limit, you can work around it by creating additional rules. Each rule can directly invoke Lambda functions without the need for SQS queues or polling. Let's not stick to option A just because it's the textbook exam-standard SNS+SQS combination. There are other options that will help you achieve the goal under different circumstances.

upvoted 2 times

...

JA2018

7 months ago

Selected Answer: B

agreed with AMEJack.... based on the stem, B required the LEAST operational overhead

upvoted 2 times

JA2018

7 months ago

From Google AI Search: The correct answer is B. Send the requests from the API Gateway REST API to Amazon EventBridge. Configure EventBridge to invoke the target Lambda functions.

upvoted 1 times

JA2018

7 months ago

Explanation: Least operational overhead: EventBridge is designed specifically for event routing and filtering, making it the most efficient option for managing which Lambda functions receive messages based on specific criteria, minimizing operational overhead compared to the other choices. Message filtering: EventBridge allows you to define detailed rules with attributes and conditions to filter messages and send them only to the relevant Lambda functions, fulfilling the requirement for message filtering. Scalability: Both EventBridge and SNS can handle large volumes of messages, but EventBridge offers better management and control over message routing, especially when dealing with complex event patterns.

upvoted 1 times

JA2018

7 months ago

Why the other options are less ideal: A. SNS with SQS: While SNS can be used for fan-out messaging, adding SQS queues introduces extra complexity and potential bottlenecks in managing multiple queues and subscriptions. C. Amazon MSK: While Kafka is a powerful messaging system, it might be overkill for this scenario due to its complexity and overhead for managing a dedicated Kafka cluster, especially if the message volume is not very high. D. Multiple SQS queues: This option would require additional logic to decide which SQS queue to send messages to based on filtering criteria, adding complexity to the architecture. Key takeaway: When looking for a solution with the least operational overhead for message routing and filtering between an API Gateway and multiple Lambda functions, Amazon EventBridge is the most suitable choice.

upvoted 1 times

...

1166ae3

11 months, 3 weeks ago

Selected Answer: B

LEAST operational overhead -> B better than A

upvoted 5 times

...

Scheldon

1 year ago

Selected Answer: A

AnswerA Hence EventBridge is a solution to handle events and we need to handle messages I believe option A is the best solution here

upvoted 3 times

...

3bdf1cc

1 year ago

https://aws.amazon.com/blogs/compute/capturing-client-events-using-amazon-api-gateway-and-amazon-eventbridge/

upvoted 2 times

...

BBR01

1 year, 2 months ago

Selected Answer: A

The main issue with B is that with Eventbrige, you can only define up to five targets for each rule. https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-targets.html

upvoted 4 times

...

sandordini

1 year, 2 months ago

B: EventBridge reacts to events, not requests or messages. C: I don't think so, but I don't know MSK well enough. D: You can add a filter so that your function only processes Amazon SQS messages containing certain data parameters. but it will still receive, so I assume it's not what the question asks for. Only A remains... But it still misses steps plus we are looking for the Least ops overhead.. I am confused..

upvoted 2 times

...

03beafc

1 year, 2 months ago

Selected Answer: B

Eventbridge + lambda is two services, sns + sqs + lambda is 3. Both can filter, but the config involved in eventbridge > lambda is easier

upvoted 3 times

MatAlves

9 months, 2 weeks ago

SNS provides built-in message filtering. SNS -> SQS -> Lambda = very common Fanout Scenario

upvoted 2 times

...

AlvinC2024

1 year, 3 months ago

Selected Answer: D

Upload and store content in Amazon S3 in the Region that is closest to the user. Use multiple distributions of Amazon CloudFront. This approach ensures that uploads are quick, taking advantage of the geographical proximity of S3, while still leveraging CloudFront for efficient content delivery outside the local region if necessary. The local nature of the content consumption aligns with storing content in the closest region to the user, addressing the requirement that 90% of the content is consumed within the AWS Region where it is uploaded.

upvoted 1 times

...

TruthWS

1 year, 3 months ago

Option B - Eventbridge allow routing event from source to dest or multi dest you want

upvoted 2 times

...

Load full discussion...