Which CI/CD solution provisions multi-account test infrastructure and runs integration tests?
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?
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests matching each AWS tool to its exact role — StackSets for multi-account infrastructure, CodeBuild for running tests — and the trap is confusing single-stack change sets with multi-account StackSets.
This DVA-C02 question tests deploying EC2 and RDS test infrastructure across multiple AWS accounts using AWS CodePipeline with CloudFormation StackSets, then running integration tests with AWS CodeBuild. The community unanimously agrees the answer is B, as StackSets handles multi-account provisioning and CodeBuild is the managed service purpose-built for executing tests.
Option C is the most tempting wrong answer because change sets are a well-known CloudFormation deployment mechanism, but change sets only preview and apply changes to a single stack in one account, so they cannot provision infrastructure across different AWS accounts.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
AWS CodePipeline is the continuous delivery orchestrator that can chain a CloudFormation deployment stage and a test stage together. CloudFormation StackSets is specifically designed to provision stacks across multiple AWS accounts and Regions from a single administrator account, which directly addresses the requirement to deploy EC2 and RDS test infrastructure in each customer's account. AWS CodeBuild is a fully managed build and test service that can execute integration test suites against the provisioned infrastructure. This combination requires the least administrative effort because all three services are fully managed and integrate natively, as community comment [1] notes: StackSets handles multi-account deployment without complex configurations, and CodePipeline plus CodeBuild provide a low-maintenance CI/CD flow.Why the Other Options Are Wrong
Option A fails because Amazon CodeGuru is a code review and application profiling service, not a test execution engine, so it cannot run integration tests. Option C uses CloudFormation change sets, which only stage changes for a single stack in one account and cannot deploy across multiple AWS accounts; additionally, a CloudFormation custom resource is an awkward, high-effort way to trigger tests. Option D is wrong because AWS SAM targets serverless applications, while the test infrastructure here is EC2 and RDS, and AWS CodeDeploy deploys application code to compute platforms rather than running test suites. Comment [3] reinforces that B is the intended answer over the alternatives.Community Comment Notes
Community consensus is unanimous (100% of votes for B), with the most-liked comment [1] clearly articulating the reasoning: StackSets removes the complexity of multi-account provisioning, and the CodePipeline/CodeBuild pairing is a seamless, fully managed CI/CD solution. Comment [2] independently confirms in Spanish that StackSets facilitates deployment across multiple accounts and that CodeBuild fits perfectly for running integration tests with minimal administrative effort. Comment [3] simply validates B over A, showing no credible support exists for any other option.Official Reference
Exam Strategy
On DVA-C02, map each service to its single core purpose: CodePipeline orchestrates delivery, StackSets deploys to multiple accounts, CodeBuild runs builds and tests, and CodeDeploy releases application code. When a question mentions deploying to multiple AWS accounts, immediately look for StackSets, and when it mentions running tests, look for CodeBuild. Watch for change sets as a distractor — they only preview or apply changes to one stack in one account.
Related Analysis
Practice All DVA-C02 Questions
Access 100 questions with complete answers and detailed explanations.
View Full DVA-C02 Practice Test →