Databricks-Machine-Learning-Professional Exam Dumps : Databricks Certified Machine Learning Professional

The MLflow Model Registry provides a centralized model store, set of APIs, and UI, to collaboratively manage the full lifecycle of an MLflow Model. It provides model lineage, model versioning, model aliasing, model tagging, and annotations. The Model Registry defines four model stages that represent the lifecycle of a model: None, Staging, Production, and Archived. Each model stage has a different meaning and purpose:

• None: This is the default stage when a new model version is registered. It indicates that the model version is not ready for any downstream use cases and needs further development or testing.
• Staging: This stage indicates that the model version is ready for testing or validation in a pre-production environment. It can be used for quality assurance, user acceptance testing, or performance evaluation before moving to production.
• Production: This stage indicates that the model version is ready for deployment in a production environment. It can be used for serving predictions, scoring data, or supporting business decisions. Only one model version per registered model can be in the production stage at a time.
• Archived: This stage indicates that the model version is no longer in active use and can be safely deleted or moved to a long-term storage. It can be used for historical or audit purposes, or for restoring a previous model version if needed.

References:

• MLflow Model Registry Documentation, p. 1-2
• Introducing the MLflow Model Registry - Databricks, p. 1-2
• Manage MLflow Models — Databricks Documentation, p. 1-2

Data type tests and checks are particularly important for streaming deployments because of the following reasons:

• Because the streaming deployment is always on, all types of data must be handled without producing an error. Streaming data may come from various sources and have different formats, schemas, or quality. If the streaming deployment cannot handle the data properly, it may result in errors, failures, or inaccurate outputs. Therefore, data type tests and checks can help validate the data and ensure the streaming deployment can process it correctly.
• Because the streaming deployment is always on, there is no practitioner to debug poor model performance. Streaming data may also change over time, affecting the model performance and accuracy. If the streaming deployment does not have a mechanism to monitor and evaluate the model performance, it may not be able to detect or correct any issues. Therefore, data type tests and checks can help identify any data drift or anomalies that may impact the model performance and trigger alerts or actions.
• Because the streaming deployment is always on, there is a need to confirm that the deployment can autoscale. Streaming data may have varying volumes and velocities, requiring the streaming deployment to scale up or down accordingly. If the streaming deployment does not have a way to adjust the resources and throughput based on the data demand, it may result in bottlenecks, delays, or inefficiencies. Therefore, data type tests and checks can help measure the data load and ensure the streaming deployment can autoscale effectively. References: Streaming Data, Data Validation, Model Monitoring, Autoscaling

Concept drift in machine learning and data mining refers to the change in the relationships between input and output data in the underlying problem over time. In other domains, this change maybe called “covariate shift,” “dataset shift,” or “nonstationarity.” Concept drift can affect the performance and accuracy of predictive models that assume a static relationship between input and output variables. Concept drift can be caused by various factors, such as changes in user behavior, environmental conditions, market trends, etc. Concept drift can be detected and handled by various methods, such as periodic retraining, online learning, ensemble methods, etc References:

• Concept drift - Wikipedia
• A Gentle Introduction to Concept Drift in Machine Learning
• Model Drift & Machine Learning: Concept Drift, Feature Drift, Etc.
• Data Drift vs. Concept Drift: What Is the Difference?