A team has written custom Python inference logic that is not covered by a built-in MLflow flavor. They want to deploy it with Databricks Model Serving. Which preparation path is correct?
Answer & explanation
Correct answer: C
WHY C: Databricks custom model serving expects an MLflow-packaged model, often via pyfunc for arbitrary Python logic, followed by registration and endpoint creation. WHY NOT A: A raw notebook is not the required serving artifact. WHY NOT B: Dependencies and model packaging must be captured properly. WHY NOT D: Delta tables are not model artifacts. WHY NOT E: CSV files do not define deployable MLflow model logic.