A developer published a change to a new version of an AWS Lambda function. To test the change, the developer must route 50% of the traffic to the new version and 60% of the traffic to the current vers

Question

Options

• ACreate two Amazon Route 53 records that use a simple routing policy to route traffic to the
• BCreate an Amazon API Gateway API with a POST method that is integrated with the Lambda
• CCreate a Lambda function alias. Set the weight to 50% for the current version and 50% for the
• DUpdate the event source mappings for the Lambda function. In the mappings, set the weight to

• A
  3% (1)
• B
  14% (4)
• C
  76% (22)
• D
  7% (2)

Explanation

Option C is correct because AWS Lambda natively supports weighted traffic routing through function aliases - you can assign percentage weights between two versions of the same function, making it the simplest, most operationally efficient canary deployment mechanism without introducing additional services. Note that the question contains a deliberate trick: 50% + 60% = 110%, which is impossible; AWS Lambda alias weights must sum to 100%, so the valid configuration is 50%/50% - recognizing this error is part of answering correctly.

Why the distractors are wrong:

• A (Route 53 simple routing): Simple routing policies don't support weighted distribution; you'd need a weighted routing policy, and even then, Route 53 routes to endpoints like ALBs or IPs - not directly to Lambda function versions.
• B (API Gateway): While API Gateway can trigger Lambda, configuring it to split traffic between two Lambda versions requires additional complexity and is not built-in, making it far less operationally efficient than a native alias.
• D (Event source mappings): Event source mappings (used for triggers like SQS or Kinesis) do not have a weight property for routing traffic between function versions - this feature simply doesn't exist.

Memory tip: Think of a Lambda alias as a "pointer with a dial" - it points to one version by default, but you can dial in a percentage (e.g., 50%) to shift traffic to a second version for canary testing, all within the Lambda console with zero extra infrastructure.

No community discussion yet for this question.