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

Provisioned Concurrency - makes sure Lambda functions could handle traffic bursts RDS proxy endpoint - intelligently manages connections to a relational database ( Amazon RDS here) So, the answer - B

If cost is a primary concern, Reserved Concurrency could be a more economical choice. Provisioned Concurrency is designed to provide more control over your Lambda function’s performance and scalability. Answer is B.

Option A is likely the best choice. It involves a straightforward adjustment to how database connections are handled without introducing new services or significantly altering existing infrastructure. While it still requires some code changes, these are limited compared to Options B, C, and D. In summary, while using AWS Secrets Manager (as in Options B and D) provides security benefits, it also introduces more complexity and significant changes to your existing setup. Therefore, if minimizing changes is your primary goal, Option A (updating the Lambda function code for connection handling) is the most suitable choice.

B is correct This solution requires minimal changes to the application: • Creating an RDS Proxy endpoint and updating the Lambda functions to use it is a relatively minor modification. • Store database secrets in AWS Secrets Manager adds some complexity, but it is still a manageable change. • Increasing provisioned concurrency for the Lambda functions can help handle bursts in traffic without requiring significant changes to the application.

By leveraging RDS Proxy, AWS Secrets Manager, and increasing provisioned concurrency, Option B provides a scalable and secure solution with minimal changes to the application code, making it the most appropriate choice for meeting the requirements. The other options have drawbacks or require more significant changes to the application: Option A: While it suggests increasing provisioned concurrency, opening database connections outside the function handler may not be a best practice and could lead to connection leaks or other issues. Option C: Increasing the max_connections parameter on the RDS instance may not be sufficient to handle bursts in traffic and could potentially impact performance. Additionally, it requires scheduling a reboot, which could cause downtime. Option D: While it correctly suggests using RDS Proxy, AWS Secrets Manager, and increasing reserved concurrency, it does not mention provisioned concurrency, which is more suitable for handling bursts in traffic.

Connection Pooling: RDS Proxy helps manage database connections efficiently by pooling and reusing connections. Reduced Latency: By reducing the overhead of establishing new connections for each Lambda invocation, RDS Proxy improves the overall performance, minimizing the latency experienced by your application during traffic bursts. Provisioned Concurrency: Increasing the provisioned concurrency for the Lambda functions ensures they are always ready to handle spikes in traffic, reducing cold start times. Seamless Integration: The integration with AWS Lambda and Secrets Manager ensures that the database credentials are securely managed. IAM Permissions: The use of AWS Identity and Access Management (IAM) permissions to control access to the proxy ensures security and compliance, making this solution secure and scalable.

B is correct for least operation(not cost effectively) in question

A is right answer. D is wrong because the provisioned Concurrency is the term to keep pre-allocated warm instances of lambda not reserved concurrency. B missing auto scaling the db.

Answer B

Option D with "reserved concurrency" can be more cost-effective and flexible for handling sudden traffic bursts, as it ensures a minimum number of instances without the potential over-provisioning of provisioned concurrency.

Sorry, meant A