Before any deploy stage for a municipal records API, unit tests and lint must run with cached dependencies. Which service should provide that CI build/test compute in the pipeline?
Select an answer to reveal the explanation.
Short Explanation
CodeBuild is the workshop bench in the pipeline: run lint and unit tests with cached deps before anyone ships to the city. S3 sites and CloudFront purges are not your test runners.
Full Explanation
Before deploy stages for a municipal records API, the pipeline needs CI compute that runs unit tests and lint with dependency caching. AWS CodeBuild is that managed build service: it executes buildspec commands, can cache dependency folders or layered images, and fails the pipeline before any civic environment is mutated. Placing CodeBuild ahead of deploy stages enforces "tests first" for records that citizens and auditors rely on, and caching keeps weekday merge builds from repeatedly downloading the same toolchains.
Amazon S3 static website hosting is content hosting, not a unit-test runner. CloudFront invalidation clears edge caches; it does not execute pytest or linters. Route 53 health checks probe endpoints for availability; they do not run the application's automated test suite as CI compute inside a pipeline.
Exam caveat: CodeBuild = build/test compute; CodePipeline = orchestration; CodeDeploy = delivery. Mixing those responsibilities is a common distractor pattern on DVA-C02.
Operational check: confirm the pipeline's first post-source action is CodeBuild, that dependency caching reduces cold build times, that failing lint or unit tests block deploy stages, and that only green builds reach the municipal records test environment.