Soru

Zorluk: OrtaDeployment Strategies

A developer is releasing an update to a production REST API managed by Amazon API Gateway. The update includes changes to both the API Gateway resource structure and the backend integrations. To minimize risk, the developer wants to route 15%15\% of the API traffic to the new version while the remaining 85%85\% is handled by the stable production version. The strategy must support immediate rollback to the stable version without modifying client configurations or deploying new API stages. Which approach should the developer use to meet these requirements?

  1. Configure a canary release on the existing API Gateway deployment stage and set the canary traffic percentage to 15%15\%.Cevap
  2. B
    Deploy the update to a new API Gateway stage and configure an Amazon Route 53 weighted routing policy pointing to both stages.
  3. C
    Set up AWS CodeDeploy to perform a Canary15Percent10Minutes deployment targeting the API Gateway stage.
  4. D
    Deploy the update to a new stage and use an Application Load Balancer weighted target group to distribute traffic between the two stage URLs.

Cevap

Configure a canary release on the existing API Gateway deployment stage and set the canary traffic percentage to 15%15\%.
Configuring a canary release on the existing API Gateway stage is the only option that keeps the endpoint URL unchanged for clients, avoids creating new stages, and allows immediate rollback by deleting the canary release.

Adım Adım Çözüm

1
Analyze the deployment constraints: 15%15\% traffic routing, 85%85\% remaining on stable, immediate rollback capability, no client configuration changes, and no creation of new API stages.
Identify that the deployment must take place within the existing API Gateway stage and support built-in traffic shifting.
Creating new stages or changing DNS/client endpoints is prohibited by the scenario requirements.
2
Evaluate the capabilities of Amazon API Gateway deployment stages.
Determine that API Gateway supports configuring a Canary release directly on a stage, allowing a designated percentage of traffic (e.g., 15%15\%) to be sent to a new deployment.
This configuration keeps the stage endpoint URL identical for clients and allows immediate promotion or deletion of the canary to rollback.
3
Compare the correct API Gateway canary configuration with other alternatives.
Confirm that Route 53, CodeDeploy, and Application Load Balancer solutions either require new stages or are not supported natively for shifting API Gateway stage configuration traffic.
Eliminating options that violate the no-new-stage constraint ensures the selection of the correct option.

Anahtar Kavram

API Gateway Canary Deployments
Bu soruyu puanla