A utility enterprise is modernizing its legacy smart meter telemetry ingestion backend to a serverless architecture on AWS. The solution must ingest bursty, real-time meter readings via an Amazon API Gateway endpoint and process them using an AWS Lambda function. The API Gateway endpoint must only be accessible privately from the enterprise's on-premises network via an AWS Direct Connect connection. The processed data is then stored in an Amazon RDS for PostgreSQL database in a private subnet. The database requires highly resilient connection management to prevent connection exhaustion during peak traffic times. Additionally, the ingestion workload must be configured so that it does not exhaust the regional execution pool and throttle critical downstream customer billing and payment Lambda functions. Which combination of actions should a solutions architect recommend to meet these requirements? (Select TWO.)
- Deploy a private API Gateway endpoint using an interface VPC endpoint, and configure an Amazon RDS Proxy between the telemetry processing Lambda function and the RDS for PostgreSQL database.Answer
- Configure reserved concurrency on the telemetry processing Lambda function to limit its maximum concurrent executions, preventing it from consuming the entire regional concurrency pool.Answer
- CConfigure the telemetry processing Lambda function inside a private subnet, and route all outbound database traffic through a single NAT Gateway deployed in a single Availability Zone.
- DStore the database credentials in AWS Secrets Manager, encrypt them using the default AWS-managed KMS key, and configure the KMS key policy to grant decryption permissions to the Lambda function's IAM role.
- EIncrease the default unreserved concurrency limit of the AWS account and configure provisioned concurrency on the customer billing and payment Lambda functions to absorb telemetry-induced bursts.