What is the role of a Webhook trigger in a BuildConfig?

• A. You must manually trigger builds after every change.
• B. Git pushes can trigger a new build automatically via a webhook.
• C. A webhook triggers only when a new tag is created.
• D. A webhook automatically creates a Route.

Answer: (B)

Webhook triggers in a BuildConfig let builds start automatically when there are changes in your source repository. When you enable a webhook trigger and configure a repository, OpenShift provides a URL that your Git service can notify whenever you push changes. A push (or other configured event) sent to that URL kicks off a new build for the BuildConfig without manual intervention, enabling a smooth, automated CI/CD flow. It’s not about creating Routes, and it isn’t limited to new tags—the trigger responds to the events you configure (often a Git push). Manual triggering is possible if you don’t use a webhook, but the webhook’s role is to automate builds in response to repository events.