A machine learning engineer is attempting to create a webhook that will trigger a Databricks Job job_id when a model version for model model transitions into any MLflow Model Registry stage. They…

Question

Exhibit

Options

• A"MODEL_VERSION_CREATED"
• B"MODEL_VERSION_TRANSITIONED_TO_PRODUCTION"
• C"MODEL_VERSION_TRANSITIONED_TO_STAGING"
• D"MODEL_VERSION_TRANSITIONED_STAGE"
• E"MODEL_VERSION_TRANSITIONED_TO_STAGING",

• A
  6% (4)
• B
  2% (1)
• C
  77% (50)
• D
  3% (2)
• E
  12% (8)

Explanation

Option C, "MODEL_VERSION_TRANSITIONED_TO_STAGING", is the valid Databricks MLflow Model Registry webhook event that fires when a model version transitions to the Staging stage - which is the target stage implied by the code context. Option D, "MODEL_VERSION_TRANSITIONED_STAGE", is the most tempting distractor because it sounds like a generic "any stage" trigger, but it is not an actual valid event name in the Databricks webhook API, making it non-functional. Option B, "MODEL_VERSION_TRANSITIONED_TO_PRODUCTION", is a real event but is stage-specific to Production, not Staging. Option A, "MODEL_VERSION_CREATED", fires when a new model version is registered, not when it transitions between stages at all. Option E is syntactically identical to C but includes a trailing comma, which would cause a syntax error or be invalid in the event string context.

Memory tip: Think of the Databricks webhook events as "TO_STAGE" - the valid stage-specific events follow the pattern MODEL_VERSION_TRANSITIONED_TO_STAGING and MODEL_VERSION_TRANSITIONED_TO_PRODUCTION. If you see a version without the TO_ (like option D), it's a trap - that format isn't in the real API.

No community discussion yet for this question.