DVA-C02 Deployment Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Use Lambda function aliases with weighted traffic shifting.

  Why it's wrong here

  While AWS Lambda aliases support weighted traffic shifting between two function versions, this mechanism typically performs an immediate split (e.g., 10% to new, 90% to old, then 100% to new). It does not inherently provide the automated, time-based incremental shifting, such as "10% every 5 minutes," that CodeDeploy offers. This approach alone lacks the controlled, gradual rollout and automated rollback features required for a robust deployment strategy.

• ✗

  Use multiple Lambda function versions and update the alias gradually.

  Why it's wrong here

  Manually updating a Lambda alias's weights between multiple versions, even if done gradually, is a manual operational task. The question implies a need for an automated, controlled deployment strategy, which CodeDeploy is designed to provide. This manual approach lacks the automation, monitoring integration, and automatic rollback capabilities that are crucial for safe and efficient production deployments.

• ✗

  Configure AWS CloudFormation to update the Lambda alias.

  Why it's wrong here

  AWS CloudFormation is an infrastructure as code service primarily used for provisioning and managing AWS resources, including Lambda functions and aliases. While it can define and update the target versions for a Lambda alias, CloudFormation itself does not provide the dynamic, incremental traffic shifting logic or automated rollback capabilities. It manages the declarative state of resources, not the procedural orchestration of gradual traffic shifts over time.

• ✓

  Modify the CodeDeploy deployment configuration to use a linear 10% every 5 minutes instead of canary.

  Why this is correct

  AWS CodeDeploy, when integrated with Lambda, provides robust capabilities for automating gradual deployments. A linear deployment configuration, such as "Linear10PercentEvery5Minutes," precisely matches the requirement for shifting traffic in fixed increments over a defined time period. This strategy allows for careful monitoring during the rollout and automatic rollback if issues are detected, ensuring a controlled and safe deployment process.