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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

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

by Charisse at Sep 10, 2024, 07:43 AM

Limited Time Offer

25%

Off

Get Premium DVA-C02 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Cherry
2 months ago
I'm feeling a bit like a 'lambda' in this exam question. Get it? 'Lambda' function? Eh, tough crowd.
upvoted 0 times
...
Delsie
2 months 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
Micaela
4 days ago
C) Do not make any changes to the application. Deploy the new version of the code. If too many errors are encountered, point the application back to the previous version using the version number in the Amazon Resource Name (ARN).
upvoted 0 times
...
Amie
15 days ago
B) Change the application to use an alias that points to the current version. Deploy the new version of the code. Update the alias to direct 10% of users to the newly deployed version. If too many errors are encountered, send 100% of traffic to the previous version
upvoted 0 times
...
Patti
28 days 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
2 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
Shenika
26 days ago
It's important to have a plan in place to easily roll back changes if needed, especially for critical functions like AWS Lambda.
upvoted 0 times
...
Ruthann
1 months ago
I agree, having the ability to gradually shift traffic can help in case of errors with the new deployment.
upvoted 0 times
...
Fletcher
2 months ago
Option D sounds like a good way to control the rollout and minimize impact on users.
upvoted 0 times
...
...
Alexia
2 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
2 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
1 months ago
Definitely, it allows for a controlled rollout and easy rollback if needed.
upvoted 0 times
...
Corrinne
1 months ago
It's a clever way to ensure that any errors can be caught early before affecting all users.
upvoted 0 times
...
Lottie
2 months ago
I agree, gradually directing 10% of users to the new version is a smart testing strategy.
upvoted 0 times
...
Cary
2 months ago
Option B sounds like a good way to minimize impact on users.
upvoted 0 times
...
...
Jeffrey
3 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
3 months ago
I agree with Meghan. Option A minimizes impact on users by using aliases to control traffic flow.
upvoted 0 times
...
Meghan
3 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
3 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
Jovita
26 days ago
Having that flexibility is key in case errors occur during deployment.
upvoted 0 times
...
Carlee
27 days ago
It definitely minimizes the impact on users, which is important.
upvoted 0 times
...
Santos
2 months ago
I agree, using an alias to switch versions is a smart approach.
upvoted 0 times
...
Rosalia
2 months ago
Option A seems like a good choice. It allows for easy rollback if needed.
upvoted 0 times
...
...

Save Cancel