DVA-C02 · Question #510
A company offers a business-to-business software service that runs on dedicated infrastructure deployed in each customer's AWS account. Before a feature release, the company needs to run integration…
The correct answer is C. Use AWS CodePipeline with AWS CloudFormation change sets to deploy the infrastructure. Use. Option C is correct because AWS CodePipeline provides the continuous delivery orchestration, and CloudFormation change sets allow the pipeline to preview, then execute infrastructure provisioning-creating and tearing down EC2 and RDS resources per test run-using standard…
Question
A company offers a business-to-business software service that runs on dedicated infrastructure deployed in each customer's AWS account. Before a feature release, the company needs to run integration tests on real AWS test infrastructure. The test infrastructure consists of Amazon EC2 instances and an Amazon RDS database. A developer must set up a continuous delivery process that will provision the test infrastructure across the different AWS accounts. The developer then must run the integration tests. Which solution will meet these requirements with the LEAST administrative effort?
Options
- AUse AWS CodeDeploy with AWS CloudFormation StackSets to deploy the infrastructure. Use
- BUse AWS CodePipeline with AWS CloudFormation StackSets to deploy the infrastructure. Use
- CUse AWS CodePipeline with AWS CloudFormation change sets to deploy the infrastructure. Use
- DUse AWS Serverless Application Model (AWS SAM) templates with AWS CloudFormation
How the community answered
(37 responses)- A8% (3)
- B14% (5)
- C76% (28)
- D3% (1)
Explanation
Option C is correct because AWS CodePipeline provides the continuous delivery orchestration, and CloudFormation change sets allow the pipeline to preview, then execute infrastructure provisioning-creating and tearing down EC2 and RDS resources per test run-using standard cross-account IAM role assumptions with minimal setup.
Why A is wrong: CodeDeploy deploys application code to existing infrastructure; it cannot provision EC2 instances or RDS databases, so it fails the provisioning requirement entirely.
Why B is wrong: CloudFormation StackSets are designed for maintaining persistent stacks across many accounts simultaneously (e.g., org-wide security baselines). They require additional administrative setup (Organizations integration or self-managed permissions in every target account), adding overhead beyond what a test pipeline needs.
Why D is wrong: AWS SAM templates are purpose-built for serverless infrastructure (Lambda, API Gateway, DynamoDB). They are not designed to provision EC2 instances and RDS databases, making SAM the wrong tool here.
Memory tip: Think "Change sets are for changing a stack in a pipeline; StackSets are for setting the same stack across many accounts permanently." When a question asks for least admin effort on temporary test infra in a pipeline, change sets + cross-account roles beat StackSets' organizational overhead.
Topics
Community Discussion
No community discussion yet for this question.