Successful builds of the city’s microservice produce container images that later environments pull for deployment. What are those images in pipeline terms?
Select an answer to reveal the explanation.
Short Explanation
Artifacts are the leftovers that matter—the image or package the build just made, parked where deploy stages can grab them. Chat logs and sticky-note screenshots aren’t deployable. Think ‘jar on the shelf,’ not ‘conversation in the hallway.’
Full Explanation
CI/CD artifacts are the versioned outputs of successful builds—commonly container images or packages—stored in registries or artifact repositories for deployment. Downstream stages consume those artifacts rather than rebuilding ad hoc from developer workstations. Informal logs, screenshots, or billing documents are not runtime deployment artifacts.