Examkin

Question

Difficulty: EasyModernizing Workloads with Serverless Architectures (Lambda and API Gateway)

An organization is launching a serverless backend using Amazon API Gateway and AWS Lambda. While the main API functions experience steady traffic, a specific administrative function executes bursty, resource-intensive import jobs. The team needs to prevent the bursty administrative function from degrading the performance of the main API functions, and they must implement a deployment strategy that allows safe, monitored rollbacks for new versions. Which TWO configurations should the solutions architect implement? (Select TWO.)

  1. Configure reserved concurrency on the administrative Lambda function to limit its maximum execution capacity and safeguard the account's unreserved concurrency pool.Answer
  2. Use AWS CodeDeploy to perform canary or linear deployments for the Lambda function versions to safely shift traffic and monitor rollback alarms.Answer
  3. C
    Leave the administrative Lambda function's concurrency unconfigured to allow it to scale dynamically and consume the entire regional concurrency pool during import spikes.
  4. D
    Deploy a single, non-redundant NAT Gateway in one Availability Zone to handle all outbound traffic from the Lambda functions to the database, relying on route tables for high availability.
  5. E
    Use the default AWS-managed KMS key (aws/lambda) to encrypt the Lambda environment variables and modify its key policy to allow cross-account access for external consumers.

Answer

The solutions architect should configure reserved concurrency on the administrative Lambda function and use AWS CodeDeploy to perform canary or linear deployments for the Lambda function versions.
Configuring reserved concurrency on the administrative Lambda function ensures it has a dedicated limit that it cannot exceed, which prevents it from exhausting the regional concurrency pool and throttling the main API functions. Additionally, using AWS CodeDeploy for canary or linear deployments provides a controlled environment where traffic is shifted gradually to new function versions and automatically rolled back if alarms are triggered.

Step-by-Step Solution

1
Isolate the bursty workload's resource usage by configuring reserved concurrency on the administrative Lambda function.
The administrative function is capped at a set concurrency limit, protecting the remaining regional pool for the steady-traffic main API functions.
This prevents regional throttling and ensures application reliability.
2
Integrate AWS CodeDeploy with the Lambda deployment pipeline to utilize canary or linear deployments.
Traffic is gradually shifted to the new version of the function while monitoring CloudWatch alarms.
This minimizes the blast radius of new deployments and enables automated rollbacks in case of errors.

Key Concept

Concurrency management and safe deployment strategies in serverless architectures
Rate this question

Topics

Modernizing Workloads with Serverless Architectures (Lambda and API Gateway)

More questions from this topic