Examkin

Soru

Zorluk: OrtaModernizing Workloads with Serverless Architectures (Lambda and API Gateway)

An energy utility company is modernizing its smart grid meter data ingestion API on AWS. The system must process high-frequency periodic telemetry reports sent from millions of IoT smart meters. During peak hours, the volume of telemetry data spikes drastically. The backend processing logic is implemented using AWS Lambda functions triggered by Amazon API Gateway endpoints. The Lambda functions perform lightweight validation and write directly to an Amazon RDS PostgreSQL database located in a private VPC subnet. The company requires a secure, highly available architecture that prevents database connection exhaustion during peak traffic periods and ensures that the smart grid ingestion workload does not starve other critical administrative workloads of Lambda compute resources in the same AWS region. Which TWO actions should the Solutions Architect take to design a solution that meets these requirements?

  1. Configure Amazon RDS Proxy between the Lambda functions and the RDS PostgreSQL database to manage and reuse the database connections.Cevap
  2. Configure reserved concurrency on the smart grid ingestion Lambda functions to restrict the maximum number of concurrent executions they can consume.Cevap
  3. C
    Configure provisioned concurrency on the smart grid ingestion Lambda functions to scale dynamically up to the regional account execution limit.
  4. D
    Deploy a single NAT Gateway in one Availability Zone to route all outbound database traffic from the Lambda functions to the private RDS subnet.
  5. E
    Encrypt the database connections using the AWS-managed KMS key (aws/rds) to enable external administrative Lambda functions in a different AWS account to securely query the database.

Cevap

Configure Amazon RDS Proxy between the Lambda functions and the database, and configure reserved concurrency on the ingestion Lambda functions.
The correct options are configuring Amazon RDS Proxy and setting reserved concurrency. Amazon RDS Proxy manages database connection scaling and reuse, preventing connection limits from being exceeded during traffic spikes. Setting reserved concurrency limits the maximum executions of the ingestion function, protecting the account-level concurrency pool so other critical administrative Lambda functions in the same region are not starved of compute capacity.

Adım Adım Çözüm

1
Address database connection pooling for serverless workloads.
Using Amazon RDS Proxy creates a shared database connection pool, preventing connection exhaustion during high-concurrency Lambda execution spikes.
Lambda functions scale rapidly and spin up distinct container instances, each attempting to establish a separate database connection, which can quickly saturate the RDS PostgreSQL connection limit.
2
Address regional Lambda resource starvation.
Setting reserved concurrency on the ingestion Lambda function limits its maximum concurrent executions.
Without reserved concurrency limits, a spike in smart grid ingestion traffic could consume the entire regional concurrency pool (default 1,000), throttling other administrative serverless workloads in the same AWS account.

Anahtar Kavram

Serverless Database Integration and Concurrency Management
Tahmini Süre:2m 0s
Bu soruyu puanla

Konular

Modernizing Workloads with Serverless Architectures (Lambda and API Gateway)

Bu konudan daha fazla soru