nerdexam
Amazon

DVA-C02 · Question #265

A company uses AWS CloudFormation to deploy an application that uses an Amazon API Gateway REST API with AWS Lambda function integration. The application uses Amazon DynamoDB for data persistence…

The correct answer is D. Configure canary settings for the production stage API. Change the percentage of traffic directed. API Gateway canary release deployments allow routing a configurable percentage of production traffic to a new stage configuration, enabling gradual rollout without DNS or load balancer changes.

Submitted by rachelw· Mar 5, 2026Deployment

Question

A company uses AWS CloudFormation to deploy an application that uses an Amazon API Gateway REST API with AWS Lambda function integration. The application uses Amazon DynamoDB for data persistence. The application has three stages: development, testing, and production. Each stage uses its own DynamoDB table. The company has encountered unexpected issues when promoting changes to the production stage. The changes were successful in the development and testing stages. A developer needs to route 20% of the traffic to the new production stage API with the next production release. The developer needs to route the remaining 80% of the traffic to the existing production stage. The solution must minimize the number of errors that any single customer experiences. Which approach should the developer take to meet these requirements?

Options

  • AUpdate 20% of the planned changes to the production stage. Deploy the new production stage.
  • BUpdate the Amazon Route 53 DNS record entry for the production stage API to use a weighted
  • CDeploy an Application Load Balancer (ALB) in front of the REST API. Change the production API
  • DConfigure canary settings for the production stage API. Change the percentage of traffic directed

How the community answered

(41 responses)
  • A
    12% (5)
  • B
    2% (1)
  • C
    7% (3)
  • D
    78% (32)

Why each option

API Gateway canary release deployments allow routing a configurable percentage of production traffic to a new stage configuration, enabling gradual rollout without DNS or load balancer changes.

AUpdate 20% of the planned changes to the production stage. Deploy the new production stage.

Deploying only 20% of the planned changes to production is a code-level partial rollout strategy, not a traffic-splitting mechanism. It does not guarantee that only 20% of users experience the new behavior.

BUpdate the Amazon Route 53 DNS record entry for the production stage API to use a weighted

Route 53 weighted routing splits traffic at the DNS level, which can cause an individual user to receive different responses across requests since DNS is not session-sticky. This violates the requirement to minimize errors for any single customer.

CDeploy an Application Load Balancer (ALB) in front of the REST API. Change the production API

Deploying an ALB in front of API Gateway adds infrastructure complexity and cost, and ALB weighted target group routing is not designed for API Gateway canary scenarios with session-level consistency.

DConfigure canary settings for the production stage API. Change the percentage of traffic directedCorrect

API Gateway supports canary settings natively on a stage, allowing a developer to specify the percentage of traffic (e.g., 20%) directed to the canary release. This is built into the service and requires no additional infrastructure, directly addressing the requirement to minimize errors for individual customers through gradual exposure.

Concept tested: API Gateway canary release deployment for production traffic splitting

Source: https://docs.aws.amazon.com/apigateway/latest/developerguide/canary-release.html

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full DVA-C02 Practice