New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon DVA-C02 Exam - Topic 3 Question 45 Discussion

Actual exam question for Amazon's DVA-C02 exam
Question #: 45
Topic #: 3
[All DVA-C02 Questions]

A banking company is building an application for users to create accounts, view balances, and review recent transactions. The company integrated an Amazon API Gateway REST API with AWS Lambda functions. The company wants to deploy a new version of a Lambda function that gives customers the ability to view their balances. The new version of the function displays customer transaction insights. The company wants to test the new version with a small group of users before deciding whether to make the feature available for all users. Which solution will meet these requirements with the LEAST disruption to users?

Show Suggested Answer Hide Answer
Suggested Answer: A

API Gateway's canary deployments allow gradual traffic shifting to a new version of a function, minimizing disruption while testing.

Why Option A is Correct:

Gradual Rollout: Reduces risk by incrementally increasing traffic.

Rollback Support: Canary deployments make it easy to revert to the previous version.

Why Not Other Options:

Option B: Redeploying the stage disrupts all users.

Option C & D: Managing new stages and weighted routing introduces unnecessary complexity.


Canary Deployments in API Gateway

Contribute your Thoughts:

0/2000 characters
Alberta
3 months ago
Why not just deploy it all at once? Seems risky otherwise.
upvoted 0 times
...
Carla
3 months ago
Option A is definitely the way to go!
upvoted 0 times
...
Colene
3 months ago
Wait, can we really revert that easily if something goes wrong?
upvoted 0 times
...
Fernanda
4 months ago
I agree, gradual traffic increase is smart.
upvoted 0 times
...
Dottie
4 months ago
A canary deployment sounds like the safest option!
upvoted 0 times
...
Yuki
4 months ago
I recall something about using Route 53 for traffic distribution, which makes option D interesting. But I’m not sure if it’s the best choice for this scenario.
upvoted 0 times
...
Maynard
4 months ago
I practiced a similar question where we had to route traffic to different stages. Option C seems like it could work, but I wonder if it’s as effective as a canary deployment.
upvoted 0 times
...
Lindsay
4 months ago
I'm not entirely sure, but I think option B might cause more downtime if we have to revert back. It feels riskier than the canary approach.
upvoted 0 times
...
Tamekia
5 months ago
I remember studying canary deployments, and I think option A sounds familiar. It seems like a safe way to test the new version with minimal disruption.
upvoted 0 times
...
Robt
5 months ago
Ah, I see. The question is asking for the least disruptive solution, so we'll want to avoid fully redeploying the API or creating a new stage. Canary deployments seem like the way to go here.
upvoted 0 times
...
Norah
5 months ago
Okay, I think I've got this. The key is to gradually roll out the new version to a subset of users, and have the ability to quickly revert if any issues are detected. Option A sounds like the best approach for that.
upvoted 0 times
...
Naomi
5 months ago
Hmm, I'm a bit unsure about the differences between the deployment options here. I'll need to review the details of each approach to make sure I understand the tradeoffs.
upvoted 0 times
...
Myra
5 months ago
This seems like a classic deployment strategy question. I'll need to carefully consider the options to determine the least disruptive solution.
upvoted 0 times
...
Diane
1 year ago
I prefer option D. Using weighted alias record set in Route 53 can help distribute traffic and minimize disruption if the new version fails.
upvoted 0 times
...
Nell
1 year ago
I agree with Frank. Canary deployment is a good way to test the new version without disrupting all users at once.
upvoted 0 times
...
Frank
1 year ago
I think option A is the best choice. Gradually increasing traffic to the new version will help identify any issues before full deployment.
upvoted 0 times
...
Hobert
1 year ago
Yikes, I just hope none of these candidates try to deploy the new version via carrier pigeon. That would be a real disruption!
upvoted 0 times
...
Amalia
1 year ago
Hmm, I'm torn between B and C. Both sound like they could work, but C just feels a bit more elegant.
upvoted 0 times
...
Jestine
1 year ago
I agree, C is the safest option. Gotta love those AWS features that make rolling out new versions a breeze.
upvoted 0 times
Keneth
1 year ago
I agree, C is the safest option. Gotta love those AWS features that make rolling out new versions a breeze.
upvoted 0 times
...
Noemi
1 year ago
Yeah, AWS definitely makes it easier to manage deployments. Can't go wrong with their features.
upvoted 0 times
...
Claudio
1 year ago
C) Deploy the new version of the function to a new stage in the REST API. Route traffic to the new stage. If the new version fails, route traffic to the original stage.
upvoted 0 times
...
Elly
1 year ago
I think C is the best option too. It's always good to have a backup plan.
upvoted 0 times
...
...
Ammie
1 year ago
Option C seems like the way to go. Gradual rollout and easy revert if issues are detected.
upvoted 0 times
Destiny
1 year ago
That makes sense. It's better to catch any issues early on before impacting all users.
upvoted 0 times
...
Graham
1 year ago
I agree, it's important to test new features with a small group before rolling out to everyone.
upvoted 0 times
...
Yoko
1 year ago
Option C seems like the way to go. Gradual rollout and easy revert if issues are detected.
upvoted 0 times
...
...

Save Cancel