SAP-C02 Question 210

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose A1

  SQS buffers bursty writes and a reserved concurrency cap on the SQS‑triggered Lambda guarantees you never exceed the on‑prem DB’s connection limit. C (RDS Proxy) doesn’t apply to on‑prem databases, B is an unnecessary migration, and D mixes SNS with provisioned (not limited) concurrency, which doesn’t protect the DB from spikes.

• Chose A1

  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.

• Chose C1

  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.