MENU
A company wants to migrate its content sharing web application hosted on Amazon EC2 to a serverless architecture. The company currently deploys changes to its application by creating a new Auto Scaling group of EC2 instances and a new Elastic Load Balancer, and then shifting the traffic away using an Amazon Route 53 weighted routing policy.
For its new serverless application, the company is planning to use Amazon API Gateway and AWS Lambd
a. The company will need to update its deployment processes to work with the new application. It will also need to retain the ability to test new features on a small number of users before rolling the features out to the entire user base.
Which deployment strategy will meet these requirements?
Suggested Answer: B
Get Premium DOP-C02 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
This corresponds to Option B: Add the AWS::CodeDeployBlueGreen transform and the AWS::CodeDeploy::BlueGreen hook parameter with the CodeDeployDefault.ECSLinear10PercentEvery1Minutes deployment configuration.
31 comments · newest first
ED
Edelmira
11 months ago
OpsWorks? Really? That feels outdated for this scenario.
WE
Wei
11 months ago
C is not serverless, why even mention it?
DE
Dexter
11 months ago
Wait, can you really use Lambda versions with CloudFormation?
TO
Tori
11 months ago
I agree, B is definitely the way to go!
LI
Linsey
12 months ago
B seems like the best option for canary releases.
MO
Moon
12 months ago
I vaguely remember something about blue/green deployments with Elastic Beanstalk, but I thought that was more for EC2 instances, not serverless.
ST
Stanford
1 year ago
I feel like using AWS CDK could be a good approach, but I can't recall if it supports canary releases effectively.
LA
Latrice
1 year ago
I think option B sounds familiar because it mentions Lambda function versions, which we practiced in our labs.
RO
Ronnie
1 year ago
I remember we discussed canary releases in class, but I'm not sure if Route 53 is the best choice for that.
JO
Jonell
1 year ago
I'm leaning towards option C with Elastic Beanstalk and a blue/green deployment. That seems like the simplest way to gradually shift traffic and test new features.
CO
Colby
1 year ago
Option A using AWS CDK and a Route 53 failover policy sounds like a good approach to me. The ability to do canary releases is an important requirement.
KI
Kirby
1 year ago
I'm a bit confused by the different deployment options here. I'll need to review the details of each one to decide which one best meets the requirements.
TA
Tamar
1 year ago
This seems like a straightforward question about serverless deployment strategies. I think option B using CloudFormation and Lambda function versions is the way to go.
MA
Malinda
1 year ago
Wait, so we're migrating a web app to serverless? I hope they're not trying to 'lift and shift' the whole thing. That's going to be a wild ride!
AL
Alica
1 year ago
OpsWorks, huh? I haven't used that in a while. Separating the API Gateway and Lambda functions into different layers could get messy.
MA
Makeda
1 year ago
Elastic Beanstalk's blue/green deployment sounds like a nice way to shift traffic gradually. That could work well for the serverless app.
TR
Trina
1 year ago
C: Promoting the new version after testing with a canary release strategy using AWS CloudFormation sounds like a solid plan.
GL
Glory
1 year ago
B: I think using AWS CDK with a Route 53 failover routing policy for canary release strategy could also be effective.
BR
Brigette
1 year ago
A: I agree, Elastic Beanstalk's blue/green deployment is a good option for gradual traffic shifting.
KA
Kayleigh
1 year ago
I think the CloudFormation approach with Lambda function versions is a good fit. Updating the stack and promoting the new version seems straightforward.
MA
Marnie
1 year ago
A: Plus, it allows for gradual traffic shifting to ensure a smooth transition for users.
DE
Denny
1 year ago
B: It definitely simplifies the process of updating the stack and promoting new versions when testing is complete.
NI
Niesha
1 year ago
A: I agree, using CloudFormation with Lambda function versions for canary release strategy sounds like a solid plan.
LA
Laura
1 year ago
The AWS CDK option sounds interesting, but using a Route 53 failover policy might be overkill for a canary release strategy.
KI
Kirby
1 year ago
D: Yeah, CloudFormation and canary release sound like a good fit for testing new features.
SH
Sharen
1 year ago
C: Option B seems more straightforward with CloudFormation and canary release strategy.
LE
Leah
1 year ago
B: I agree, but I think using Route 53 failover for canary release might be too complex.
CA
Casey
1 year ago
A: I think option A with AWS CDK is a good choice.
VE
Veronica
2 years ago
I'm not sure, I think option B could also work well with the canary release strategy. It's important to consider all options before making a decision.
TH
Theodora
2 years ago
I agree with Rodrigo. Option A seems to be the most flexible and efficient deployment strategy for the company's needs.
RO
Rodrigo
2 years ago
I think option A is the best choice because it allows for canary releases and updating the CloudFormation stack easily.