Which command removes the config trigger from the deployment config mysql?

• A. oc set trigger dc/mysql --from-config --remove
• B. oc set triggers dc/mysql --from-config --remove
• C. oc set triggers dc/mysql --from-config
• D. oc set triggers dc/mysql --remove --from-config

Answer: (B)

Managing deployment config triggers in OpenShift is about controlling when a new deployment happens automatically. A config trigger fires when a referenced configuration (like a ConfigMap or Secret) changes. To remove that specific trigger from a deployment config named mysql, you use the command with the plural subcommand to modify triggers, specify the trigger type with a flag, and indicate removal.

The best command is: oc set triggers dc/mysql --from-config --remove. It explicitly targets the deployment config mysql, identifies the trigger as coming from a config change, and performs the removal. Using the singular form is not valid for this operation, and omitting the removal flag would not delete the trigger (it would modify or add a trigger instead). Including both --from-config and --remove ensures only the config-trigger is removed while other triggers, like image-change triggers, remain unaffected.