New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon DOP-C02 Exam - Topic 4 Question 23 Discussion

Actual exam question for Amazon's DOP-C02 exam
Question #: 23
Topic #: 4
[All DOP-C02 Questions]

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?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

0/2000 characters
Nathalie
3 months ago
I’m not sure about D, seems overly complicated for this scenario.
upvoted 0 times
...
Erin
3 months ago
B is also a good choice, but I think C has more control.
upvoted 0 times
...
Helga
3 months ago
Wait, does that really work with a 1-hour wait? Sounds risky.
upvoted 0 times
...
Mitzie
4 months ago
I agree, C is solid for managing traffic transition!
upvoted 0 times
...
Buffy
4 months ago
Option C seems like the best fit for blue/green deployment.
upvoted 0 times
...
Jackie
4 months ago
I practiced a similar question about deployment strategies, and I think option C is the most aligned with the requirements given.
upvoted 0 times
...
Estrella
4 months ago
I feel like the CloudFormation option might not fully meet the requirements since it doesn't mention traffic transition clearly.
upvoted 0 times
...
Goldie
4 months ago
I think AWS CodeDeploy could work well for this scenario, especially with the waiting period option.
upvoted 0 times
...
Candra
5 months ago
I remember studying blue/green deployments, but I'm not sure if Elastic Beanstalk is the best choice here.
upvoted 0 times
...
Lenny
5 months 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.
upvoted 0 times
...
Zack
5 months 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.
upvoted 0 times
...
Francis
5 months 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.
upvoted 0 times
...
Darci
5 months ago
This looks like a pretty straightforward deployment strategy question. I think I can handle this one.
upvoted 0 times
...
Chau
5 months 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.
upvoted 0 times
...
Yolando
5 months 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.
upvoted 0 times
...
Alyce
9 months 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.
upvoted 0 times
...
Martina
9 months 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.
upvoted 0 times
...
Elliot
9 months 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.
upvoted 0 times
Izetta
8 months ago
Let's go with Option C then, it seems like the most reliable solution.
upvoted 0 times
...
Lonny
8 months ago
Yeah, AWS CodeDeploy offers more control and automation compared to manually updating Route 53.
upvoted 0 times
...
Kassandra
8 months ago
I think Option C with AWS CodeDeploy might be a better fit for this scenario.
upvoted 0 times
...
Brett
8 months ago
Yeah, Option C sounds more reliable for this deployment strategy.
upvoted 0 times
...
Gilberto
8 months ago
I think Option C with AWS CodeDeploy might be a better solution.
upvoted 0 times
...
Ona
8 months ago
I agree, Option A seems like a risky choice.
upvoted 0 times
...
Miles
9 months ago
I agree, Option A seems like a risky choice.
upvoted 0 times
...
...
Lashawn
10 months 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.
upvoted 0 times
Shanda
8 months ago
It's important to have a smooth deployment strategy in place to avoid any disruptions to the application.
upvoted 0 times
...
Sunshine
9 months ago
I agree, setting the deletion policy on the ALB for 1 hour seems like a smart way to handle the transition.
upvoted 0 times
...
Dorthy
9 months ago
Option D with Elastic Beanstalk and the immutable deployment sounds like a solid choice.
upvoted 0 times
...
...
Jina
10 months 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.
upvoted 0 times
Ressie
9 months 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.
upvoted 0 times
...
Kimbery
9 months ago
Yeah, using a blue/green deployment strategy with CodeDeploy makes the transition smooth and automated.
upvoted 0 times
...
Son
10 months ago
I agree, Option C with CodeDeploy seems like the best choice for this scenario.
upvoted 0 times
...
...
Oliva
10 months 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.
upvoted 0 times
Britt
8 months ago
Definitely, it meets all the requirements mentioned in the question.
upvoted 0 times
...
Pauline
9 months ago
And having a lifecycle policy to handle the original environment termination is key.
upvoted 0 times
...
Jovita
9 months ago
I agree, using Elastic Beanstalk for blue/green deployment is a good choice.
upvoted 0 times
...
Verdell
9 months ago
Option B looks like the perfect solution to me.
upvoted 0 times
...
...
Noah
10 months 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.
upvoted 0 times
...
Nickole
10 months 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.
upvoted 0 times
...
Bok
10 months 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.
upvoted 0 times
...
Josefa
11 months 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.
upvoted 0 times
...
Christene
11 months ago
I agree with Ira. CodeDeploy seems like the most efficient way to handle the deployment and transition process.
upvoted 0 times
...
Ira
11 months 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.
upvoted 0 times
...

Save Cancel