MENU
A company has a website that is developed in PHP and is launched using AWS Elastic Beanstalk. There is a new version of the website that needs to be deployed in the Elastic Beanstalk environment. The company cannot tolerate having the website offline if an update fails. Deployments must have minimal impact and rollback as soon as possible.
Suggested Answer: C
Get Premium DVA-C02 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
36 comments · newest first
BI
Billi
11 months ago
Definitely going with rolling, can't afford any downtime!
SA
Sarah
11 months ago
All at once? That sounds risky!
AM
Amber
11 months ago
Snapshots sound interesting, but are they really practical for this?
MA
Mari
12 months ago
I think immutable deployments are better for quick rollbacks.
VE
Verdell
12 months ago
Rolling deployments are the way to go for zero downtime!
BE
Bette
1 year ago
Snapshots sound familiar, but I’m not clear on how they fit into this situation. I think they’re more about backups than deployment strategies.
PA
Page
1 year ago
I practiced a similar question, and I think all at once deployments are risky for this scenario because they could take the site down if something goes wrong.
ST
Stephanie
1 year ago
I'm not entirely sure, but I feel like immutable deployments could also work well since they create new instances for the new version, which helps with rollback.
MI
Miles
1 year ago
I remember studying deployment strategies, and I think rolling updates might be the best option here since they minimize downtime.
PU
Pura
1 year ago
This seems straightforward enough. I'm going to go with option E, ToNumber([Customer Transactions Transaction Code]) >= 50. It looks like the most direct way to solve this problem.
LA
Lavera
1 year ago
Okay, I've got this. The Script helper is where you can find all the available commands that can be used in your automation scripts. That's definitely the right answer here. Feeling confident about this one.
PA
Patria
1 year ago
Didn't we do a practice question on this? I feel like it was mostly focused on distributing certificates.
GR
Gregg
1 year ago
You know, the company should just throw the website up on a hamster wheel and let the little guy power it. Guaranteed zero downtime and maximum cuteness factor.
SA
Sage
1 year ago
C) Snapshots
MA
Margot
1 year ago
B) Rolling
RU
Ruby
1 year ago
A) All at once
CH
Cherri
1 year ago
I'm going to go with 'All at once'. Why waste time with these fancy deployment methods? Just rip the band-aid off and get it done!
EV
Evelynn
1 year ago
User 3: 'Immutable' deployments are the best option for minimizing impact and ensuring quick rollback.
WI
Willie
1 year ago
User 2: I prefer 'Rolling' deployments. It's safer and less risky.
WI
Willodean
1 year ago
User 1: I think 'All at once' is the way to go. Let's just get it done quickly.
RU
Rueben
1 year ago
Oh, 'Snapshots'! That way, they can just roll back to the previous version if something goes wrong. Simple and effective, right?
AR
Arlyne
1 year ago
D) Immutable
MI
Mitsue
1 year ago
C) Snapshots
MO
Mollie
1 year ago
B) Rolling
GW
Gwenn
1 year ago
A) All at once
AL
Alaine
1 year ago
D) Immutable
DU
Dustin
1 year ago
C) Snapshots
FI
Fidelia
1 year ago
B) Rolling
SL
Slyvia
1 year ago
A) All at once
EL
Elza
2 years ago
Hmm, 'Immutable' deployment sounds like the way to go. No messing around with updates, just swap out the whole environment. Probably the safest option.
LI
Lisbeth
1 year ago
Yeah, 'Immutable' deployment definitely minimizes the risk of downtime. It's a smart choice.
ZA
Zachary
1 year ago
I agree, 'Immutable' deployment seems like the safest option. No room for error.
AL
Altha
2 years ago
I think the answer is 'Rolling' deployment. It allows for a gradual rollout, minimizing impact and enabling a quick rollback if needed.
RO
Rodolfo
2 years ago
I prefer Immutable deployment, it ensures consistency and reliability.
LA
Lasandra
2 years ago
I agree with Mitsue, Rolling deployment allows for minimal impact and easy rollback.
MI
Mitsue
2 years ago
I think we should go with Rolling deployment.