The city's shared DevOps account still runs always-on EC2 build VMs that execute containerized test suites for permitting, GIS, and public-health pipelines, sitting idle between merges. Which container-service modernization should architects select for the test runners?
Select an answer to reveal the explanation.
Short Explanation
Test runners are visiting inspectors, not tenants with a year lease. Park the suites on Fargate, run them when a merge lands, and stop paying for idle build VMs. Bigger always-on boxes just raise the rent.
Full Explanation
Tooling workloads such as CI test runners are valid Task 4.4 container-service candidates. AWS Fargate runs ephemeral test containers without a fleet of long-lived build VMs, improving cost and patching for a multi-team municipal DevOps account. Larger idle EC2, laptop-only tests, and Athena as a test runtime miss that selection.