A developer is updating the code for an AWS Lambda function to add new capabilities. The Lambda function has version aliases for production and development environments that run separate versions of t

Question

Options

• ACreate a weighted alias that references the production version of the function and the updated
• BAdd a Network Load Balancer. Add the production version of the function and updated version of
• CUse AWS CodeDeploy to create a linear traffic shifting deployment
• DCreate a tag for the Lambda function that contains the production version and updated version of

• A
  71% (25)
• B
  3% (1)
• C
  9% (3)
• D
  17% (6)

Explanation

Option A is correct because Lambda weighted aliases let you split traffic between two function versions by percentage - perfect for a staging environment that needs to route invocations to both production and development simultaneously without changing the callers' endpoint.

Why the distractors are wrong:

• B - Network Load Balancers are for EC2/ECS targets, not Lambda version routing; this adds unnecessary complexity and doesn't solve the versioning problem natively.
• C - CodeDeploy linear deployments shift traffic away from the old version over time (for safe deployments), not maintain simultaneous routing to two specific versions as a stable staging setup.
• D - Lambda tags are metadata for organization and billing purposes; they have no traffic routing capability whatsoever.

Memory tip: Think of a weighted alias as a "traffic splitter knob" - you dial in what percentage goes to each version (e.g., 70% prod / 30% dev). The key phrase in the question is "handle invocations to both" simultaneously, which is the exact use case weighted aliases were designed for.

No community discussion yet for this question.