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.

• ✗

  Run the update-function-code command again with the --publish flag.

  Why it's wrong here

  The update-function-code command, when executed without the --publish flag, updates only the $LATEST version of the Lambda function. Running it again with --publish would overwrite $LATEST again with potentially the same code and then publish that as a new version. The goal is to publish the already updated $LATEST as a new version, not to re-update and then publish. The --publish flag is specifically for publishing at the time of the code update, not for publishing a previously updated $LATEST.

• ✗

  Run the delete-function command and then create-function with the updated code.

  Why it's wrong here

  Deleting the function entirely with delete-function and then recreating it with create-function would result in a completely new function ARN, effectively erasing all existing versions, aliases, triggers, and associated configurations. This drastic action is not an appropriate or efficient method for simply creating a new version of an existing function. Lambda versioning is specifically designed to manage multiple code deployments for the same function without requiring a full recreation, preserving its identity and history.

• ✓

  Run the publish-version command to create a new version from the updated $LATEST.

  Why this is correct

  The publish-version command is the precise and correct mechanism to create an immutable, numbered version of a Lambda function based on the current state of its $LATEST qualifier. Since the developer has already successfully updated the function's code (which implicitly updates $LATEST), this command will capture that specific, updated code as a new, distinct version. This new version can then be referenced by aliases, enabling controlled deployments and reliable rollbacks.

• ✗

  Run the update-function-configuration command to set the version number.

  Why it's wrong here

  The update-function-configuration command is exclusively used to modify various configuration settings of an existing Lambda function, such as memory allocation, timeout duration, environment variables, or the execution role. It does not possess any functionality or parameters to create new versions of the function or to directly "set" a version number. Version numbers are automatically generated and assigned by Lambda only when a new version is explicitly published, not through configuration updates.

Go deeper

Related to this question