Databricks Certified Machine Learning Associate Practice Mode

Community Discussion

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

• Chose A0

  - Correct answer : A — Include the timestamp column in `primary_keys` with the entity key, and pass that column to `timeseries_columns` so lookups respect point-in-time correctness. A . Correct. Time series feature tables require the time column to be part of the primary key and declared through `timeseries_columns`, which is what enables point-in-time lookups during training-set creation. B . Incorrect. Treating the timestamp as a plain schema column gives it no special meaning; `create_training_set` has no mechanism to infer time ordering from insertion order alone. C . Incorrect. Omitting the timestamp key removes any way to look up feature values as of a specific point in time, and `merge` mode write behavior does not substitute for that. D . Incorrect. `tags` store descriptive key-value metadata for humans and catalog search; they are not read by the training-set or lookup logic that enforces point-in-time correctness.