A batch inference job uses a model packaged with two feature lookups: account_creation_date and num_lifetime_purchases. The scoring DataFrame provides account_creation_date explicitly for a what-if analysis. How does Databricks handle this during score_batch?
Answer & explanation
Correct answer: C
WHY C: Databricks supports custom feature values during score_batch; supplied columns override lookup for those features, while missing packaged features are still retrieved. WHY NOT A: Overlapping supplied feature columns are not ignored. WHY NOT B: Partial overrides are supported. WHY NOT D: One scoring request does not rewrite model metadata. WHY NOT E: The provided values are used for inference, not merely logged as tags.