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.

• ✗

  The function's handler name is incorrect in the deployment package.

  Why it's wrong here

  An incorrect handler name within the deployment package does not prevent the Lambda function code from being uploaded or updated successfully. This configuration error is typically detected during the *invocation* of the function, resulting in an `InvalidParameterValueException` or a similar runtime error indicating the specified handler could not be found. Deployment itself, which involves uploading the code and configuring the function, would succeed without this specific issue causing a `ResourceConflictException`.

• ✗

  The Lambda function's IAM role is missing necessary permissions.

  Why it's wrong here

  If the Lambda function's IAM role lacks the required permissions, such as `lambda:UpdateFunctionCode` or `lambda:UpdateFunctionConfiguration`, the deployment operation would fail with an `AccessDeniedException`. This error explicitly indicates a lack of authorization for the caller to perform the requested action on the resource. A `ResourceConflictException`, however, signifies a contention over the resource itself due to an ongoing operation, not an issue with the caller's permissions.

• ✗

  The Lambda function's memory limit is set too low for the deployment package.

  Why it's wrong here

  The memory limit configured for a Lambda function primarily impacts its runtime execution, determining the maximum memory available for the function's processes during invocation. Setting this limit too low would lead to `OutOfMemoryError` exceptions during actual function execution if the workload exceeds the allocated memory. It does not, however, prevent the successful deployment or update of the function's code package itself, which is a separate administrative operation unrelated to runtime resource allocation.

• ✓

  Another deployment is currently in progress for the same Lambda function.

  Why this is correct

  AWS Lambda enforces serialization of deployment operations for a given function to maintain consistency and prevent race conditions. If a developer attempts to deploy a new version or update configuration while another update, such as a code upload or configuration change, is already in progress for the same function, the Lambda service will return a `ResourceConflictException`. This error specifically signals that the resource is temporarily unavailable for modification due to another ongoing operation.

Go deeper

Related to this question