MENU
A developer is deploying an AWS Lambda function The developer wants the ability to return to older versions of the function quickly and seamlessly.
How can the developer achieve this goal with the LEAST operational overhead?
Suggested Answer: B
Get Premium DVA-C02 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
A function alias is a pointer to a specific Lambda function version. You can use aliases to create different environments for your function, such as development, testing, and production. You can also use aliases to perform blue/green deployments by shifting traffic between two versions of your function gradually. This way, you can easily roll back to a previous version if something goes wrong, without having to redeploy your code or change your configuration. Reference:AWS Lambda function aliases
23 comments · newest first
KA
Karen Clark
12 days ago
B makes the most sense here because the tricky part is traffic shifting between versions using aliases with minimal overhead.
HA
Haruka Phan
2 days ago
It also lets you test an update with small traffic first, catching issues before full rollout.
WA
Walid Farooqi
5 days ago
I got B as well after rereading the scenario.
CA
Casey
2 months ago
B is definitely the least overhead. Quick and effective!
DA
Dalene
2 months ago
Option C is too manual. S3 is not efficient for quick rollbacks.
JE
Jerry
2 months ago
I like option D, but it feels like overkill for this.
EL
Elinore
2 months ago
Option A sounds complicated. Blue/green needs more setup.
GA
Gail
3 months ago
Agreed! Aliases let you switch versions easily.
LI
Lindsey
3 months ago
I think option B is the best choice. Aliases are simple.
CU
Curtis
3 months ago
Not sure about B, sounds too simple for complex apps.
HI
Hillary
3 months ago
Wow, I didn't know aliases could handle versioning so easily!
FL
Flo
3 months ago
I thought C was a good option too, but it sounds like more work.
RO
Rosio
3 months ago
I disagree, A seems more robust for deployments.
DA
Danilo
4 months ago
B is the way to go! Function aliases are super handy.
ER
Eric
4 months ago
B is definitely the least overhead, easy to switch versions.
CH
Chaya
4 months ago
Surprised that D isn't the best option here!
AV
Avery
4 months ago
C sounds like a lot of extra work to manage.
TR
Troy
6 months ago
I disagree, A seems more robust for blue/green.
MA
Mammie
6 months ago
B is the way to go! Function aliases are super handy.
LA
Lashanda
6 months ago
I think using AWS CodePipeline might be overkill for just rolling back to older versions. Aliases sound simpler.
MI
Mitzie
7 months ago
I feel like we had a practice question about blue/green deployments, but that seemed more complex than what’s needed here.
TR
Truman
7 months ago
I’m not entirely sure, but I think maintaining deployment packages in S3 could be more work than just using aliases.
TO
Tora
7 months ago
I remember we discussed using function aliases in class. It seems like a straightforward way to manage versions without too much hassle.