Exam AWS Certified Solutions Architect - Professional SAP-C02 topic 1 question 212 discussion

A tricky question :) The RDS proxy sounds sexy, but it cannot be used because the database is on premise. The creative solution here is SQS. Such questions are partly about your understanding of the services and some solutions are good, even if they sound a bit strange at first :)

"The company wants to protect the database from crashes" means keep the existing one and do something that can prevent crashes, not to migrate it to another in anywhere. -> B, C out Choice between SQS and SNS is easy.

Amazon SQS decouples ingestion from processing, allowing for asynchronous data handling. By placing data into an SQS queue, you can buffer incoming requests regardless of spikes in Lambda invocation. You then create a separate Lambda consumer that reads messages from the queue and writes them to the database at a controlled rate. Using reserved concurrency, you can limit the number of simultaneous Lambda executions to a number lower than the database's connection limit—protecting the database.

C, Keyword: "supports a limited number of concurrent connections" Creating an Amazon RDS Proxy DB instance and attaching it to the Amazon RDS DB instance can help manage the database connections efficiently and prevent the database from being overwhelmed by too many connections. The RDS Proxy can pool and share connections to the database, which can reduce the number of connections that each Lambda function invocation needs to establish. This can help to prevent the database from crashing when the number of Lambda function invocations is high. Reconfiguring the Lambda function to write to the RDS Proxy DB instance instead of directly to the database can further help to protect the database from crashes. This is because the RDS Proxy can handle the connections to the database, reducing the load on the database and helping to ensure its stability.

You can use SQS to write data, however the phrase "reserved concurrency" is incorrect, Lambda has "provisioned concurrency"

Option A: AWS Tutorial on How To https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/rds-lambda-tutorial.html

Option A

Correct A.

Its an A

correct is A as database is on-premises

MODERATOR Please delete my previous comment. I commented about RDS proxy which is totally WRONG. Answer is A

Will go with C , don't think the question says they need to keep the on-prem db

apparently, we need to make the lambda "not to rush that much" and keep the connection within the limit of the on-pre DB. So if we want not to lose data while waiting we implement SQS before the lambda so it keeps the requests in the queue.

C should be logical answer, that's what RDS proxy does. But, they want to keep the existing SQL on-prem and not migrate to RDS. So C and B are out. We need to throttle the connections. SNS is not designed for this. So, it's SQS (A).

Correct answer is A

c-c-c-c-c-c By creating an Amazon RDS Proxy DB instance and attaching it to the existing Amazon RDS DB instance, you can protect the database from crashes caused by a high number of Lambda function invocations. The RDS Proxy acts as an intermediary between the Lambda function and the database, managing the connections and pooling them efficiently

A is the answer. RDS proxy is meant to help with connection pooling. Amazon RDS Proxy instance maintains a pool of established connections to your RDS database instances, reducing the stress on database compute and memory resources that typically occurs when new connections are established. RDS Proxy also shares infrequently used database connections, so that fewer connections access the RDS database. This connection pooling enables your database to efficiently support a large number and frequency of application connections so that your application can scale without compromising performance.