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 DVA-C02 Exam - Topic 3 Question 12 Discussion

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

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.

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

0/2000 characters
Billi
5 months ago
Definitely going with rolling, can't afford any downtime!
upvoted 0 times
...
Sarah
5 months ago
All at once? That sounds risky!
upvoted 0 times
...
Amber
5 months ago
Snapshots sound interesting, but are they really practical for this?
upvoted 0 times
...
Mari
6 months ago
I think immutable deployments are better for quick rollbacks.
upvoted 0 times
...
Verdell
6 months ago
Rolling deployments are the way to go for zero downtime!
upvoted 0 times
...
Bette
6 months 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.
upvoted 0 times
...
Page
6 months 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.
upvoted 0 times
...
Stephanie
6 months 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.
upvoted 0 times
...
Miles
6 months ago
I remember studying deployment strategies, and I think rolling updates might be the best option here since they minimize downtime.
upvoted 0 times
...
Pura
7 months 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.
upvoted 0 times
...
Lavera
7 months 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.
upvoted 0 times
...
Patria
7 months ago
Didn't we do a practice question on this? I feel like it was mostly focused on distributing certificates.
upvoted 0 times
...
Gregg
11 months 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.
upvoted 0 times
Sage
10 months ago
C) Snapshots
upvoted 0 times
...
Margot
11 months ago
B) Rolling
upvoted 0 times
...
Ruby
11 months ago
A) All at once
upvoted 0 times
...
...
Cherri
12 months 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!
upvoted 0 times
Evelynn
10 months ago
User 3: 'Immutable' deployments are the best option for minimizing impact and ensuring quick rollback.
upvoted 0 times
...
Willie
11 months ago
User 2: I prefer 'Rolling' deployments. It's safer and less risky.
upvoted 0 times
...
Willodean
11 months ago
User 1: I think 'All at once' is the way to go. Let's just get it done quickly.
upvoted 0 times
...
...
Rueben
12 months ago
Oh, 'Snapshots'! That way, they can just roll back to the previous version if something goes wrong. Simple and effective, right?
upvoted 0 times
Arlyne
10 months ago
D) Immutable
upvoted 0 times
...
Mitsue
10 months ago
C) Snapshots
upvoted 0 times
...
Mollie
10 months ago
B) Rolling
upvoted 0 times
...
Gwenn
11 months ago
A) All at once
upvoted 0 times
...
Alaine
11 months ago
D) Immutable
upvoted 0 times
...
Dustin
11 months ago
C) Snapshots
upvoted 0 times
...
Fidelia
11 months ago
B) Rolling
upvoted 0 times
...
Slyvia
12 months ago
A) All at once
upvoted 0 times
...
...
Elza
1 year 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.
upvoted 0 times
Lisbeth
11 months ago
Yeah, 'Immutable' deployment definitely minimizes the risk of downtime. It's a smart choice.
upvoted 0 times
...
Zachary
11 months ago
I agree, 'Immutable' deployment seems like the safest option. No room for error.
upvoted 0 times
...
...
Altha
1 year ago
I think the answer is 'Rolling' deployment. It allows for a gradual rollout, minimizing impact and enabling a quick rollback if needed.
upvoted 0 times
...
Rodolfo
1 year ago
I prefer Immutable deployment, it ensures consistency and reliability.
upvoted 0 times
...
Lasandra
1 year ago
I agree with Mitsue, Rolling deployment allows for minimal impact and easy rollback.
upvoted 0 times
...
Mitsue
1 year ago
I think we should go with Rolling deployment.
upvoted 0 times
...

Save Cancel