Databricks ML Data Scientist Databricks-Machine-Learning-Professional New Questions

Jensen-Shannon (JS) distance is a symmetric measure of the distance between two probability distributions. It is based on the Kullback-Leibler (KL) divergence, but unlike KL, it does not depend on which distribution is considered the reference and which is considered the comparison. JS distance is also bounded between 0 and 1, which makes it easier to interpret and compare across different features.

Kolmogorov-Smirnov (KS) test is a non-parametric test that compares the cumulative distribution functions (CDFs) of two samples. It calculates the maximum difference between the CDFs and compares it to a critical value to determine if the samples are from the same distribution. KS test is sensitive to the shape, location, and scale of the distributions, but it can also be too sensitive for large datasets, where small changes can result in significant differences.

JS distance is more robust than KS test for numeric feature drift detection because it can handle large datasets without being too sensitive to minor fluctuations. It can also capture changes in the shape and spread of the distributions, not just the location. JS distance does not require any manual threshold or cutoff determinations, unlike KS test, which requires choosing a significance level and a critical value. JS distance can also be generalized to multivariate cases, while KS test is limited to univariate cases. References:

• Which test is the best? We compared 5 methods to detect data drift on large datasets
• The Jensen-Shannon Divergence: A Measure of Distance Between Probability Distributions
• Kullback–Leibler vs Kolmogorov-Smirnov distance

The Databricks REST APIs allow users to programmatically access Databricks features and services, such as clusters, jobs, workspaces, libraries, secrets, and more. The Jobs API enables users to create, edit, delete, run, and list jobs, as well as manage job runs. Users can use the Jobs API to programmatically create a new Databricks job whose schedule depends on the result of some automated tests in a machine learning pipeline. For example, users can use the create endpoint to create a new job with a cron_schedule parameter that specifies the cron expression for the job schedule. Users can also use the run_now endpoint to run an existing job with a run_name parameter that specifies the name of the run. Users can use the runs/get endpoint to get the run result state of a job run, and use conditional logic to trigger another job run based on the result. Users can also use the runs/list endpoint to list all the runs of a job, and use the runs/cancel endpoint to cancel a job run if needed. References:

• Databricks REST API — Databricks Documentation, p. 1
• Jobs API — Databricks Documentation, p. 1-2
• Create and run Databricks Jobs | Databricks on AWS, Create and run jobs using the CLI, API, or notebooks, p. 1

The context parameter is an instance of mlflow.pyfunc.model.ModelContext, which is a wrapper around the model metadata and artifacts. The context parameter allows the user to provide the model access to objects like preprocessing models or custom configuration files that are needed for the model inference. For example, the context parameter can be used to load a scikit-learn preprocessing model that was logged as an artifact with the MLflow model, and then apply it to the input data before passing it to the main model. The context parameter can also be used to access the model signature and the input example, if they were logged with the model. The context parameter is passed to the load_context and predict methods of the PythonModel class, which is asubclass of mlflow.pyfunc.PythonModel that defines the custom logic for loading and scoring the model. References:

• mlflow.pyfunc Documentation, p. 1-2
• mlflow.pyfunc.model Documentation, p. 1-2
• Understanding PyFunc in MLflow, Part 2: Pyfunc Components, p. 1-2
• python - How to load model from mlflow with custom predict without local file?, p. 1-2