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.

• ✗

  Configure a CodeDeploy deployment group in the SAM template.

  Why it's wrong here

  While AWS CodeDeploy is the underlying service that performs the traffic shifting for SAM's canary deployments, a developer does not directly configure a CodeDeploy DeploymentGroup resource in the SAM template. Instead, SAM abstracts this by using specific Lambda function properties, such as DeploymentPreference, which then instruct SAM to provision and manage the necessary CodeDeploy resources automatically. Directly defining a CodeDeploy DeploymentGroup is not the standard or correct approach for enabling SAM's built-in canary deployments.

• ✗

  Create a Lambda alias and configure traffic shifting manually.

  Why it's wrong here

  Manually creating a Lambda alias and then configuring traffic shifting through the AWS console or CLI would bypass the significant automation provided by SAM. SAM's AutoPublishAlias and DeploymentPreference properties are specifically designed to automate the creation of aliases, the publishing of new Lambda versions, and the controlled traffic shifting between versions, eliminating the need for manual intervention during deployment. This manual approach defeats the purpose of using SAM for streamlined, automated canary deployments.

• ✓

  Add the AutoPublishAlias and DeploymentPreference properties to the Lambda function in the SAM template.

  Why this is correct

  This is the correct and most efficient method for enabling canary deployments with SAM. The AutoPublishAlias property in a SAM Lambda function resource automatically creates a new Lambda version and an alias pointing to it upon deployment, facilitating robust version management. The DeploymentPreference property then configures the traffic shifting strategy, including options for canary or linear deployments, automated rollback alarms, and pre/post-traffic hooks, all orchestrated by AWS CodeDeploy under the hood, enabling fully automated canary deployments.

• ✗

  Use AWS CodePipeline to orchestrate the canary deployment.

  Why it's wrong here

  AWS CodePipeline is a continuous delivery service used to automate entire release pipelines, which can include building, testing, and deploying applications. While CodePipeline can certainly be used to orchestrate the *entire* deployment process for a SAM application, it is not a prerequisite or the direct mechanism for enabling the *canary deployment itself* within SAM. SAM's built-in canary deployment capabilities, configured via DeploymentPreference, function independently of CodePipeline, handling the traffic shifting logic directly through CloudFormation and CodeDeploy.