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 1 Question 35 Discussion

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

A developer wants the ability to roll back to a previous version of an AWS Lambda function in the event of errors caused by a new deployment. How can the developer achieve this with MINIMAL impact on users?

Show Suggested Answer Hide Answer
Suggested Answer: A

Pseudo Parameters:CloudFormation provides pseudo parameters that reference runtime context, including the current AWS Region.

Operational Efficiency:TheAWS::Regionpseudo parameter offers the most direct and self-contained way to obtain the Region dynamically within the template.


CloudFormation Pseudo Parameters:https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/pseudo-parameter-reference.html

Contribute your Thoughts:

Cherry
21 days ago
I'm feeling a bit like a 'lambda' in this exam question. Get it? 'Lambda' function? Eh, tough crowd.
upvoted 0 times
...
Delsie
24 days ago
Why not just have the app auto-rollback to the previous version if it detects too many errors? That would be the most seamless approach.
upvoted 0 times
Patti
14 hours ago
A) Change the application to use an alias that points to the current version. Deploy the new version of the code Update the alias to use the newly deployed version. If too many errors are encountered, point the alias back to the previous version.
upvoted 0 times
...
...
Carolynn
1 months ago
Option D with the three aliases is the most complex, but it does give the most control over the rollout. Gradually shifting traffic is a good idea.
upvoted 0 times
Ruthann
16 days ago
I agree, having the ability to gradually shift traffic can help in case of errors with the new deployment.
upvoted 0 times
...
Fletcher
22 days ago
Option D sounds like a good way to control the rollout and minimize impact on users.
upvoted 0 times
...
...
Alexia
1 months ago
Option C is the simplest, but I'm not sure I like the idea of directly pointing the application back to the previous version. Seems risky.
upvoted 0 times
...
Renay
1 months ago
Option B with the 10% traffic split is an interesting approach. Gradually shifting users to the new version is a smart way to test it.
upvoted 0 times
Billy
3 days ago
Definitely, it allows for a controlled rollout and easy rollback if needed.
upvoted 0 times
...
Corrinne
8 days ago
It's a clever way to ensure that any errors can be caught early before affecting all users.
upvoted 0 times
...
Lottie
20 days ago
I agree, gradually directing 10% of users to the new version is a smart testing strategy.
upvoted 0 times
...
Cary
21 days ago
Option B sounds like a good way to minimize impact on users.
upvoted 0 times
...
...
Jeffrey
2 months ago
I prefer option D. It provides more flexibility by using multiple aliases to manage traffic and rollback if necessary.
upvoted 0 times
...
Mignon
2 months ago
I agree with Meghan. Option A minimizes impact on users by using aliases to control traffic flow.
upvoted 0 times
...
Meghan
2 months ago
I think option A is the best choice. It allows us to easily switch back to the previous version if needed.
upvoted 0 times
...
Evette
2 months ago
Option A seems like a straightforward way to roll back to the previous version. I like how it minimizes the impact on users.
upvoted 0 times
Santos
21 days ago
I agree, using an alias to switch versions is a smart approach.
upvoted 0 times
...
Rosalia
25 days ago
Option A seems like a good choice. It allows for easy rollback if needed.
upvoted 0 times
...
...

Save Cancel