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.

• ✗

  An S3 lifecycle rule

  Why it's wrong here

  An S3 lifecycle rule is designed to automate the management of objects within an S3 bucket, such as transitioning them to different storage classes or expiring them after a set period. These rules operate exclusively on S3 object data and have no mechanism or capability to control, shift, or influence traffic routing to AWS Lambda functions or manage their deployment strategies.

• ✓

  A Lambda alias/deployment preference

  Why this is correct

  A Lambda alias, when combined with deployment preferences (often managed by AWS CodeDeploy), is the primary mechanism for implementing gradual traffic shifts for Lambda functions. This approach allows a new version of a Lambda function to incrementally receive a percentage of invocations, enabling canary or linear deployments and controlled rollouts to minimize risk.

• ✓

  CloudWatch alarms tied to deployment health

  Why this is correct

  CloudWatch alarms are essential for monitoring the health and performance of a Lambda function during a gradual deployment. By tying these alarms to key metrics like error rates, latency, or invocation counts, they can automatically detect issues with the new function version. If an alarm threshold is breached, it can trigger an automatic rollback of the deployment, ensuring service stability.

• ✗

  A public S3 bucket

  Why it's wrong here

  A public S3 bucket is primarily used for storing and serving static content or providing publicly accessible data storage. While Lambda functions can interact with S3 buckets (e.g., triggered by object uploads), a public S3 bucket itself offers no functionality for managing, routing, or gradually shifting invocation traffic between different versions of a Lambda function. Its role is data storage, not compute deployment control.