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 38

Question 370

Consider the following fictional Databricks production case: A feature-engineering job is CPU-bound on hundreds of independent daily partitions and a team upgrades only the driver to a much larger machine. What consequence most specifically follows from leaving the issue unchanged?

  1. A costly driver upgrade leaves worker-side backlog and deadline misses unchanged.
  2. Multiple trials contend for the same accelerator and fail with memory exhaustion.
  3. Seasonal behavior is blurred and no store receives its required independent fit.
  4. Trials are lost or repeated even when compute nodes appear healthy.

Explanation

Correct Answer

A:

This consequence follows from the specific unresolved condition. A costly driver upgrade leaves worker-side backlog and deadline misses unchanged. The causal constraint is: Data-parallel workloads may benefit from more executor cores and appropriately partitioned tasks rather than vertical driver scaling.

Incorrect Answers

B:

That direct consequence 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 more immediate risk here is a costly driver upgrade leaves worker-side backlog and deadline misses unchanged.

C:

That direct consequence is directed at a different scaling and tuning situation: A retailer needs one independent forecasting model per store but concatenates all store histories before fitting one global model. The more immediate risk here is a costly driver upgrade leaves worker-side backlog and deadline misses unchanged.

D:

That direct consequence is directed at a different scaling and tuning situation: A researcher parallelizes Optuna trials while sharing one writable SQLite file on a fragile network mount and observes duplicate reservations and storage locks. The more immediate risk here is a costly driver upgrade leaves worker-side backlog and deadline misses unchanged.

Question 371

A production ML review contains this situation: An interrupted Ray hyperparameter sweep has an expensive completed-trial history but a new launch discards its experiment checkpoint. What production-safe change best matches the evidence?

  1. Tune outer concurrency based on actual cluster capacity and each trial's resource demand.
  2. Persist trial checkpoints to approved durable storage and restore unfinished trials using the supported Ray workflow.
  3. Keep SQL/DataFrame aggregation in Spark unless a distinct Ray capability justifies conversion.
  4. Assign each trial a unique tracked run with a shared parent experiment and stable trial metadata.

Explanation

Correct Answer

B:

This corrects the relevant failure boundary instead of merely hiding the symptom. Persist trial checkpoints to approved durable storage and restore unfinished trials using the supported Ray workflow. The issue matters because training compute is wasted and selected parameters are biased toward only the new subset of trials.

Incorrect Answers

A:

That corrective action is directed at a different scaling and tuning situation: An operations model uses a SparkML estimator that itself distributes data, yet the team launches dozens of concurrent full-cluster fits on the same fixed small cluster. The relevant corrective action here is persist trial checkpoints to approved durable storage and restore unfinished trials using the supported Ray workflow.

C:

That corrective action is directed at a different scaling and tuning situation: A team already has a vectorized Spark DataFrame pipeline and proposes converting everything to Ray datasets solely to perform a simple SQL aggregation. The relevant corrective action here is persist trial checkpoints to approved durable storage and restore unfinished trials using the supported Ray workflow.

D:

That corrective action is directed at a different scaling and tuning situation: An Optuna optimization reuses the same MLflow run ID for concurrent trials, causing overlapping parameter values and artifacts. The relevant corrective action here is persist trial checkpoints to approved durable storage and restore unfinished trials using the supported Ray workflow.

Question 372

In an enterprise ML workflow, the reported issue is: A team trains on curated development features but deploys the same job with credentials that accidentally read unapproved production source tables. Which change addresses the real cause without undermining other requirements?

  1. Use a supported governed model registry and controlled permissions for production model versions.
  2. Parameterize approved environment resources and use narrowly scoped credentials per stage.
  3. Bind training outputs to registered immutable versions and promote them through governed jobs or serving endpoints.
  4. Apply the correct governance controls separately to experiments, registered models and serving endpoints.

Explanation

Correct Answer

B:

This corrects the relevant failure boundary instead of merely hiding the symptom. Parameterize approved environment resources and use narrowly scoped credentials per stage. The issue matters because production inference can access unrelated protected data or train on unintended tables.

Incorrect Answers

A:

That corrective action is directed at a different model lifecycle management situation: An engineer stores model weights in a personal workspace folder and treats that path as a production artifact registry with audit history. The relevant corrective action here is parameterize approved environment resources and use narrowly scoped credentials per stage.

C:

That corrective action is directed at a different model lifecycle management situation: A team records experiments but has no controlled path from a selected registered model to scheduled scoring jobs. The relevant corrective action here is parameterize approved environment resources and use narrowly scoped credentials per stage.

D:

That corrective action is directed at a different model lifecycle management situation: A platform team proposes using MLflow Tracking alone to enforce production endpoint authorization, ignoring Unity Catalog and service permissions. The relevant corrective action here is parameterize approved environment resources and use narrowly scoped credentials per stage.

Question 373

The engineering team encounters the following issue: An endpoint's error rate spikes while data profiles look normal, and responders attempt to retrain the model instead of checking serving infrastructure. What investigation would most effectively isolate this behavior?

  1. Inspect endpoint status codes, resource saturation and model-load logs together with current profile metrics.
  2. Inspect the stored snapshot rows and timestamps to determine whether historical hourly observations are retained.
  3. Compare historical baselines, current seasonal patterns and change approvals for the existing threshold.
  4. Compare recent and baseline quantiles plus a supported numeric distribution-difference metric at equivalent sample sizes.

Explanation

Correct Answer

A:

This is the most discriminating check for the observed symptoms. Inspect endpoint status codes, resource saturation and model-load logs together with current profile metrics. The underlying technical issue is that model health, performance and data drift are different failure categories that need separate investigation paths.

Incorrect Answers

B:

That diagnostic evidence is directed at a different drift detection and lakehouse monitoring situation: A retail profile is created on a static materialized daily inventory table; a team expects its initial snapshot to show each prior hour as a separate trend. For the stated incident, the decisive observation is inspect endpoint status codes, resource saturation and model-load logs together with current profile metrics.

C:

That diagnostic evidence is directed at a different drift detection and lakehouse monitoring situation: A production alert threshold is hard-coded against last year's baseline, but seasonal traffic has shifted and the owner never reviewed the threshold. For the stated incident, the decisive observation is inspect endpoint status codes, resource saturation and model-load logs together with current profile metrics.

D:

That diagnostic evidence is directed at a different drift detection and lakehouse monitoring situation: A loan-risk feature usually has median debt-to-income 0.34, but a new cohort has median 0.61 while the average stays almost unchanged due to outliers. For the stated incident, the decisive observation is inspect endpoint status codes, resource saturation and model-load logs together with current profile metrics.

Question 374

The engineering team encounters the following issue: A developer changes a feature transform in a notebook and directly uses production data as the only test case. What investigation would most effectively isolate this behavior?

  1. Compare helper source hashes and test assertions across consuming notebooks.
  2. Repeat the same synthetic category fixture in separate processes and compare exact mapping outputs.
  3. Compare timestamp values after ingestion, feature-table write and training-set as-of join for one known event.
  4. Inspect test-environment evidence and the presence of function-level synthetic fixtures.

Explanation

Correct Answer

D:

This is the most discriminating check for the observed symptoms. Inspect test-environment evidence and the presence of function-level synthetic fixtures. The underlying technical issue is that unit tests belong on controlled synthetic inputs before integrations, and production smoke tests do not replace them.

Incorrect Answers

A:

That diagnostic evidence is directed at a different validation testing situation: An engineering group duplicates a validation helper across six notebooks, and two copies enforce outdated threshold values. For the stated incident, the decisive observation is inspect test-environment evidence and the presence of function-level synthetic fixtures.

B:

That diagnostic evidence is directed at a different validation testing situation: A notebook's label encoder produces a different category order depending on an unordered Python set, but tests assert only output length. For the stated incident, the decisive observation is inspect test-environment evidence and the presence of function-level synthetic fixtures.

C:

That diagnostic evidence is directed at a different validation testing situation: A feature-refresh task writes rows with event time in local timezone while the training join assumes UTC; unit tests of each component pass. For the stated incident, the decisive observation is inspect test-environment evidence and the presence of function-level synthetic fixtures.

Question 375

A production ML review contains this situation: A language model's weights cannot fit on one accelerator yet a team launches pure data-parallel replicas, each loading the entire model. Which diagnostic check provides the strongest direct evidence?

  1. Inspect model registry versions, join keys and output cardinality against source record IDs.
  2. Compare per-replica parameter memory with device capacity and supported sharding topology.
  3. Compare GPU inventory with the current trial task graph, resource reservations and wait times.
  4. Measure repeated dataset exports and per-trial deserialization relative to model-fitting time.

Explanation

Correct Answer

B:

This is the most discriminating check for the observed symptoms. Compare per-replica parameter memory with device capacity and supported sharding topology. The underlying technical issue is that data parallelism duplicates model parameters, while model parallelism or sharding distributes parameters when required.

Incorrect Answers

A:

That diagnostic evidence is directed at a different scaling and tuning situation: 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. For the stated incident, the decisive observation is compare per-replica parameter memory with device capacity and supported sharding topology.

C:

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 compare per-replica parameter memory with device capacity and supported sharding topology.

D:

That diagnostic evidence is directed at a different scaling and tuning situation: A hyperparameter search operates on large Spark-managed feature tables but each candidate model is small and independent, and workers repeatedly convert the entire table for each Ray task. For the stated incident, the decisive observation is compare per-replica parameter memory with device capacity and supported sharding topology.

Question 376

The engineering team encounters the following issue: 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. What corrective action should the engineer prefer?

  1. Record the selected child run and model artifact identity in the parent summary metadata.
  2. Replace identifiers with synthetic or aggregated diagnostic evidence and restrict artifact access appropriately.
  3. Record a resume lineage link and preserve distinct nested trials for both original and continued runs.
  4. Package validated feature retrieval and preprocessing behind a documented PyFunc inference contract with approved credentials.

Explanation

Correct Answer

D:

This corrects the relevant failure boundary instead of merely hiding the symptom. Package validated feature retrieval and preprocessing behind a documented PyFunc inference contract with approved credentials. The issue matters because clients cannot satisfy the model input requirements, so live predictions fail or leak internal fields.

Incorrect Answers

A:

That corrective action 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. The relevant corrective action here is package validated feature retrieval and preprocessing behind a documented PyFunc inference contract with approved credentials.

B:

That corrective action is directed at a different advanced mlflow usage situation: A regulated analytics team uploads full customer identifiers inside MLflow model artifacts during troubleshooting. The relevant corrective action here is package validated feature retrieval and preprocessing behind a documented PyFunc inference contract with approved credentials.

C:

That corrective action 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 relevant corrective action here is package validated feature retrieval and preprocessing behind a documented PyFunc inference contract with approved credentials.

Question 377

In an enterprise ML workflow, the reported issue is: After choosing the best parameter map, a data scientist reports the same cross-validation score as an independent final test result without any untouched data. Which change addresses the real cause without undermining other requirements?

  1. Add a justified tail-sensitive error measure such as RMSE and inspect failure slices in model selection.
  2. Use Tokenizer.transform in the correct pipeline position while reserving fit for actual Estimators.
  3. Hold out a final test set before tuning and score the selected pipeline exactly once after selection.
  4. Run a versioned scheduled batch-scoring workflow and materialize results for downstream review.

Explanation

Correct Answer

C:

This corrects the relevant failure boundary instead of merely hiding the symptom. Hold out a final test set before tuning and score the selected pipeline exactly once after selection. The issue matters because reported performance is optimistically biased because the evaluation influenced configuration choice.

Incorrect Answers

A:

That corrective action is directed at a different using spark ml situation: A forecasting model has a few catastrophic numeric errors hidden by a low median absolute error and operations care about large misses. The relevant corrective action here is hold out a final test set before tuning and score the selected pipeline exactly once after selection.

B:

That corrective action 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. The relevant corrective action here is hold out a final test set before tuning and score the selected pipeline exactly once after selection.

D:

That corrective action is directed at a different using spark ml situation: A credit reporting task needs one million records scored once per week for offline account review and requests a permanently running interactive endpoint. The relevant corrective action here is hold out a final test set before tuning and score the selected pipeline exactly once after selection.

Question 378

Review this production model incident: A churn model logs requests, predictions, model versions and later ground-truth labels, but monitoring is configured as a generic feature snapshot. Which failure risk follows most closely from the unresolved behavior?

  1. A broken source creates a silent feature gap while the surviving non-null distribution appears stable.
  2. Users cannot receive predictions because of infrastructure failures that retraining cannot fix.
  3. Performance comparisons by deployed model version cannot be calculated from the generic snapshot configuration.
  4. Gradual cumulative drift becomes invisible despite material divergence from the trained population.

Explanation

Correct Answer

C:

This consequence follows from the specific unresolved condition. Performance comparisons by deployed model version cannot be calculated from the generic snapshot configuration. The causal constraint is: Inference profiles are built for prediction monitoring when model ID, outputs, timestamps and optionally labels are recorded.

Incorrect Answers

A:

That direct consequence is directed at a different drift detection and lakehouse monitoring situation: A nightly scoring feed drops all null-feature rows before calculating drift, making missingness jump invisible. The more immediate risk here is performance comparisons by deployed model version cannot be calculated from the generic snapshot configuration.

B:

That direct consequence is directed at a different drift detection and lakehouse monitoring situation: An endpoint's error rate spikes while data profiles look normal, and responders attempt to retrain the model instead of checking serving infrastructure. The more immediate risk here is performance comparisons by deployed model version cannot be calculated from the generic snapshot configuration.

D:

That direct consequence 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. The more immediate risk here is performance comparisons by deployed model version cannot be calculated from the generic snapshot configuration.

Question 379

A production ML review contains this situation: An engineer stores model weights in a personal workspace folder and treats that path as a production artifact registry with audit history. What production-safe change best matches the evidence?

  1. Parameterize approved environment resources and use narrowly scoped credentials per stage.
  2. Use a supported governed model registry and controlled permissions for production model versions.
  3. Pin and validate supported dependency versions as part of the promoted model/code release.
  4. Add a backward-compatible schema migration and gated deployment order to the release workflow.

Explanation

Correct Answer

B:

This corrects the relevant failure boundary instead of merely hiding the symptom. Use a supported governed model registry and controlled permissions for production model versions. The issue matters because the artifact can disappear with an account change or be overwritten without reliable provenance.

Incorrect Answers

A:

That corrective action is directed at a different model lifecycle management situation: A team trains on curated development features but deploys the same job with credentials that accidentally read unapproved production source tables. The relevant corrective action here is use a supported governed model registry and controlled permissions for production model versions.

C:

That corrective action 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. The relevant corrective action here is use a supported governed model registry and controlled permissions for production model versions.

D:

That corrective action 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. The relevant corrective action here is use a supported governed model registry and controlled permissions for production model versions.

Question 380

Review this production model incident: An online feature monitor compares weekend shopping to weekday reference data and treats expected weekend behavior as a model failure. What evidence would best distinguish the actual fault from neighboring ML concerns?

  1. Stratify historical samples by day type and examine whether the observed difference is expected seasonality.
  2. Compare inference-table last-seen with metric-table last-refresh and schema errors in profiling jobs.
  3. Compare spike duration and alert time window against the approved ten-minute persistence rule.
  4. Test timestamp conversion and timezone interpretation for valid and malformed synthetic source rows.

Explanation

Correct Answer

A:

This is the most discriminating check for the observed symptoms. Stratify historical samples by day type and examine whether the observed difference is expected seasonality. The underlying technical issue is that reference populations should match relevant seasonality and business context when interpreting drift.

Incorrect Answers

B:

That diagnostic evidence is directed at a different drift detection and lakehouse monitoring situation: A team has accurate inference logs but its monitoring job never refreshes computed drift metrics after a table schema change. For the stated incident, the decisive observation is stratify historical samples by day type and examine whether the observed difference is expected seasonality.

C:

That diagnostic evidence 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. For the stated incident, the decisive observation is stratify historical samples by day type and examine whether the observed difference is expected seasonality.

D:

That diagnostic evidence is directed at a different drift detection and lakehouse monitoring situation: A time-series monitor uses a string-formatted date that cannot be reliably converted to timestamps and silently groups most rows into an unknown bucket. For the stated incident, the decisive observation is stratify historical samples by day type and examine whether the observed difference is expected seasonality.

Certified Machine Learning Professional Practice Tests