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.

• ✗

  Update alias, update function code, publish version

  Why it's wrong here

  Updating an alias before the new function code is even deployed and published as a distinct version is premature and ineffective. An alias must point to an existing, immutable version of the Lambda function. Attempting to update it at this stage would either point to the old code or fail because the desired new version does not yet exist, preventing proper traffic redirection.

• ✗

  Create alias, update function code, publish version

  Why it's wrong here

  Creating an alias requires specifying a target Lambda function version ARN. If the developer attempts to create an alias before the new function code has been deployed and subsequently published as a new, immutable version, there is no specific version for the alias to reference. This sequence would prevent the alias from being correctly configured to point to the desired new deployment.

• ✗

  Publish version, update function code, update alias

  Why it's wrong here

  Publishing a version of a Lambda function creates an immutable snapshot of the function's *current* code and configuration. If this step occurs *before* the new function code has been updated, the published version will inadvertently contain the old code. This would result in deploying the previous functionality under a new version number, necessitating another code update and version publication to achieve the desired outcome.

• ✓

  Update function code, publish version, update alias

  Why this is correct

  First, updating the function code ensures the `$LATEST` version contains the desired new logic. Next, publishing a version creates an immutable snapshot of this updated code, providing a stable reference point. Finally, updating the alias to point to this newly published version allows for controlled traffic shifting, enabling safe deployments, rollbacks, and advanced strategies like canary releases.