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 108 discussion

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

Question #: 108
Topic #: 1

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

A company has an automobile sales website that stores its listings in a database on Amazon RDS. When an automobile is sold, the listing needs to be removed from the website and the data must be sent to multiple target systems.
Which design should a solutions architect recommend?

A. Create an AWS Lambda function triggered when the database on Amazon RDS is updated to send the information to an Amazon Simple Queue Service (Amazon SQS) queue for the targets to consume.
B. Create an AWS Lambda function triggered when the database on Amazon RDS is updated to send the information to an Amazon Simple Queue Service (Amazon SQS) FIFO queue for the targets to consume.
C. Subscribe to an RDS event notification and send an Amazon Simple Queue Service (Amazon SQS) queue fanned out to multiple Amazon Simple Notification Service (Amazon SNS) topics. Use AWS Lambda functions to update the targets.
D. Subscribe to an RDS event notification and send an Amazon Simple Notification Service (Amazon SNS) topic fanned out to multiple Amazon Simple Queue Service (Amazon SQS) queues. Use AWS Lambda functions to update the targets.

Show Suggested Answer

Suggested Answer: A 🗳️

by Lilibell at Oct. 14, 2022, 12:18 a.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

romko

Highly Voted 2 years, 7 months ago

Selected Answer: A

Interesting point that Amazon RDS event notification doesn't support any notification when data inside DB is updated. https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_Events.overview.html So subscription to RDS events doesn't give any value for Fanout = SNS => SQS B is out because FIFO is not required here. A is left as correct answer

upvoted 91 times

Tsige

9 months ago

Option A suggests creating an AWS Lambda function triggered when the database on Amazon RDS is updated to send the information to an Amazon Simple Queue Service (Amazon SQS) queue for the targets to consume. While this approach can work, it has a few limitations compared to Option D: Scalability and Fan-out: Option A uses a single SQS queue, which means all target systems would need to poll the same queue. This can become a bottleneck if multiple systems need to process the data simultaneously. Option D, on the other hand, uses an SNS topic to fan out the event to multiple SQS queues, allowing each target system to have its own queue. This improves scalability and ensures that each target system can process the data independently. Option D offers a more scalable, decoupled, and flexible solution for handling the event notifications and distributing the data to multiple target systems.

upvoted 4 times

...

mknarula

1 year ago

But... SQS is a queue and is incapable of sending messages to "multiple target systems". SNS is pub/sub and topics can be subscribed by multiple apps to update when such an even occurs. Moreover Amazon RDS uses native capabilities of DBs like Postgres, MS SQL for change data capture. This can be used to send notifications to SNS

upvoted 5 times

...

nauman001

2 years, 3 months ago

Listing the Amazon RDS event notification categories. https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_Events.ListingCategories.html:

upvoted 3 times

...

Jiang_aws1

2 years, 7 months ago

D is connect RDS event notification by RDS stream or advance audit DML so it is possible

upvoted 2 times

Jiang_aws1

2 years, 7 months ago

The key is "Fanned out" due to "Multiple target systems" need to update

upvoted 4 times

...

JayBee65

2 years, 7 months ago

Please provide reference for this claim: " event notification by RDS stream or advance audit DML"

upvoted 4 times

...

Load full discussion...

...

ksolovyov

Highly Voted 2 years, 6 months ago

Selected Answer: A

RDS events only provide operational events such as DB instance events, DB parameter group events, DB security group events, and DB snapshot events. What we need in the scenario is to capture data-modifying events (INSERT, DELETE, UPDATE) which can be achieved thru native functions or stored procedures.

upvoted 15 times

BlueVolcano1

2 years, 5 months ago

I agree with it requiring a native function or stored procedure, but can they in turn invoke a Lambda function? I have only seen this being possible with Aurora, but not RDS - and I'm not able to find anything googling for it either. I guess it has to be possible, since there's no other option that fits either. https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html

upvoted 1 times

BlueVolcano1

2 years, 5 months ago

To add to that though, A also states to only use SQS (no SNS to SQS fan-out), which doesn't seem right as the message needs to go to multiple targets?

upvoted 13 times

...

a0c03ac

Most Recent 1 week, 5 days ago

Selected Answer: D

D. Subscribe to an RDS event notification and send an Amazon Simple Notification Service (Amazon SNS) topic fanned out to multiple Amazon Simple Queue Service (Amazon SQS) queues. Use AWS Lambda functions to update the targets. ✅ Explanation: This solution provides a scalable, decoupled, and event-driven architecture that meets the requirement of sending data to multiple target systems when a listing is sold: RDS event notifications can be configured to publish to an SNS topic. SNS supports fan-out to multiple SQS queues, allowing each target system to receive the event independently. Lambda functions can be triggered from each SQS queue to process and forward the data to the respective target systems. This design ensures: Loose coupling between components. Scalability and fault tolerance. Asynchronous processing for better performance and reliability

upvoted 1 times

...

Charlesvg

1 month ago

Selected Answer: A

i really hesitated between A & D. But it is really not posssible for RDS event notifications to send messages about a delete row. An option A only says to use a SQS, event if multiple targets can not consume from one SQS message, you can set up an SNS with the SQS queue to implement the fan out

upvoted 1 times

...

kaleido

1 month ago

Selected Answer: D

I prefer answer D because "data needs to be sent to targets". SNS is more efficient.

upvoted 1 times

...

bora4motion

1 month, 3 weeks ago

Selected Answer: D

going with d as you need sns to fan out to multiple systems

upvoted 1 times

...

Kp002

2 months, 1 week ago

Selected Answer: D

Why not A or B: Lambda cannot be directly triggered by Amazon RDS data changes unless you’re using Amazon Aurora with the advanced Aurora MySQL features, which support Aurora database triggers to invoke Lambda. If it’s standard RDS, you’d need to build this logic into the application itself or poll the database — not ideal. • FIFO queues (Option B) are only needed if message order is critical, which isn’t indicated in the question.

upvoted 1 times

...

c6ee0dd

2 months, 3 weeks ago

Selected Answer: D

D : event publishes message to a topic making it available to multiple consumers A : Its a single SQS queue which can lead to problems when multiple consumers are consuming the data concurrently

upvoted 1 times

...

TEC65

3 months ago

Selected Answer: D

D - RDS cannot send notification to lambda

upvoted 1 times

...

network_enthusiast

3 months ago

Selected Answer: B

B is the correct answer

upvoted 1 times

...

CloudExpert01

3 months, 2 weeks ago

Selected Answer: A

RDS event notifications won't capture row-level changes directly, and adding complexity with SQS and SNS may be unnecessary.

upvoted 1 times

...

ChhatwaniB

4 months, 2 weeks ago

Selected Answer: D

SQS won’t work for multiple targets. Once a message is consumed by a target it will be removed from the queue

upvoted 3 times

...

Saloniip

4 months, 4 weeks ago

Selected Answer: D

We need to send same msg to multiple targets that a data bas been removed. Not different msgs to different targets. so option d is much better solution.

upvoted 1 times

...

zdi561

5 months, 2 weeks ago

Selected Answer: D

A is not right because one SQS consumed by multiple targets with different process is not possible. Ideally it should be sent to multiple SQS. D is working ok.

upvoted 4 times

...

CristiaNNN

6 months ago

Selected Answer: D

Option D: Subscribe to an RDS event notification and send an Amazon Simple Notification Service (Amazon SNS) topic fanned out to multiple Amazon Simple Queue Service (Amazon SQS) queues. Use AWS Lambda functions to update the targets. Correct Choice: This approach leverages RDS event notifications and SNS for fanning out updates to multiple SQS queues. Each target can then independently process updates using Lambda functions, making it scalable and modular.

upvoted 4 times

...

Rcosmos

6 months ago

Selected Answer: D

Conclusão: A opção D (SNS para distribuição e SQS para entrega confiável) é a solução mais adequada, escalável e resiliente para lidar com a necessidade de envio de dados a vários sistemas de destino após a venda de um automóvel.

upvoted 1 times

...

4729e6c

6 months, 1 week ago

Selected Answer: D

Option D is the best choice because it uses RDS event notifications to trigger an SNS topic that fans out to multiple SQS queues, enabling each target system to process events independently and reliably. This approach ensures scalability, decoupling, and durable message storage. Option A is not ideal because RDS does not natively trigger Lambda functions; an external polling mechanism would be required, increasing complexity and operational overhead.

upvoted 2 times

...

Load full discussion...