DATABRICKS-MLP Question 21

Community Discussion

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

• Chose A0

  ,B - Correct answer s : A, B — A custom call like `mlflow.log_metric("projected_cost_savings", value)` can be added inside the same active run that `autolog()` is populating, without disabling autologging.; Autologging and manual `log_metric` calls write to the same active run object, so both the automatic and the custom metrics appear together on one run's page. A . Autologging populates whatever run is active without preventing additional manual logging calls, so a custom metric like cost savings can be logged into that same run alongside the autologged values. B . Both autologging and manual calls target the currently active MLflow run, so a reviewer opening that run's page sees the automatically captured metrics together with any manually logged custom ones. C . Autologging does not lock the run against further calls; it simply adds its own logging calls under the hood while leaving the run fully open to any additional manual logging the script performs. D . There is no naming convention required for custom metrics to coexist with autologged ones; any metric name not already used by the autologging integration logs normally. E . Autologging still requires an active run, either one explicitly started with `start_run()` or one it creates automatically if none is active; it does not remove the need for run management. F . If a custom metric name collides with one autologging already logs, the later call simply overwrites the earlier value for that metric name, which is not guaranteed to favor either source and can be surprising rather than a documented precedence rule.