A serverless application is being developed using AWS Lambda and Amazon RDS as a database. It is expected that AWS Lambda functions will open a large number of simultaneous connections to the database server. The team would like to reduce the memory and CPU overhead for connection management on the database. What is the optimal solution to this requirement?

Answer options:

A.Upgrade the database to a larger database class.
B.Create an RDS Proxy.
C.Create an AWS PrivateLink.
D.Create an AWS ElastiCache cluster.

Answer: B
Option A is incorrect because this is not the optimal solution. Increasing the database class can make more database resources available for connection management, but it does not reduce the memory and CPU overhead associated with connection management.
Option B is CORRECT because RDS proxy is a service that can be used to pool simultaneous connections from serverless applications and alleviate the connection management from the RDS database instance.
Option C is incorrect because AWS PrivateLink is a service that provides private VPC network integration for cloud-based services.
Option D is incorrect because the requirement is to reduce the overhead associated with connections to the RDS database. Implementing ElastiCache would require a code change. Also, the question does not specify that caching is appropriate or possible in this use case. This is not an applicable option in this scenario.
Reference:
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/rds-proxy.html