Which concept lets you tag and track a specific image version within the cluster's image catalog for use in builds and deployments?

Which concept lets you tag and track a specific image version within the cluster's image catalog for use in builds and deployments?

• A. Route
• B. ConfigMap
• C. ImageStreamTag
• D. Deployment

Answer: (C)

Tagging and tracking a specific image version inside the cluster’s image catalog is handled by an ImageStreamTag. In OpenShift, an ImageStream represents a collection of image references from registries, and an ImageStreamTag designates a precise version of that image within the stream. This lets builds and deployments reference a stable image digest or version, so you get reproducible results even as new images are pushed to the registry. You can update or pin to newer versions by updating the tag, enabling controlled rollout of image changes. Other options don’t fit because a Route exposes services to the outside world, a ConfigMap stores configuration data for pods, and a Deployment runs and manages application pods but does not provide the mechanism to track or pin a specific image version inside the cluster’s image catalog.

Tagging and tracking a specific image version inside the cluster’s image catalog is handled by an ImageStreamTag. In OpenShift, an ImageStream represents a collection of image references from registries, and an ImageStreamTag designates a precise version of that image within the stream. This lets builds and deployments reference a stable image digest or version, so you get reproducible results even as new images are pushed to the registry. You can update or pin to newer versions by updating the tag, enabling controlled rollout of image changes.

Other options don’t fit because a Route exposes services to the outside world, a ConfigMap stores configuration data for pods, and a Deployment runs and manages application pods but does not provide the mechanism to track or pin a specific image version inside the cluster’s image catalog.