MENU
A DevOps engineer manages a web application that runs on Amazon EC2 instances behind an Application Load Balancer (ALB). The instances run in an EC2 Auto Scaling group across multiple Availability Zones. The engineer needs to implement a deployment strategy that:
Launches a second fleet of instances with the same capacity as the original fleet.
Maintains the original fleet unchanged while the second fleet is launched.
Transitions traffic to the second fleet when the second fleet is fully deployed.
Terminates the original fleet automatically 1 hour after transition.
Which solution will satisfy these requirements?
Suggested Answer: D
Get Premium DOP-C02 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
44 comments · newest first
NA
Nathalie
11 months ago
I’m not sure about D, seems overly complicated for this scenario.
ER
Erin
11 months ago
B is also a good choice, but I think C has more control.
HE
Helga
11 months ago
Wait, does that really work with a 1-hour wait? Sounds risky.
MI
Mitzie
11 months ago
I agree, C is solid for managing traffic transition!
BU
Buffy
12 months ago
Option C seems like the best fit for blue/green deployment.
JA
Jackie
12 months ago
I practiced a similar question about deployment strategies, and I think option C is the most aligned with the requirements given.
ES
Estrella
1 year ago
I feel like the CloudFormation option might not fully meet the requirements since it doesn't mention traffic transition clearly.
GO
Goldie
1 year ago
I think AWS CodeDeploy could work well for this scenario, especially with the waiting period option.
CA
Candra
1 year ago
I remember studying blue/green deployments, but I'm not sure if Elastic Beanstalk is the best choice here.
LE
Lenny
1 year ago
I've got a good handle on these deployment strategies, so I feel confident I can identify the right solution here. I'll carefully evaluate each option against the requirements.
ZA
Zack
1 year ago
Whew, this is a lot to consider. I'm not sure I fully understand the differences between the deployment options like CloudFormation, Elastic Beanstalk, and CodeDeploy. I'll need to review those concepts before attempting this.
FR
Francis
1 year ago
Hmm, I'm a bit confused about the different deployment options here. I'll need to carefully read through each choice and think through the requirements.
DA
Darci
1 year ago
This looks like a pretty straightforward deployment strategy question. I think I can handle this one.
CH
Chau
1 year ago
Okay, let's see. The key things I need to focus on are launching a second fleet, maintaining the original while the new one is deployed, transitioning traffic, and terminating the original after an hour. I think I can work through this step-by-step.
YO
Yolando
1 year ago
Hmm, I'm a bit unsure about this one. The options seem similar, and I'll need to carefully read through the requirements to determine the best fit.
AL
Alyce
1 year ago
Option D, eh? Ah, the good old 'set it and forget it' approach. I wonder if the Elastic Beanstalk fairy will just wave her magic wand and make it all work out in the end.
MA
Martina
1 year ago
Option A, huh? Sounds like the DevOps engineer is just winging it and hoping the ALB doesn't pull a disappearing act. Maybe they can summon the AWS gods to keep it alive for that one magical hour.
EL
Elliot
1 year ago
Hold up, Option A with CloudFormation and Route 53 updates? That's like trying to fix a leaky faucet with duct tape and a prayer. Not my cup of tea.
IZ
Izetta
1 year ago
Let's go with Option C then, it seems like the most reliable solution.
LO
Lonny
1 year ago
Yeah, AWS CodeDeploy offers more control and automation compared to manually updating Route 53.
KA
Kassandra
1 year ago
I think Option C with AWS CodeDeploy might be a better fit for this scenario.
BR
Brett
1 year ago
Yeah, Option C sounds more reliable for this deployment strategy.
GI
Gilberto
1 year ago
I think Option C with AWS CodeDeploy might be a better solution.
ON
Ona
1 year ago
I agree, Option A seems like a risky choice.
MI
Miles
1 year ago
I agree, Option A seems like a risky choice.
LA
Lashawn
1 year ago
Hmm, Option D with Elastic Beanstalk and the immutable deployment seems interesting. Setting the deletion policy on the ALB is a clever way to handle the termination requirement.
SH
Shanda
1 year ago
It's important to have a smooth deployment strategy in place to avoid any disruptions to the application.
SU
Sunshine
1 year ago
I agree, setting the deletion policy on the ALB for 1 hour seems like a smart way to handle the transition.
DO
Dorthy
1 year ago
Option D with Elastic Beanstalk and the immutable deployment sounds like a solid choice.
JI
Jina
1 year ago
I'm not sure about the other options, but Option C with CodeDeploy and the blue/green configuration sounds pretty solid. Terminating the original instances after 1 hour is a nice touch.
RE
Ressie
1 year ago
The waiting period of 1 hour before terminating the original instances provides a safety net in case of any issues with the new fleet.
KI
Kimbery
1 year ago
Yeah, using a blue/green deployment strategy with CodeDeploy makes the transition smooth and automated.
SO
Son
1 year ago
I agree, Option C with CodeDeploy seems like the best choice for this scenario.
OL
Oliva
2 years ago
Option B looks like the perfect solution to me. Using Elastic Beanstalk environments for blue/green deployment and a lifecycle policy to handle the original environment termination - that's exactly what the question asks for.
BR
Britt
1 year ago
Definitely, it meets all the requirements mentioned in the question.
PA
Pauline
1 year ago
And having a lifecycle policy to handle the original environment termination is key.
JO
Jovita
1 year ago
I agree, using Elastic Beanstalk for blue/green deployment is a good choice.
VE
Verdell
1 year ago
Option B looks like the perfect solution to me.
NO
Noah
2 years ago
I'm not sure, I think option B could also work. Using Elastic Beanstalk for blue/green deployment with a lifecycle policy to terminate the original environment after 1 hour could be a good approach.
NI
Nickole
2 years ago
I agree with Bok. Option C seems like the most efficient way to handle the deployment strategy while ensuring the original fleet is terminated after the transition.
BO
Bok
2 years ago
I think option C is the best solution. Using AWS CodeDeploy with blue/green deployment will allow for a smooth transition and automatic termination of the original fleet after 1 hour.
JO
Josefa
2 years ago
I'm not sure, I think option B could also work well with Elastic Beanstalk. It offers a blue/green deployment strategy which could be beneficial in this scenario.
CH
Christene
2 years ago
I agree with Ira. CodeDeploy seems like the most efficient way to handle the deployment and transition process.
IR
Ira
2 years ago
I think option C is the best solution. CodeDeploy allows for a smooth transition and automatic termination of the original fleet after 1 hour.