DVA-C02 · Question #328
A developer works for a company that only has a single pre-production AWS account with an AWS CloudFormation AWS Serverless Application Model (AWS SAM) stack. The developer made changes to an existing
The correct answer is C. Use the AWS SAM CLI to package and deploy the SAM application to a new AWS account. https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/using-sam-cli-
Question
A developer works for a company that only has a single pre-production AWS account with an AWS CloudFormation AWS Serverless Application Model (AWS SAM) stack. The developer made changes to an existing AWS Lambda function specified in the AWS SAM template and additional Amazon Simple Notification service (Amazon SNS) topics. The developer wants to do a one-time deploy of the changes to test if the changes are working. The developer does not want to impact the existing pre-production application that is currently being used by other team members as part of the release pipeline. Which solution will meet these requirements?
Options
- AUse the AWS SAM CLI to package and deploy the SAM application to the pre-production AWS
- BUse the AWS SAM CLI to package and create a change set against the pre-production AWS
- CUse the AWS SAM CLI to package and deploy the SAM application to a new AWS account
- DUpdate the CloudFormation stack in the pre-production account. Add a separate stage that points
How the community answered
(39 responses)- A21% (8)
- B10% (4)
- C64% (25)
- D5% (2)
Explanation
https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/using-sam-cli-
Community Discussion
No community discussion yet for this question.