SnowPro Advanced: MLOps Engineer free question 10 / 10 · Domain 5: Governance, Security, and Monitoring
The model CHURN has a model version monitor on version V3. The team logged V4 in the Model Registry, made it the default version and pointed the scoring job at it. A week later the V3 monitor dashboard shows only old data, and nothing covers V4. What does the ML Observability documentation say?
- The monitor follows the default version, so it covers V4 after the next refresh
- ALTER MODEL MONITOR can add V4, so that one monitor covers both of the versions
- One monitor per model is the rule, so V4 can only be watched after V3 is dropped
- Create a new monitor for V4; one monitor watches exactly one model version
Show the answer and explanation
Answer: D
Why this is correct
The section "ML Observability workflow" says you must explicitly create a model monitor object for each model version you want to monitor. Each model version can have exactly one monitor, and each monitor can monitor exactly one model version; they cannot be shared. Each monitor encapsulates the model version to monitor, the table that stores the monitor logs, the aggregation window and an optional baseline table. The V3 monitor therefore keeps watching V3, which no longer receives new inference rows, and V4 needs its own CREATE MODEL MONITOR with VERSION = 'V4' over the table where the scoring job now writes its results.
Why the other options are wrong
"The monitor follows the default version, so it covers V4 after the next refresh" … The page says you must explicitly create a model monitor object for each model version you want to monitor. A monitor encapsulates the model version it watches, so it does not move to a new default version.
"ALTER MODEL MONITOR can add V4, so that one monitor covers both of the versions" … Each monitor can monitor exactly one model version, and monitors cannot be shared. One monitor object therefore cannot cover V3 and V4 together; each version that needs watching gets its own monitor.
"One monitor per model is the rule, so V4 can only be watched after V3 is dropped" … The rule is per model version, not per model: each model version can have exactly one monitor. V3 and V4 can each have their own monitor at the same time.
A new version needs a new monitor
Creating the monitor belongs in the same release step that logs and promotes the version, so that no version runs unwatched. Keeping the V3 monitor for a while also lets the dashboard compare the two versions with the Compare model selector.