Which of the following triggers redeployments when the image tag updates?

• A. configChange trigger
• B. routeChange trigger
• C. imageChange trigger
• D. secretChange trigger

Answer: (C)

Redeployments triggered by an image tag update are driven by an imageChange trigger. When a DeploymentConfig includes an imageChange trigger linked to an ImageStreamTag, updates to the image tag—such as pushing a new build to that tag—signal OpenShift to start a new rollout using the updated image. The deployment will pull the latest image and replace existing pods, ensuring the running application reflects the new image without manual intervention.

In contrast, other triggers respond to different events: a configChange trigger redeploys when the pod template in the DeploymentConfig changes (for example, environment variables or resource requests/limits), not simply when the image changes. A routeChange trigger would respond to changes in the route resource itself, which isn’t about the container image. A secretChange trigger would redeploy if a referenced secret changes, which is useful for secrets but not the usual mechanism for updating container images.