Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon Exam DVA-C02 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:

Diane
5 days 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
7 days 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
12 days 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
19 days 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
22 days 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
23 days 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
2 days 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
3 days ago
Yeah, AWS definitely makes it easier to manage deployments. Can't go wrong with their features.
upvoted 0 times
...
Claudio
12 days 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
13 days ago
I think C is the best option too. It's always good to have a backup plan.
upvoted 0 times
...
...
Ammie
1 months ago
Option C seems like the way to go. Gradual rollout and easy revert if issues are detected.
upvoted 0 times
Destiny
7 days ago
That makes sense. It's better to catch any issues early on before impacting all users.
upvoted 0 times
...
Graham
12 days ago
I agree, it's important to test new features with a small group before rolling out to everyone.
upvoted 0 times
...
Yoko
23 days ago
Option C seems like the way to go. Gradual rollout and easy revert if issues are detected.
upvoted 0 times
...
...

Save Cancel