DATABRICKS-MLP Question 63

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose A0

  ,B,C - Correct answer s : A, B, C — Confirm the served entity references the model by alias (such as `@Champion`) rather than a version number hardcoded to whatever was true when the YAML was written.; Confirm `catalog_name` and `schema_name` on the `registered_models` resource resolve to the intended production namespace once the prod target's variables are applied.; Confirm `grants` on the production `registered_models` resource are scoped to the specific principals that need access, not granted broadly by default. A . Checking that the served entity tracks an alias rather than a version frozen at authoring time confirms the endpoint will automatically follow future promotions instead of silently going stale. B . Verifying that catalog_name and schema_name resolve correctly once target variables are applied catches a misconfigured or unresolved variable before it registers the model into the wrong namespace in production. C . Verifying grants are scoped to only the principals that actually need access is exactly the least-privilege check a reviewer should make before a production model resource goes live. D . A populated comment field has no effect on MLflow run logging; comment is purely descriptive metadata, so this is not a real risk worth checking for. E . Traffic does not route itself automatically without configuration; traffic_config's routes are what define how requests are split across served entities, so omitting it entirely is not a valid or harmless state to leave unchecked. F . Hardcoding entity_version to the current highest version freezes the endpoint on that version and requires a manual redeploy for every future promotion, which is the opposite of what a reviewer should confirm is in place.