The city’s prebuilt CD path already builds, pushes, and rolls container images into Kubernetes. How should a new Meraki webhook consumer integrate into that environment?
Select an answer to reveal the explanation.
Short Explanation
The prebuilt conveyor already moves sealed crates—images—into the cluster. Hand-carrying loose source onto each node is not “integrate into the CD.”
Full Explanation
Integrating into a prebuilt Docker and Kubernetes CD environment means the pipeline builds a container image, pushes it to the registry the cluster already trusts, and rolls that tag. Copying source onto each node or installing Python on workers is not that integration. Authoring a new Dockerfile from scratch is a related but separate 4.4 skill; here the artifact contract is the image the existing path deploys.