Start rolling out a new change to a deployment config named php.

• A. oc rollout latest dc/php
• B. oc rollout restart dc/php
• C. oc rollout history dc/php
• D. oc scale dc/php

Answer: (A)

Triggering a new rollout using the latest changes defined in the DeploymentConfig is the mechanism to apply updates in a controlled, rolling fashion. The command that starts this process tells OpenShift to create a new replication controller based on the most recent state of the php DeploymentConfig and begin replacing old pods with the updated ones. This ensures the new configuration (like a new image) is deployed gradually with minimal downtime.

The other options don’t specifically start a rollout from the updated config: restarting would recreate pods using the current template, not necessarily using the latest changes; history just shows past rollouts; scaling changes the number of replicas.