A DevOps engineer is building a continuous deployment pipeline for a serverless application that uses AWS Lambda functions. The company wants to reduce the customer impact of an unsuccessful…

Question

Options

• AUse an AWS Serverless Application Model (AWS SAM) template to define the serverless
• BUse AWS CloudFormation to publish a new stack update, and include Amazon CloudWatch
• CUse AWS CloudFormation to publish a new version on every stack update, and include Amazon
• DUse AWS CodeBuild to add sample event payloads for testing to the Lambda functions. Publish a

• A
  70% (32)
• B
  9% (4)
• C
  17% (8)
• D
  4% (2)

Explanation

Explanation

Option A is correct because AWS SAM natively supports safe Lambda deployments through built-in traffic shifting (canary and linear deployment configurations) combined with AWS CodeDeploy and CloudWatch alarms - this combination allows gradual rollout of new Lambda versions and automatic rollback if alarms are triggered, directly addressing both requirements of minimizing customer impact and monitoring for issues.

Option B is incorrect because simply publishing a CloudFormation stack update performs an all-or-nothing deployment with no traffic shifting, meaning any bad deployment immediately impacts all customers with no gradual rollout capability.

Option C is incorrect because while publishing a new Lambda version is a step in the right direction, CloudFormation alone does not configure the traffic-shifting and automatic rollback mechanisms needed - AWS SAM or CodeDeploy integration is required to orchestrate this properly.

Option D is incorrect because CodeBuild with sample event payloads is a testing/validation approach, not a deployment strategy - it does not provide traffic shifting, canary deployments, or automatic rollback capabilities.

Memory Tip

Think "SAM = Safe Automated Migration" - AWS SAM templates support DeploymentPreference configurations (Canary, Linear, AllAtOnce) with built-in CloudWatch alarm triggers for automatic rollback, making it the go-to solution for safe serverless deployments.

No community discussion yet for this question.