cert
cert-1
cert-2

Pass Databricks Certified Machine Learning Professional Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
Certified Machine Learning Professional Exam - Verified By Experts
Certified Machine Learning Professional Premium File

Certified Machine Learning Professional Premium File

$69.99
$76.99
  • Premium File 216 Questions & Answers. Last Update: Nov 12, 2026

Whats Included:

  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
 
$76.99
$69.99
accept 12 downloads in the last 7 days
block-screenshots
Databricks Certified Machine Learning Professional Practice Test 13

Question 120

In an enterprise ML workflow, the reported issue is: A regulated analytics team uploads full customer identifiers inside MLflow model artifacts during troubleshooting. What technical distinction is essential to this investigation?

  1. Experiment tracking must minimize sensitive data and enforce artifact permissions rather than treating all model logs as harmless.
  2. Custom MLflow model packaging must include declared compatible dependencies for the independent serving environment.
  3. A resumed search needs stable experiment and parent-child provenance across partial reruns to support comparison.
  4. Request-scoped feature retrieval and thread-safe state are needed when the custom model serves multiple callers.

Explanation

Correct Answer

A:

The technical constraint is specific to the reported failure. Experiment tracking must minimize sensitive data and enforce artifact permissions rather than treating all model logs as harmless. To test it, review artifact payload fields, access controls and permitted data classifications before reuse.

Incorrect Answers

B:

That underlying principle is directed at a different advanced mlflow usage situation: A team logs a custom Python model that imports a package installed only in the author's notebook, and the serving endpoint fails when loading the artifact. The current incident instead turns on experiment tracking must minimize sensitive data and enforce artifact permissions rather than treating all model logs as harmless.

C:

That underlying principle is directed at a different advanced mlflow usage situation: A research team restarts a long hyperparameter sweep and merges all newly executed trials into a new experiment without connecting them to the original parent. The current incident instead turns on experiment tracking must minimize sensitive data and enforce artifact permissions rather than treating all model logs as harmless.

D:

That underlying principle is directed at a different advanced mlflow usage situation: A fraud PyFunc uses a global mutable feature cache initialized by the first request and mixes data between subsequent users. The current incident instead turns on experiment tracking must minimize sensitive data and enforce artifact permissions rather than treating all model logs as harmless.

Question 121

In an enterprise ML workflow, the reported issue is: A model's inference table records output probabilities but omits ground-truth labels, yet reviewers expect immediate precision and recall metrics. Which change addresses the real cause without undermining other requirements?

  1. Add an approved later label join and maintain separate unlabeled input-drift metrics until labels arrive.
  2. Configure a supported time-series profile with the appropriate timestamp and daily granularity.
  3. Separate versioned baseline storage from current data and block unintended updates.
  4. Add an appropriately sustained alert condition or window aggregate instead of a one-minute peak trigger.

Explanation

Correct Answer

A:

This corrects the relevant failure boundary instead of merely hiding the symptom. Add an approved later label join and maintain separate unlabeled input-drift metrics until labels arrive. The issue matters because a dashboard displays unsupported performance claims based only on predicted probabilities.

Incorrect Answers

B:

That corrective action is directed at a different drift detection and lakehouse monitoring situation: A fleet sensor table records measurement timestamps and analysts need daily drift trends; a snapshot-only profile erases the time dimension. The relevant corrective action here is add an approved later label join and maintain separate unlabeled input-drift metrics until labels arrive.

C:

That corrective action is directed at a different drift detection and lakehouse monitoring situation: A baseline table is overwritten every night with the current day's data before a drift calculation, making the comparison always look unchanged. The relevant corrective action here is add an approved later label join and maintain separate unlabeled input-drift metrics until labels arrive.

D:

That corrective action is directed at a different drift detection and lakehouse monitoring situation: A monitor alerts whenever a ratio exceeds 0.3 for a single minute, although normal traffic produces brief spikes and operations require ten-minute persistence. The relevant corrective action here is add an approved later label join and maintain separate unlabeled input-drift metrics until labels arrive.

Question 122

The engineering team encounters the following issue: A team records experiments but has no controlled path from a selected registered model to scheduled scoring jobs. Which experiment most directly demonstrates a successful fix?

  1. A clean production-like environment loads the promoted artifact and matches approved prediction fixtures.
  2. The same signed release revision and dependencies run in test and production with matching fixture output.
  3. An integration fixture confirms the promoted job reads the intended schema before traffic is moved.
  4. A deployment record traces production predictions to the approved model version and generating run.

Explanation

Correct Answer

D:

This verification measures the required result rather than just process liveness. A deployment record traces production predictions to the approved model version and generating run. It confirms whether the targeted action succeeded: bind training outputs to registered immutable versions and promote them through governed jobs or serving endpoints.

Incorrect Answers

A:

That acceptance test is directed at a different model lifecycle management situation: A model is promoted to production with its code unchanged but a different unpinned training library version is installed, altering prediction preprocessing. Here the actual success criterion is a deployment record traces production predictions to the approved model version and generating run.

B:

That acceptance test is directed at a different model lifecycle management situation: A regulated company changes deployed Python notebook code directly in production to correct a model transform while its test environment runs a different untracked revision. Here the actual success criterion is a deployment record traces production predictions to the approved model version and generating run.

C:

That acceptance test is directed at a different model lifecycle management situation: A customer segmentation project promotes a scoring job but omits a database migration required by its new feature schema. Here the actual success criterion is a deployment record traces production predictions to the approved model version and generating run.

Question 123

Consider the following fictional Databricks production case: An endpoint update request succeeds but the newly configured model version is still loading; monitoring marks the release complete immediately. Which implementation is most appropriate for the stated incident?

  1. Prepare a complete tested green environment and switch traffic after approval while retaining blue for rollback.
  2. Gate release completion on ready healthy serving entities and validated predictions.
  3. Use a supported routing design or keep the protected region on the approved model until scoped rollout is available.
  4. Set a statistically and operationally adequate rollout observation period with strict safety abort thresholds.

Explanation

Correct Answer

B:

This corrects the relevant failure boundary instead of merely hiding the symptom. Gate release completion on ready healthy serving entities and validated predictions. The issue matters because production traffic reaches a model not yet loaded or compatible with runtime dependencies.

Incorrect Answers

A:

That corrective action is directed at a different deployment strategies situation: A bank requires an immediate rollback after deployment and wants the prior serving environment intact until the new environment passes tests. The relevant corrective action here is gate release completion on ready healthy serving entities and validated predictions.

C:

That corrective action is directed at a different deployment strategies situation: A model release requires all clients from a restricted region to keep the old version, but a simple percentage split sends some of those clients to the candidate. The relevant corrective action here is gate release completion on ready healthy serving entities and validated predictions.

D:

That corrective action is directed at a different deployment strategies situation: A candidate fraud model has near-identical average error to the champion, but an organization wants to compare rare fraudulent transactions during a brief canary. The relevant corrective action here is gate release completion on ready healthy serving entities and validated predictions.

Question 124

In an enterprise ML workflow, the reported issue is: An insurer already stores its risk features as a large Spark DataFrame but exports them into Python lists before every vector transformation and repeatedly hits out-of-memory errors. How should the engineer validate the correction?

  1. Two sample sentences produce the expected token-array column from a direct transform.
  2. The tracked run records each parameter map, validation metric and final chosen model before untouched test evaluation.
  3. Model accuracy and coverage are reported on untouched realistic evaluation cohorts.
  4. A test run completes preprocessing with bounded driver memory and matching feature values.

Explanation

Correct Answer

D:

This verification measures the required result rather than just process liveness. A test run completes preprocessing with bounded driver memory and matching feature values. It confirms whether the targeted action succeeded: replace unnecessary local conversions with supported distributed SparkML transforms and retain an end-to-end Spark pipeline.

Incorrect Answers

A:

That acceptance test is directed at a different using spark ml situation: A text pipeline repeatedly fits a Tokenizer stage even though tokenization simply converts strings into token arrays without learning a model. Here the actual success criterion is a test run completes preprocessing with bounded driver memory and matching feature values.

B:

That acceptance test is directed at a different using spark ml situation: An ML engineer manually compares two logistic-regression regularization values on a single holdout but has no reusable SparkML parameter-search plan. Here the actual success criterion is a test run completes preprocessing with bounded driver memory and matching feature values.

C:

That acceptance test is directed at a different using spark ml situation: A recommender experiment computes all evaluation metrics on training interactions and reports the result as generalization to new customers. Here the actual success criterion is a test run completes preprocessing with bounded driver memory and matching feature values.

Question 125

A production ML review contains this situation: A business deploys a model whose features are computed from a stream in memory only and disappear when its compute cluster restarts. What production-safe change best matches the evidence?

  1. Enforce a supported lookback policy and explicit null handling for devices without recent data.
  2. Publish computed features to a durable governed destination with supported streaming recovery.
  3. Promote a versioned feature definition with backward-compatibility tests and controlled rollout.
  4. Use deterministic merge or overwrite semantics scoped to logical feature keys and verify retry behavior.

Explanation

Correct Answer

B:

This corrects the relevant failure boundary instead of merely hiding the symptom. Publish computed features to a durable governed destination with supported streaming recovery. The issue matters because scores after failover revert to incomplete or uninitialized feature state.

Incorrect Answers

A:

That corrective action is directed at a different advanced feature store concepts situation: A sensor classifier silently reuses features from a year-old device after months without readings, despite a maximum allowed lookback of seven days. The relevant corrective action here is publish computed features to a durable governed destination with supported streaming recovery.

C:

That corrective action is directed at a different advanced feature store concepts situation: A team updates a shared on-demand feature function without version control and unexpectedly changes both batch retraining and online serving behavior. The relevant corrective action here is publish computed features to a durable governed destination with supported streaming recovery.

D:

That corrective action is directed at a different advanced feature store concepts situation: A feature refresh writes duplicate records for each entity and logical timestamp after retries, breaking unique lookups. The relevant corrective action here is publish computed features to a durable governed destination with supported streaming recovery.

Question 126

In an enterprise ML workflow, the reported issue is: An Optuna search runs 80 hyperparameter trials but records only the last winning score in MLflow, making comparisons impossible. What technical distinction is essential to this investigation?

  1. Ray resource declarations must match actual device use to avoid GPU oversubscription.
  2. Data parallelism duplicates model parameters, while model parallelism or sharding distributes parameters when required.
  3. Selecting Ray over Spark must be based on the actual training library and distributed API, not the existence of a cluster.
  4. Reliable tuning provenance requires parameter, metric and trial identity logging for every evaluated trial.

Explanation

Correct Answer

D:

The technical constraint is specific to the reported failure. Reliable tuning provenance requires parameter, metric and trial identity logging for every evaluated trial. To test it, inspect the Optuna trial table and compare its IDs and metrics against MLflow runs.

Incorrect Answers

A:

That underlying principle is directed at a different scaling and tuning situation: A Ray Tune training function requests zero GPU resources but initializes a large GPU model inside every trial. The current incident instead turns on reliable tuning provenance requires parameter, metric and trial identity logging for every evaluated trial.

B:

That underlying principle is directed at a different scaling and tuning situation: A language model's weights cannot fit on one accelerator yet a team launches pure data-parallel replicas, each loading the entire model. The current incident instead turns on reliable tuning provenance requires parameter, metric and trial identity logging for every evaluated trial.

C:

That underlying principle is directed at a different scaling and tuning situation: A team switches a SparkML training stage to Ray without verifying that its chosen estimator supports Ray's distributed fit contracts. The current incident instead turns on reliable tuning provenance requires parameter, metric and trial identity logging for every evaluated trial.

Question 127

Consider the following fictional Databricks production case: A streaming anomaly team uses a static read of a message directory once, believing the trained SparkML model will continuously produce scores for future arriving events. What consequence most specifically follows from leaving the issue unchanged?

  1. Events arriving after startup never receive anomaly scores.
  2. No training-derived category mapping exists for the requested transformation.
  3. The supposedly unseen holdout can affect model inputs and inflate reported generalization.
  4. The selected hyperparameter reflects an unrepeatable or misreported single holdout trial.

Explanation

Correct Answer

A:

This consequence follows from the specific unresolved condition. Events arriving after startup never receive anomaly scores. The causal constraint is: A fitted model can transform streaming DataFrames in a supported Structured Streaming pipeline, but a one-time static read is not a continuing source.

Incorrect Answers

B:

That direct consequence is directed at a different using spark ml situation: A new Spark developer calls transform on an unfitted StringIndexer instance and expects learned category labels to appear automatically. The more immediate risk here is events arriving after startup never receive anomaly scores.

C:

That direct consequence is directed at a different using spark ml situation: A credit-risk pipeline fits StringIndexer on the entire dataset before splitting train and holdout, and rare holdout labels influence its learned category mapping. The more immediate risk here is events arriving after startup never receive anomaly scores.

D:

That direct consequence is directed at a different using spark ml situation: An ML engineer manually compares two logistic-regression regularization values on a single holdout but has no reusable SparkML parameter-search plan. The more immediate risk here is events arriving after startup never receive anomaly scores.

Question 128

Review this production model incident: A team already has a vectorized Spark DataFrame pipeline and proposes converting everything to Ray datasets solely to perform a simple SQL aggregation. What is the central engineering constraint behind this behavior?

  1. Spark SQL is often the more direct choice for distributed tabular transformations, while Ray targets flexible task/actor workloads.
  2. Reliable tuning provenance requires parameter, metric and trial identity logging for every evaluated trial.
  3. Ray resource declarations must match actual device use to avoid GPU oversubscription.
  4. Vertical versus horizontal scaling decisions must consider dataset size, execution architecture and fixed coordination overhead.

Explanation

Correct Answer

A:

The technical constraint is specific to the reported failure. Spark SQL is often the more direct choice for distributed tabular transformations, while Ray targets flexible task/actor workloads. To test it, compare operation requirements, data conversion cost and supported query optimizations in both engines.

Incorrect Answers

B:

That underlying principle is directed at a different scaling and tuning situation: An Optuna search runs 80 hyperparameter trials but records only the last winning score in MLflow, making comparisons impossible. The current incident instead turns on spark SQL is often the more direct choice for distributed tabular transformations, while Ray targets flexible task/actor workloads.

C:

That underlying principle is directed at a different scaling and tuning situation: A Ray Tune training function requests zero GPU resources but initializes a large GPU model inside every trial. The current incident instead turns on spark SQL is often the more direct choice for distributed tabular transformations, while Ray targets flexible task/actor workloads.

D:

That underlying principle is directed at a different scaling and tuning situation: A moderately sized dataset fits on one worker but a team provisions a huge distributed cluster and observes overhead higher than model fit. The current incident instead turns on spark SQL is often the more direct choice for distributed tabular transformations, while Ray targets flexible task/actor workloads.

Question 129

In an enterprise ML workflow, the reported issue is: A monitor is pointed at a Unity Catalog table but the automation identity lacks the privileges needed to generate profile outputs. Before modifying the pipeline, which evidence should be collected first?

  1. Review rolling-window statistics alongside a fixed approved baseline for the same cohort.
  2. Inspect sample size, numeric drift statistic and estimated business impact for the same comparison.
  3. Inspect effective owner permissions, catalog/schema access and creation error logs for the target table.
  4. Inspect whether row-level event timestamps and prediction records actually exist for the desired minute windows.

Explanation

Correct Answer

C:

This is the most discriminating check for the observed symptoms. Inspect effective owner permissions, catalog/schema access and creation error logs for the target table. The underlying technical issue is that monitor creation and ongoing metric writes depend on governed resource access and configured output locations.

Incorrect Answers

A:

That diagnostic evidence is directed at a different drift detection and lakehouse monitoring situation: A streaming payments monitor always compares today with the previous hour, and a slow week-long distribution drift escapes because adjacent hours differ only slightly. For the stated incident, the decisive observation is inspect effective owner permissions, catalog/schema access and creation error logs for the target table.

B:

That diagnostic evidence is directed at a different drift detection and lakehouse monitoring situation: A monitoring dashboard reports a statistically significant tiny difference after one million observations, and the team immediately treats it as operationally material drift. For the stated incident, the decisive observation is inspect effective owner permissions, catalog/schema access and creation error logs for the target table.

D:

That diagnostic evidence is directed at a different drift detection and lakehouse monitoring situation: A research team captures only daily batch inference totals with no row-level timestamps but insists on per-minute live inference drift analysis. For the stated incident, the decisive observation is inspect effective owner permissions, catalog/schema access and creation error logs for the target table.

Question 130

Review this production model incident: A fraud-feature drift monitor crosses its threshold but the alert has no assigned recipient and no incident ownership. Which mitigation resolves the defect rather than concealing it?

  1. Use a supported snapshot data profile for the governed table and its quality metrics.
  2. Configure a documented threshold with the responsible on-call team and a tested delivery route.
  3. Configure model-identity-aware inference monitoring with version-specific comparisons.
  4. Compute comparable version-specific performance trends and retain traffic-share context.

Explanation

Correct Answer

B:

This corrects the relevant failure boundary instead of merely hiding the symptom. Configure a documented threshold with the responsible on-call team and a tested delivery route. The issue matters because material drift remains unaddressed because nobody receives the notification.

Incorrect Answers

A:

That corrective action is directed at a different drift detection and lakehouse monitoring situation: An analyst wants to inspect today’s static customer table for missing values and profile changes but chooses an inference monitor requiring model IDs and predictions. The relevant corrective action here is configure a documented threshold with the responsible on-call team and a tested delivery route.

C:

That corrective action is directed at a different drift detection and lakehouse monitoring situation: An inference profile groups two active model versions into one aggregate and hides a regression introduced by the new release. The relevant corrective action here is configure a documented threshold with the responsible on-call team and a tested delivery route.

D:

That corrective action is directed at a different drift detection and lakehouse monitoring situation: A scoring endpoint quietly moves from model v7 to v8 during a rollout but an inference trend aggregates both versions in one error curve. The relevant corrective action here is configure a documented threshold with the responsible on-call team and a tested delivery route.

Certified Machine Learning Professional Practice Tests