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 11

Question 100

Consider the following fictional Databricks production case: An engineering group duplicates a validation helper across six notebooks, and two copies enforce outdated threshold values. What underlying principle determines the most appropriate interpretation?

  1. Unit tests belong on controlled synthetic inputs before integrations, and production smoke tests do not replace them.
  2. Unit tests should exercise edge cases and expected output contracts, not just the happy-path fixture.
  3. Shared reusable validation code can prevent silent divergence between independent notebook copies.
  4. Model artifact identity must be checked through registry promotion and endpoint deployment, not inferred from job success.

Explanation

Correct Answer

C:

The technical constraint is specific to the reported failure. Shared reusable validation code can prevent silent divergence between independent notebook copies. To test it, compare helper source hashes and test assertions across consuming notebooks.

Incorrect Answers

A:

That underlying principle is directed at a different validation testing situation: A developer changes a feature transform in a notebook and directly uses production data as the only test case. The current incident instead turns on shared reusable validation code can prevent silent divergence between independent notebook copies.

B:

That underlying principle is directed at a different validation testing situation: A feature function maps a null purchase amount to zero without distinguishing missing observations, and a notebook unit test covers only positive amounts. The current incident instead turns on shared reusable validation code can prevent silent divergence between independent notebook copies.

D:

That underlying principle is directed at a different validation testing situation: A model version is registered but the deployment job points to an old alias after promotion and continues serving last week's model. The current incident instead turns on shared reusable validation code can prevent silent divergence between independent notebook copies.

Question 101

The engineering team encounters the following issue: A low-latency feature table uses external customer names as lookup keys; names change and are not unique. Which experiment most directly demonstrates a successful fix?

  1. Renaming a display label does not alter the entity's online lookup result.
  2. A restart restores feature values consistent with the pre-restart control dataset.
  3. All registered consumer models pass feature compatibility and expected-output tests against the promoted version.
  4. A fixture with three feature revisions produces exactly one eligible feature row per prediction time.

Explanation

Correct Answer

A:

This verification measures the required result rather than just process liveness. Renaming a display label does not alter the entity's online lookup result. It confirms whether the targeted action succeeded: use a stable governed primary key and update feature publication and serving lookup mappings.

Incorrect Answers

B:

That acceptance test is directed at a different advanced feature store concepts situation: A business deploys a model whose features are computed from a stream in memory only and disappear when its compute cluster restarts. Here the actual success criterion is renaming a display label does not alter the entity's online lookup result.

C:

That acceptance test 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. Here the actual success criterion is renaming a display label does not alter the entity's online lookup result.

D:

That acceptance test is directed at a different advanced feature store concepts situation: A training dataset combines a feature table with multiple timestamped rows per device using an equality join on device ID only. Here the actual success criterion is renaming a display label does not alter the entity's online lookup result.

Question 102

Review this production model incident: A monitoring dashboard reports a statistically significant tiny difference after one million observations, and the team immediately treats it as operationally material drift. Which failure risk follows most closely from the unresolved behavior?

  1. Alert fatigue grows from trivial shifts that do not affect decisions or predictions.
  2. Missing historical windows are treated as evidence of zero incidents or zero data change.
  3. The monitoring pipeline either floods the SOC or ignores new material shifts.
  4. The live population drifts far from model training even though daily changes remain modest.

Explanation

Correct Answer

A:

This consequence follows from the specific unresolved condition. Alert fatigue grows from trivial shifts that do not affect decisions or predictions. The causal constraint is: Statistical significance and practical effect size differ; large samples can make negligible shifts detectable.

Incorrect Answers

B:

That direct consequence 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. The more immediate risk here is alert fatigue grows from trivial shifts that do not affect decisions or predictions.

C:

That direct consequence 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. The more immediate risk here is alert fatigue grows from trivial shifts that do not affect decisions or predictions.

D:

That direct consequence 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. The more immediate risk here is alert fatigue grows from trivial shifts that do not affect decisions or predictions.

Question 103

In an enterprise ML workflow, the reported issue is: A customer-risk feature needs a ratio of current debt to income, but online serving recomputes it differently from the training pipeline. What likely operational or model-quality harm does this issue create?

  1. One purchase increases the spending feature twice, affecting downstream risk scores.
  2. Training-serving skew silently changes the meaning of risk thresholds.
  3. Historical training datasets cannot be faithfully reconstructed after the overwrite.
  4. An ancient measurement can influence a current score as if it were fresh evidence.

Explanation

Correct Answer

B:

This consequence follows from the specific unresolved condition. Training-serving skew silently changes the meaning of risk thresholds. The causal constraint is: On-demand feature definitions should apply consistent logic and missing/zero-denominator handling across contexts.

Incorrect Answers

A:

That direct consequence is directed at a different advanced feature store concepts situation: A real-time feature job updates user purchase totals without checking whether upstream transaction events are delivered twice. The more immediate risk here is training-serving skew silently changes the meaning of risk thresholds.

C:

That direct consequence 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 more immediate risk here is training-serving skew silently changes the meaning of risk thresholds.

D:

That direct consequence 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 more immediate risk here is training-serving skew silently changes the meaning of risk thresholds.

Question 104

Consider the following fictional Databricks production case: A team updates a shared on-demand feature function without version control and unexpectedly changes both batch retraining and online serving behavior. Which implementation is most appropriate for the stated incident?

  1. Apply the approved availability cutoff and exclude features not accessible when the decision was made.
  2. Define an owned Feature Engineering Client workflow with scheduled computation and versioned feature outputs.
  3. Use stable checkpoints and an idempotent feature update design for replayed source events.
  4. Promote a versioned feature definition with backward-compatibility tests and controlled rollout.

Explanation

Correct Answer

D:

This corrects the relevant failure boundary instead of merely hiding the symptom. Promote a versioned feature definition with backward-compatibility tests and controlled rollout. The issue matters because several models change their effective input distributions without deliberate retraining or review.

Incorrect Answers

A:

That corrective action is directed at a different advanced feature store concepts situation: A retailer's features arrive two hours late, and offline training uses event time alone even though the online system could not have seen those late arrivals at prediction time. The relevant corrective action here is promote a versioned feature definition with backward-compatibility tests and controlled rollout.

B:

That corrective action is directed at a different advanced feature store concepts situation: A team manually reruns a feature notebook each week before training; feature definitions change without an execution history or stable destination. The relevant corrective action here is promote a versioned feature definition with backward-compatibility tests and controlled rollout.

C:

That corrective action is directed at a different advanced feature store concepts situation: An online behavioral feature counter consumes a streaming source but does not retain checkpoint state after worker restarts. The relevant corrective action here is promote a versioned feature definition with backward-compatibility tests and controlled rollout.

Question 105

A production ML review contains this 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. What production-safe change best matches the evidence?

  1. Record a resume lineage link and preserve distinct nested trials for both original and continued runs.
  2. Record the selected child run and model artifact identity in the parent summary metadata.
  3. Standardize metric naming and units, version the computation and recalculate a comparable ranking.
  4. Log required dependencies and portable model code with the PyFunc artifact and redeploy a validated environment.

Explanation

Correct Answer

C:

This corrects the relevant failure boundary instead of merely hiding the symptom. Standardize metric naming and units, version the computation and recalculate a comparable ranking. The issue matters because a model can win solely because its reported metric uses a different scale.

Incorrect Answers

A:

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 standardize metric naming and units, version the computation and recalculate a comparable ranking.

B:

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 standardize metric naming and units, version the computation and recalculate a comparable ranking.

D:

That corrective action 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 relevant corrective action here is standardize metric naming and units, version the computation and recalculate a comparable ranking.

Question 106

A production ML review contains this situation: A monitor owner writes a custom metric that logs unaggregated account-level health data in a broadly shared results table. Which statement best explains the failure mode?

  1. Alert windows and persistence conditions must align with the service objective to avoid transient false positives.
  2. Aggregate performance can conceal failure in important subpopulations and lifecycle stages.
  3. Production input should sometimes be compared to a retained training reference, not only recent windows.
  4. Custom monitoring outputs should preserve necessary aggregate signals without exposing unnecessary entity-level sensitive data.

Explanation

Correct Answer

D:

The technical constraint is specific to the reported failure. Custom monitoring outputs should preserve necessary aggregate signals without exposing unnecessary entity-level sensitive data. To test it, review the metric query's output grain, fields and result-table access against data classification.

Incorrect Answers

A:

That underlying principle 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 current incident instead turns on custom monitoring outputs should preserve necessary aggregate signals without exposing unnecessary entity-level sensitive data.

B:

That underlying principle is directed at a different drift detection and lakehouse monitoring situation: A recommender reports stable overall accuracy while click-through prediction quality for first-time users deteriorates sharply. The current incident instead turns on custom monitoring outputs should preserve necessary aggregate signals without exposing unnecessary entity-level sensitive data.

C:

That underlying principle 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. The current incident instead turns on custom monitoring outputs should preserve necessary aggregate signals without exposing unnecessary entity-level sensitive data.

Question 107

Review this production model incident: A model's feature generation step overwrites all feature-table history daily even though time-aware training requires earlier snapshots. What end-to-end verification is most persuasive here?

  1. A fixture with three feature revisions produces exactly one eligible feature row per prediction time.
  2. A past labeled event can still retrieve the correct historical feature state.
  3. A restart restores feature values consistent with the pre-restart control dataset.
  4. Load tests meet request-time latency while documented fallback values remain semantically valid.

Explanation

Correct Answer

B:

This verification measures the required result rather than just process liveness. A past labeled event can still retrieve the correct historical feature state. It confirms whether the targeted action succeeded: use an update strategy that preserves required historical feature states and governance metadata.

Incorrect Answers

A:

That acceptance test is directed at a different advanced feature store concepts situation: A training dataset combines a feature table with multiple timestamped rows per device using an equality join on device ID only. Here the actual success criterion is a past labeled event can still retrieve the correct historical feature state.

C:

That acceptance test is directed at a different advanced feature store concepts situation: A business deploys a model whose features are computed from a stream in memory only and disappear when its compute cluster restarts. Here the actual success criterion is a past labeled event can still retrieve the correct historical feature state.

D:

That acceptance test is directed at a different advanced feature store concepts situation: A streaming recommender's request-time feature function calls a slow third-party API synchronously on every prediction. Here the actual success criterion is a past labeled event can still retrieve the correct historical feature state.

Question 108

A production ML review contains this situation: An organization has reliable model serving but never archives feature definitions or experiment parameters and cannot reproduce predictions after drift. Which diagnostic check provides the strongest direct evidence?

  1. Trace a sample production prediction backward through model, feature snapshot and logged run metadata.
  2. Inspect environment-specific data-source references and effective service-identity permissions.
  3. Compare the logged training environment, lockfile and production model-load dependency versions.
  4. Compare required feature schema in the release with deployed table and endpoint contracts.

Explanation

Correct Answer

A:

This is the most discriminating check for the observed symptoms. Trace a sample production prediction backward through model, feature snapshot and logged run metadata. The underlying technical issue is that lifecycle reproducibility spans source data, feature definitions, training configuration, model artifact and serving identity.

Incorrect Answers

B:

That diagnostic evidence 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. For the stated incident, the decisive observation is trace a sample production prediction backward through model, feature snapshot and logged run metadata.

C:

That diagnostic evidence 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. For the stated incident, the decisive observation is trace a sample production prediction backward through model, feature snapshot and logged run metadata.

D:

That diagnostic evidence 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. For the stated incident, the decisive observation is trace a sample production prediction backward through model, feature snapshot and logged run metadata.

Question 109

The engineering team encounters the following issue: A notebook's label encoder produces a different category order depending on an unordered Python set, but tests assert only output length. What direct consequence should the owner prioritize if no fix is made?

  1. A library compatibility defect escapes despite green tests against an older environment.
  2. Predictions drift between restarts because identical labels occupy different vector positions.
  3. A model that looks accurate offline cannot be called successfully by production clients.
  4. Production jobs waste resources or mutate test artifacts during business scoring.

Explanation

Correct Answer

B:

This consequence follows from the specific unresolved condition. Predictions drift between restarts because identical labels occupy different vector positions. The causal constraint is: Unit tests should verify reproducible content and stable mappings rather than shape alone.

Incorrect Answers

A:

That direct consequence is directed at a different validation testing situation: A release pipeline runs development unit tests against a different dependency image from the one deployed to production. The more immediate risk here is predictions drift between restarts because identical labels occupy different vector positions.

C:

That direct consequence is directed at a different validation testing situation: A churn feature job succeeds and a classifier achieves acceptable F1, but the deployed endpoint returns HTTP 400 because request column names differ. The more immediate risk here is predictions drift between restarts because identical labels occupy different vector positions.

D:

That direct consequence is directed at a different validation testing situation: An ML project stores test files directly in each production notebook and execution of a deployed notebook inadvertently reruns expensive tests. The more immediate risk here is predictions drift between restarts because identical labels occupy different vector positions.

Question 110

The engineering team encounters the following issue: A monitor is pointed at a Unity Catalog table but the automation identity lacks the privileges needed to generate profile outputs. Which technical principle most directly explains the root of the issue?

  1. Monitor creation and ongoing metric writes depend on governed resource access and configured output locations.
  2. Monitoring granularity cannot exceed the information preserved in source rows and ingestion cadence.
  3. Reference populations should match relevant seasonality and business context when interpreting drift.
  4. Observability starts with traceable, appropriately governed prediction logging before statistical analysis.

Explanation

Correct Answer

A:

The technical constraint is specific to the reported failure. Monitor creation and ongoing metric writes depend on governed resource access and configured output locations. To test it, inspect effective owner permissions, catalog/schema access and creation error logs for the target table.

Incorrect Answers

B:

That underlying principle 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. The current incident instead turns on monitor creation and ongoing metric writes depend on governed resource access and configured output locations.

C:

That underlying principle is directed at a different drift detection and lakehouse monitoring situation: An online feature monitor compares weekend shopping to weekday reference data and treats expected weekend behavior as a model failure. The current incident instead turns on monitor creation and ongoing metric writes depend on governed resource access and configured output locations.

D:

That underlying principle is directed at a different drift detection and lakehouse monitoring situation: A serving endpoint appears healthy but nobody records model version, request identifier or prediction value, so a drift incident cannot be reconstructed. The current incident instead turns on monitor creation and ongoing metric writes depend on governed resource access and configured output locations.

Certified Machine Learning Professional Practice Tests