MENU
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?
Suggested Answer: A
Get Premium DVA-C02 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
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.
37 comments · newest first
JI
Jina
11 months ago
C sounds risky, no gradual testing at all!
DE
Deane
11 months ago
Wait, can you really just switch aliases like that?
WH
Whitney
11 months ago
D seems overly complicated for just a rollback.
TE
Teresita
11 months ago
I think B is better for gradual rollouts.
SH
Shantell
12 months ago
Option A is the simplest way to roll back.
FA
Fanny
12 months ago
I’m leaning towards option B since it allows for a gradual rollout, but I’m not entirely sure if that’s the best way to handle errors.
AD
Adelle
1 year ago
I practiced a question like this, and I feel like option D is overcomplicated. I wonder if the simpler options might be just as effective.
TA
Tammi
1 year ago
I think option A sounds familiar because it’s straightforward, but I’m not confident if it minimizes user impact as much as option B might.
CH
Chauncey
1 year ago
I remember studying how aliases work with Lambda versions, but I'm not sure if we should use an alias for gradual traffic shifting or just roll back completely.
LE
Lennie
1 year ago
Option C seems the simplest, but I'm not sure if directly updating the ARN is the best practice here. I'll need to double-check the AWS documentation on that.
AF
Afton
1 year ago
Option D looks like the most robust solution, with the ability to gradually roll out the new version and easily roll back if needed. That's the one I'm leaning towards.
LE
Leigha
1 year ago
I'm a bit confused by the different alias options. I'll need to review the details of each approach more carefully before deciding.
OR
Orville
1 year ago
This question seems straightforward. I think option A is the best approach to minimize impact on users.
JE
Jeannetta
1 year ago
I'm a bit confused on this one. I know the CALs are important, but I'm not sure which file would be the right one to restore. I'll have to review the material again and see if I can figure it out.
CH
Cherry
1 year ago
I'm feeling a bit like a 'lambda' in this exam question. Get it? 'Lambda' function? Eh, tough crowd.
DE
Delsie
1 year 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.
MI
Micaela
1 year 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).
AM
Amie
1 year 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
PA
Patti
1 year 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.
CA
Carolynn
1 year 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.
SH
Shenika
1 year ago
It's important to have a plan in place to easily roll back changes if needed, especially for critical functions like AWS Lambda.
RU
Ruthann
1 year ago
I agree, having the ability to gradually shift traffic can help in case of errors with the new deployment.
FL
Fletcher
1 year ago
Option D sounds like a good way to control the rollout and minimize impact on users.
AL
Alexia
1 year 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.
RE
Renay
2 years 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.
BI
Billy
1 year ago
Definitely, it allows for a controlled rollout and easy rollback if needed.
CO
Corrinne
1 year ago
It's a clever way to ensure that any errors can be caught early before affecting all users.
LO
Lottie
1 year ago
I agree, gradually directing 10% of users to the new version is a smart testing strategy.
CA
Cary
1 year ago
Option B sounds like a good way to minimize impact on users.
JE
Jeffrey
2 years ago
I prefer option D. It provides more flexibility by using multiple aliases to manage traffic and rollback if necessary.
MI
Mignon
2 years ago
I agree with Meghan. Option A minimizes impact on users by using aliases to control traffic flow.
ME
Meghan
2 years ago
I think option A is the best choice. It allows us to easily switch back to the previous version if needed.
EV
Evette
2 years ago
Option A seems like a straightforward way to roll back to the previous version. I like how it minimizes the impact on users.
JO
Jovita
1 year ago
Having that flexibility is key in case errors occur during deployment.
CA
Carlee
1 year ago
It definitely minimizes the impact on users, which is important.
SA
Santos
1 year ago
I agree, using an alias to switch versions is a smart approach.
RO
Rosalia
1 year ago
Option A seems like a good choice. It allows for easy rollback if needed.