Rollback to version 2 of deployment config php.

Prepare for the Red Hat Openshift Developer EX288 Exam. Study with comprehensive quizzes and flashcards. Each question includes hints and explanations to enhance your understanding. Ace your exam with confidence!

Multiple Choice

Rollback to version 2 of deployment config php.

Explanation:
Rolling back a deploymentConfig to a specific previous revision uses the oc rollback command with the resource identified and the target version specified. The correct form is to rollback the deploymentConfig named php to version 2 by calling oc rollback dc/php --to-version=2. This uses the deploymentConfig resource type (dc) and the integer revision number, which OpenShift treats as the exact rollback point. Version numbers are integers representing specific revisions, so a version like 2.0 isn’t valid. Specifying the resource as just php omits the resource type, making the command ambiguous for OpenShift to operate on. And rolling back to version 1 would revert to a different revision than requested.

Rolling back a deploymentConfig to a specific previous revision uses the oc rollback command with the resource identified and the target version specified. The correct form is to rollback the deploymentConfig named php to version 2 by calling oc rollback dc/php --to-version=2. This uses the deploymentConfig resource type (dc) and the integer revision number, which OpenShift treats as the exact rollback point.

Version numbers are integers representing specific revisions, so a version like 2.0 isn’t valid. Specifying the resource as just php omits the resource type, making the command ambiguous for OpenShift to operate on. And rolling back to version 1 would revert to a different revision than requested.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy