A civic cloud team must repeatedly provision networks and instances with declarative templates, schedule containers across a cluster at scale, and run classic build jobs in a CI server. Which tool-to-job mapping is correct?
Select an answer to reveal the explanation.
Short Explanation
Match the wrench to the bolt: Terraform writes the cloud wiring as code, Kubernetes places containers on the cluster, and Jenkins (or similar) runs the classic build jobs. Mixing those jobs across the wrong tools is a common exam trap. Keep each tool’s purpose straight and the mapping clicks.
Full Explanation
Terraform (or equivalent) provides declarative infrastructure as code for networks and instances; Kubernetes schedules and orchestrates containers at cluster scale; Jenkins is a classic CI server for build and test jobs. Cloud+ Domain 5 expects candidates to match DevOps tools to their primary jobs rather than conflating IaC, orchestration, and CI responsibilities.