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 27

Question 260

The engineering team encounters the following issue: A recommendation team wraps a large pandas UDF around entire customer histories, then discovers some partitions exceed worker memory while others finish quickly. What investigation would most effectively isolate this behavior?

  1. Inspect the Optuna trial table and compare its IDs and metrics against MLflow runs.
  2. Review simulator state ownership, task dependency graph and required actor lifetimes.
  3. Inspect per-group record counts, Arrow batch sizes and executor spill or OOM traces.
  4. Compare GPU inventory with the current trial task graph, resource reservations and wait times.

Explanation

Correct Answer

C:

This is the most discriminating check for the observed symptoms. Inspect per-group record counts, Arrow batch sizes and executor spill or OOM traces. The underlying technical issue is that pandas-function distribution requires bounded partition or group size, not just parallel execution of arbitrary large pandas objects.

Incorrect Answers

A:

That diagnostic evidence 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. For the stated incident, the decisive observation is inspect per-group record counts, Arrow batch sizes and executor spill or OOM traces.

B:

That diagnostic evidence is directed at a different scaling and tuning situation: A reinforcement-learning simulator requires stateful actors exchanging messages and irregular task graphs, but the team plans one Spark SQL groupBy per simulation step. For the stated incident, the decisive observation is inspect per-group record counts, Arrow batch sizes and executor spill or OOM traces.

D:

That diagnostic evidence is directed at a different scaling and tuning situation: A team runs independent GPU-heavy neural trials sequentially, despite having several isolated GPU workers that can fit each model. For the stated incident, the decisive observation is inspect per-group record counts, Arrow batch sizes and executor spill or OOM traces.

Question 261

Review this production model incident: An analyst loads a fitted LogisticRegressionModel but calls fit on it for every scored batch rather than transform. Which mitigation resolves the defect rather than concealing it?

  1. Evaluate the model with class-sensitive metrics and choose thresholds aligned with false-positive and missed-fraud tradeoffs.
  2. Use model.transform on new feature vectors and retrain only in an approved training workflow.
  3. Choose a justified supported unknown-category handling strategy and test it without retraining on confidential evaluation labels.
  4. Fit and persist a unified PipelineModel containing scaling and model stages, then use it for inference.

Explanation

Correct Answer

B:

This corrects the relevant failure boundary instead of merely hiding the symptom. Use model.transform on new feature vectors and retrain only in an approved training workflow. The issue matters because unintended retraining or API failures compromise reproducibility of batch scores.

Incorrect Answers

A:

That corrective action is directed at a different using spark ml situation: A fraud detector predicts the majority no-fraud class for 99.4% of cases and advertises 99.4% accuracy while missing most positives. The relevant corrective action here is use model.transform on new feature vectors and retrain only in an approved training workflow.

C:

That corrective action is directed at a different using spark ml situation: An inference pipeline sends new categorical labels unseen during training to StringIndexerModel with error handling configured to reject unknown categories. The relevant corrective action here is use model.transform on new feature vectors and retrain only in an approved training workflow.

D:

That corrective action is directed at a different using spark ml situation: A churn experiment separately scripts feature scaling in training but omits that scaling when the deployed prediction job loads the classifier. The relevant corrective action here is use model.transform on new feature vectors and retrain only in an approved training workflow.

Question 262

In an enterprise ML workflow, the reported issue is: A fairness reviewer needs the difference in false-negative rates between two approved cohorts, but the monitor computes an aggregate without cohort labels. How should the engineer validate the correction?

  1. A test alert identifies the precise asset, time window, threshold and metric that caused it.
  2. A cohort with large cumulative distance from its training baseline raises a distinct signal.
  3. Queue length and tail latency fall under controlled peak traffic without unnecessary idle CPU provisioning.
  4. A synthetic two-cohort fixture produces the independently calculated disparity value.

Explanation

Correct Answer

D:

This verification measures the required result rather than just process liveness. A synthetic two-cohort fixture produces the independently calculated disparity value. It confirms whether the targeted action succeeded: calculate slice-specific error rates and a documented derived disparity metric with privacy safeguards.

Incorrect Answers

A:

That acceptance test is directed at a different drift detection and lakehouse monitoring situation: A drift alert fires but its message contains only the word anomaly without dataset, model version or baseline window. Here the actual success criterion is a synthetic two-cohort fixture produces the independently calculated disparity value.

B:

That acceptance test is directed at a different drift detection and lakehouse monitoring situation: A model trained on last year's customer mix is monitored only against yesterday's already shifted cohort, so its original training-population mismatch is hidden. Here the actual success criterion is a synthetic two-cohort fixture produces the independently calculated disparity value.

C:

That acceptance test is directed at a different drift detection and lakehouse monitoring situation: A production endpoint scales CPU instances up when traffic rises, but request queues and P95 response time keep growing despite low CPU usage. Here the actual success criterion is a synthetic two-cohort fixture produces the independently calculated disparity value.

Question 263

Review this production model incident: A batch scoring pipeline trains one per-region model and then joins model predictions back using region alone, duplicating rows because each region contains multiple versioned models. What end-to-end verification is most persuasive here?

  1. A controlled A/B benchmark demonstrates the chosen configuration's cost-performance advantage.
  2. End-to-end throughput improves after removing the true serialized bottleneck.
  3. A restart retains finished trial metrics and resumes remaining work without rerunning accepted completions.
  4. Each source record receives exactly one score from its assigned region-specific model version.

Explanation

Correct Answer

D:

This verification measures the required result rather than just process liveness. Each source record receives exactly one score from its assigned region-specific model version. It confirms whether the targeted action succeeded: bind the selected model version to each group and join predictions on a unique provenance key.

Incorrect Answers

A:

That acceptance test 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. Here the actual success criterion is each source record receives exactly one score from its assigned region-specific model version.

B:

That acceptance test is directed at a different scaling and tuning situation: An ML project has a single sequential external feature-service dependency and expects data-parallel workers to increase throughput 20-fold. Here the actual success criterion is each source record receives exactly one score from its assigned region-specific model version.

C:

That acceptance test is directed at a different scaling and tuning situation: An interrupted Ray hyperparameter sweep has an expensive completed-trial history but a new launch discards its experiment checkpoint. Here the actual success criterion is each source record receives exactly one score from its assigned region-specific model version.

Question 264

In an enterprise ML workflow, the reported issue is: An endpoint update request succeeds but the newly configured model version is still loading; monitoring marks the release complete immediately. What technical distinction is essential to this investigation?

  1. Rare-outcome evaluation requires sufficient exposure, observation time and mature labels before concluding parity.
  2. Blue-green deployment keeps two release environments available so traffic can be switched between validated states.
  3. Model Serving configuration acceptance is not equivalent to endpoint/model readiness for user traffic.
  4. A canary rollout can expose a small controlled share of live traffic while retaining a proven model for most requests.

Explanation

Correct Answer

C:

The technical constraint is specific to the reported failure. Model Serving configuration acceptance is not equivalent to endpoint/model readiness for user traffic. To test it, inspect endpoint state, individual served-entity readiness and model-load errors after the update.

Incorrect Answers

A:

That underlying principle 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 current incident instead turns on model Serving configuration acceptance is not equivalent to endpoint/model readiness for user traffic.

B:

That underlying principle 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 current incident instead turns on model Serving configuration acceptance is not equivalent to endpoint/model readiness for user traffic.

D:

That underlying principle is directed at a different deployment strategies situation: A travel site serves 30,000 bookings per minute and wants to evaluate a new fraud model while limiting customer impact during its first hour. The current incident instead turns on model Serving configuration acceptance is not equivalent to endpoint/model readiness for user traffic.

Question 265

Review this production model incident: A team logs custom MLflow model weights but forgets to include required Python package versions in the model environment. What evidence would best distinguish the actual fault from neighboring ML concerns?

  1. Review endpoint change history, CI deployment commits and the order of conflicting updates.
  2. Inspect sanitized 401/403 response details, the caller identity and documented endpoint access scopes.
  3. Compare training import versions and logged model environment metadata with serving import failures.
  4. Compare response creation time, endpoint model version and cache keys before and after rollback.

Explanation

Correct Answer

C:

This is the most discriminating check for the observed symptoms. Compare training import versions and logged model environment metadata with serving import failures. The underlying technical issue is that mLflow custom-model portability depends on the declared runtime dependencies as well as artifact bytes.

Incorrect Answers

A:

That diagnostic evidence is directed at a different custom model serving situation: A team edits a model endpoint through the UI while its CI pipeline concurrently applies an older configuration and reverts the intended traffic split. For the stated incident, the decisive observation is compare training import versions and logged model environment metadata with serving import failures.

B:

That diagnostic evidence is directed at a different custom model serving situation: A client invokes a registered custom ML model using an unauthenticated HTTP POST to the serving endpoint and assumes network access implies authorization. For the stated incident, the decisive observation is compare training import versions and logged model environment metadata with serving import failures.

D:

That diagnostic evidence is directed at a different custom model serving situation: An integration caches predictions without recording the model version and returns yesterday's values after a controlled rollback. For the stated incident, the decisive observation is compare training import versions and logged model environment metadata with serving import failures.

Question 266

Review this production model incident: A new Spark developer calls transform on an unfitted StringIndexer instance and expects learned category labels to appear automatically. What is the central engineering constraint behind this behavior?

  1. Training-set fit does not establish out-of-sample predictive quality or cold-start behavior.
  2. Scoring should use preprocessing components trained and versioned with the exact estimator artifact.
  3. StringIndexer is an Estimator that must fit its category mapping before its resulting model can transform records.
  4. Keeping fitted preprocessing and the estimator in one saved PipelineModel prevents training-serving transformation drift.

Explanation

Correct Answer

C:

The technical constraint is specific to the reported failure. StringIndexer is an Estimator that must fit its category mapping before its resulting model can transform records. To test it, compare the original StringIndexer type with the fitted StringIndexerModel and inspect its label mapping.

Incorrect Answers

A:

That underlying principle 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. The current incident instead turns on stringIndexer is an Estimator that must fit its category mapping before its resulting model can transform records.

B:

That underlying principle is directed at a different using spark ml situation: A batch scoring service loads a classifier version from last month while using today's new feature indexer, silently changing categorical positions. The current incident instead turns on stringIndexer is an Estimator that must fit its category mapping before its resulting model can transform records.

D:

That underlying principle is directed at a different using spark ml situation: A churn experiment separately scripts feature scaling in training but omits that scaling when the deployed prediction job loads the classifier. The current incident instead turns on stringIndexer is an Estimator that must fit its category mapping before its resulting model can transform records.

Question 267

Consider the following fictional Databricks production case: A data scientist selects the lowest validation loss from nested runs but reports only the parent run ID as the model-producing run. Which observation most directly tests the suspected failure boundary?

  1. Compare training feature timestamp definitions with live feature retrieval windows on a matched historical request.
  2. Inspect metric computation code and raw values across runs for incompatible scale conventions.
  3. Replay interleaved synthetic customer requests and inspect whether cache keys and outputs remain isolated.
  4. Trace winning model artifact URI and validation metric to its actual nested child run.

Explanation

Correct Answer

D:

This is the most discriminating check for the observed symptoms. Trace winning model artifact URI and validation metric to its actual nested child run. The underlying technical issue is that a parent groups trials; the specific child run that produced the selected artifact must remain identifiable.

Incorrect Answers

A:

That diagnostic evidence is directed at a different advanced mlflow usage situation: A deployed custom model fetches latest feature values during serving while offline evaluation used event-time snapshots without checking the difference. For the stated incident, the decisive observation is trace winning model artifact URI and validation metric to its actual nested child run.

B:

That diagnostic evidence is directed at a different advanced mlflow usage situation: A team logs a score labeled accuracy with values between 0 and 100 in some runs and between 0 and 1 in others, then ranks runs automatically. For the stated incident, the decisive observation is trace winning model artifact URI and validation metric to its actual nested child run.

C:

That diagnostic evidence 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. For the stated incident, the decisive observation is trace winning model artifact URI and validation metric to its actual nested child run.

Question 268

A production ML review contains this situation: A real-time churn endpoint accepts customer IDs and must fetch current allowed account features, but a custom model class instead expects the caller to supply the entire internal training row. Which diagnostic check provides the strongest direct evidence?

  1. Inspect the run's metric keys versus artifact store and recover the expected plot file.
  2. Compare actual serving request schema, feature lookup capabilities and the model's predict signature.
  3. Trace winning model artifact URI and validation metric to its actual nested child run.
  4. Correlate worker logs and metric histories by run ID to expose simultaneous writes to the same run.

Explanation

Correct Answer

B:

This is the most discriminating check for the observed symptoms. Compare actual serving request schema, feature lookup capabilities and the model's predict signature. The underlying technical issue is that a custom MLflow PyFunc's input contract and online feature lookups must be designed for request-time availability and governance.

Incorrect Answers

A:

That diagnostic evidence is directed at a different advanced mlflow usage situation: An ML engineer logs a calibration plot as a string metric, then downstream reviewers cannot inspect the visualization or its input version. For the stated incident, the decisive observation is compare actual serving request schema, feature lookup capabilities and the model's predict signature.

C:

That diagnostic evidence is directed at a different advanced mlflow usage situation: A data scientist selects the lowest validation loss from nested runs but reports only the parent run ID as the model-producing run. For the stated incident, the decisive observation is compare actual serving request schema, feature lookup capabilities and the model's predict signature.

D:

That diagnostic evidence is directed at a different advanced mlflow usage situation: A training orchestrator starts parallel child fits but all workers accidentally log into one active MLflow run and overwrite each other's metrics. For the stated incident, the decisive observation is compare actual serving request schema, feature lookup capabilities and the model's predict signature.

Question 269

The engineering team encounters the following issue: A notebook uses the MLflow Deployments SDK to send a column-major payload to a custom model endpoint expecting a different documented dataframe schema. Which experiment most directly demonstrates a successful fix?

  1. The scoped automation can deploy the authorized model and cannot access unrelated catalog models.
  2. Boundary requests return validated predictions or controlled informative errors according to contract.
  3. A saved two-record request returns correctly ordered predictions with the expected schema.
  4. An artifact scan contains no credential strings while authorized serving requests still work.

Explanation

Correct Answer

C:

This verification measures the required result rather than just process liveness. A saved two-record request returns correctly ordered predictions with the expected schema. It confirms whether the targeted action succeeded: format requests according to the supported MLflow Deployments client and registered model input schema.

Incorrect Answers

A:

That acceptance test is directed at a different custom model serving situation: A test engineer can create a model-serving endpoint in a sandbox but the production deployment fails because the automation identity lacks registered-model access. Here the actual success criterion is a saved two-record request returns correctly ordered predictions with the expected schema.

B:

That acceptance test is directed at a different custom model serving situation: A custom PyFunc's predict method assumes every request contains a numeric feature that is optional under the documented inference schema. Here the actual success criterion is a saved two-record request returns correctly ordered predictions with the expected schema.

D:

That acceptance test is directed at a different custom model serving situation: An engineer logs a customer-specific API token inside the pickled PythonModel object before registering it to Unity Catalog. Here the actual success criterion is a saved two-record request returns correctly ordered predictions with the expected schema.

Question 270

A production ML review contains this situation: A training dataset combines a feature table with multiple timestamped rows per device using an equality join on device ID only. Which statement best explains the failure mode?

  1. A time-series feature table needs a documented timestamp key and an as-of lookup to avoid multiplying labels or attaching future values.
  2. An online store's existence does not guarantee its feature freshness; synchronization must be monitored.
  3. On-demand feature functions must explicitly handle invalid input and output type constraints.
  4. Historical feature timelines must be retained when reproducible point-in-time joins depend on prior values.

Explanation

Correct Answer

A:

The technical constraint is specific to the reported failure. A time-series feature table needs a documented timestamp key and an as-of lookup to avoid multiplying labels or attaching future values. To test it, check entity join cardinality and the most recent eligible feature timestamp for each observation.

Incorrect Answers

B:

That underlying principle is directed at a different advanced feature store concepts situation: A team publishes an online feature table but neglects its refresh schedule while the predictive model assumes values no older than 15 minutes. The current incident instead turns on a time-series feature table needs a documented timestamp key and an as-of lookup to avoid multiplying labels or attaching future values.

C:

That underlying principle is directed at a different advanced feature store concepts situation: A payment classifier's on-demand feature division returns infinity for zero denominators and fails serialization in the serving endpoint. The current incident instead turns on a time-series feature table needs a documented timestamp key and an as-of lookup to avoid multiplying labels or attaching future values.

D:

That underlying principle is directed at a different advanced feature store concepts situation: A model's feature generation step overwrites all feature-table history daily even though time-aware training requires earlier snapshots. The current incident instead turns on a time-series feature table needs a documented timestamp key and an as-of lookup to avoid multiplying labels or attaching future values.

Certified Machine Learning Professional Practice Tests