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 91

Question 900

A production ML review contains this situation: An engineer uses only production replay data to validate a code change and exposes customer events in an unrestricted test workspace. What is the most material immediate risk in this situation?

  1. A hidden offset causes training-serving skew and potential future-data leakage.
  2. Invalid standardized values contaminate model input vectors or crash scoring.
  3. Small logic errors require slow integration jobs for every test iteration.
  4. Sensitive events leak into lower-trust test assets while making debugging harder.

Explanation

Correct Answer

D:

This consequence follows from the specific unresolved condition. Sensitive events leak into lower-trust test assets while making debugging harder. The causal constraint is: Test stages need appropriate data classification and isolation, not just increasingly realistic inputs.

Incorrect Answers

A:

That direct consequence 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. The more immediate risk here is sensitive events leak into lower-trust test assets while making debugging harder.

B:

That direct consequence is directed at a different validation testing situation: A preprocessing function divides by a standard deviation and returns infinity for a constant numeric column. The more immediate risk here is sensitive events leak into lower-trust test assets while making debugging harder.

C:

That direct consequence is directed at a different validation testing situation: A team hides all preprocessing logic inside one long notebook, making it hard to test independently without starting a Spark cluster. The more immediate risk here is sensitive events leak into lower-trust test assets while making debugging harder.

Question 901

Review this production model incident: A team has accurate inference logs but its monitoring job never refreshes computed drift metrics after a table schema change. What is the central engineering constraint behind this behavior?

  1. Time-series profile configuration needs a valid temporal column with reliable timestamp semantics.
  2. Alert payloads should carry sufficient metric and lineage context for safe triage.
  3. Missing-value changes can be a quality or distribution signal and should not be silently discarded from monitored populations.
  4. Monitoring pipelines require scheduled computation and output-health checks, not merely raw event storage.

Explanation

Correct Answer

D:

The technical constraint is specific to the reported failure. Monitoring pipelines require scheduled computation and output-health checks, not merely raw event storage. To test it, compare inference-table last-seen with metric-table last-refresh and schema errors in profiling jobs.

Incorrect Answers

A:

That underlying principle 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. The current incident instead turns on monitoring pipelines require scheduled computation and output-health checks, not merely raw event storage.

B:

That underlying principle 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. The current incident instead turns on monitoring pipelines require scheduled computation and output-health checks, not merely raw event storage.

C:

That underlying principle 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 current incident instead turns on monitoring pipelines require scheduled computation and output-health checks, not merely raw event storage.

Question 902

The engineering team encounters the following issue: An ML engineer logs a calibration plot as a string metric, then downstream reviewers cannot inspect the visualization or its input version. Which technical principle most directly explains the root of the issue?

  1. Custom MLflow model packaging must include declared compatible dependencies for the independent serving environment.
  2. Parent and nested child runs encode experiment-to-trial relationships while preserving each trial's parameters and metrics.
  3. A custom MLflow PyFunc's input contract and online feature lookups must be designed for request-time availability and governance.
  4. Complex objects such as plots and reports belong in versioned MLflow artifacts rather than scalar metrics.

Explanation

Correct Answer

D:

The technical constraint is specific to the reported failure. Complex objects such as plots and reports belong in versioned MLflow artifacts rather than scalar metrics. To test it, inspect the run's metric keys versus artifact store and recover the expected plot file.

Incorrect Answers

A:

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 complex objects such as plots and reports belong in versioned MLflow artifacts rather than scalar metrics.

B:

That underlying principle is directed at a different advanced mlflow usage situation: An experiment tunes 40 candidates but logs each trial as an unrelated root MLflow run, so reviewers cannot reconstruct which search produced a winner. The current incident instead turns on complex objects such as plots and reports belong in versioned MLflow artifacts rather than scalar metrics.

C:

That underlying principle is directed at a different advanced mlflow usage 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. The current incident instead turns on complex objects such as plots and reports belong in versioned MLflow artifacts rather than scalar metrics.

Question 903

A production ML review contains this situation: A nightly scoring feed drops all null-feature rows before calculating drift, making missingness jump invisible. Which check shows that this particular problem has been resolved?

  1. The profile generates expected current-table completeness and distribution statistics without inventing prediction metadata.
  2. A synthetic increase in missing values raises the intended data-quality signal at unchanged non-null values.
  3. A synthetic region-only failure triggers the scoped alert without misclassifying healthy regions.
  4. An injected shift remains visible against the preserved baseline after repeated monitor runs.

Explanation

Correct Answer

B:

This verification measures the required result rather than just process liveness. A synthetic increase in missing values raises the intended data-quality signal at unchanged non-null values. It confirms whether the targeted action succeeded: monitor missingness explicitly alongside supported drift statistics and repair the upstream filter if needed.

Incorrect Answers

A:

That acceptance test 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. Here the actual success criterion is a synthetic increase in missing values raises the intended data-quality signal at unchanged non-null values.

C:

That acceptance test is directed at a different drift detection and lakehouse monitoring situation: An alert query uses one global transaction-failure count and masks a complete outage in a small high-value region. Here the actual success criterion is a synthetic increase in missing values raises the intended data-quality signal at unchanged non-null values.

D:

That acceptance test 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. Here the actual success criterion is a synthetic increase in missing values raises the intended data-quality signal at unchanged non-null values.

Question 904

A production ML review contains this situation: A team records experiments but has no controlled path from a selected registered model to scheduled scoring jobs. What is the most material immediate risk in this situation?

  1. Production inference can access unrelated protected data or train on unintended tables.
  2. A healthy deployed job crashes on missing fields or silently reads wrong defaults.
  3. The live model logic diverges from tested code and cannot be reproduced during an incident.
  4. The wrong experiment artifact may be used in production because lifecycle stages are disconnected.

Explanation

Correct Answer

D:

This consequence follows from the specific unresolved condition. The wrong experiment artifact may be used in production because lifecycle stages are disconnected. The causal constraint is: Tracking, registry, jobs and serving are distinct lifecycle capabilities that must be linked by artifact identity.

Incorrect Answers

A:

That direct consequence 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 more immediate risk here is the wrong experiment artifact may be used in production because lifecycle stages are disconnected.

B:

That direct consequence 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 more immediate risk here is the wrong experiment artifact may be used in production because lifecycle stages are disconnected.

C:

That direct consequence 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. The more immediate risk here is the wrong experiment artifact may be used in production because lifecycle stages are disconnected.

Question 905

Review this production model incident: A notebook uses the MLflow Deployments SDK to send a column-major payload to a custom model endpoint expecting a different documented dataframe schema. What evidence would best distinguish the actual fault from neighboring ML concerns?

  1. Compare serialized request JSON field names, batch dimensions and the model signature for a failing fixture.
  2. Scan the serialized custom model artifact and logs for token material and audit its access history.
  3. Review endpoint change history, CI deployment commits and the order of conflicting updates.
  4. Replay valid, missing and nonnumeric fixture fields against the PyFunc predict interface.

Explanation

Correct Answer

A:

This is the most discriminating check for the observed symptoms. Compare serialized request JSON field names, batch dimensions and the model signature for a failing fixture. The underlying technical issue is that serving inference payloads must conform to the endpoint and model's accepted request/response schema.

Incorrect Answers

B:

That diagnostic evidence 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. For the stated incident, the decisive observation is compare serialized request JSON field names, batch dimensions and the model signature for a failing fixture.

C:

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 serialized request JSON field names, batch dimensions and the model signature for a failing fixture.

D:

That diagnostic evidence 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. For the stated incident, the decisive observation is compare serialized request JSON field names, batch dimensions and the model signature for a failing fixture.

Question 906

The engineering team encounters the following issue: A time-ordered customer-retention dataset includes events from the future, yet a developer randomly cross-validates across time and then claims a forward-looking forecast is unbiased. What direct consequence should the owner prioritize if no fix is made?

  1. Future information leaks into training folds and overstates forecast usefulness.
  2. A per-row driver bottleneck creates lag and breaks recovery guarantees.
  3. No training-derived category mapping exists for the requested transformation.
  4. Predictions change because the deployed estimator receives unscaled columns it was never trained on.

Explanation

Correct Answer

A:

This consequence follows from the specific unresolved condition. Future information leaks into training folds and overstates forecast usefulness. The causal constraint is: Temporal evaluation must respect what data would have been available at the forecast origin, not simply use random folds.

Incorrect Answers

B:

That direct consequence is directed at a different using spark ml situation: An energy plant needs one model prediction for every new sensor micro-batch but proposes a synchronous REST call per row from a driver collect loop. The more immediate risk here is future information leaks into training folds and overstates forecast usefulness.

C:

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 future information leaks into training folds and overstates forecast usefulness.

D:

That direct consequence 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 more immediate risk here is future information leaks into training folds and overstates forecast usefulness.

Question 907

In an enterprise ML workflow, the reported issue is: An ML engineer manually compares two logistic-regression regularization values on a single holdout but has no reusable SparkML parameter-search plan. What technical distinction is essential to this investigation?

  1. Real-time serving requires online-accessible feature values and an inference route designed for request-time latency.
  2. Tokenizer is a Transformer and applies transform directly without a separate learned fit step.
  3. Ranking quality and operating threshold quality are distinct; precision and recall depend on the chosen cutoff.
  4. CrossValidator and a ParamGridBuilder can evaluate estimator parameter maps across controlled folds when the validation design permits it.

Explanation

Correct Answer

D:

The technical constraint is specific to the reported failure. CrossValidator and a ParamGridBuilder can evaluate estimator parameter maps across controlled folds when the validation design permits it. To test it, inspect the estimator ParamGridBuilder maps, evaluator metric and fold configuration used for the claimed search.

Incorrect Answers

A:

That underlying principle is directed at a different using spark ml situation: A mobile app requires thousands of concurrent low-latency scores with online features, but a team plans to query an offline historical feature Delta table for every request. The current incident instead turns on crossValidator and a ParamGridBuilder can evaluate estimator parameter maps across controlled folds when the validation design permits it.

B:

That underlying principle 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 current incident instead turns on crossValidator and a ParamGridBuilder can evaluate estimator parameter maps across controlled folds when the validation design permits it.

C:

That underlying principle is directed at a different using spark ml situation: A binary classifier ranks risky cases well but sends too many alerts at a default 0.5 decision threshold. The current incident instead turns on crossValidator and a ParamGridBuilder can evaluate estimator parameter maps across controlled folds when the validation design permits it.

Question 908

Consider the following fictional Databricks production case: A release pipeline runs development unit tests against a different dependency image from the one deployed to production. Which observation most directly tests the suspected failure boundary?

  1. Compare image digests and dependency manifests across unit, integration and deployment stages.
  2. Inspect function outputs for null, zero and positive synthetic inputs against the documented business rule.
  3. Compare class-index mappings and positive/negative fixture outputs from training to serving.
  4. Identify deterministic data transformations entangled with session setup and filesystem side effects.

Explanation

Correct Answer

A:

This is the most discriminating check for the observed symptoms. Compare image digests and dependency manifests across unit, integration and deployment stages. The underlying technical issue is that release-stage testing must validate the actual artifact and dependency environment being promoted.

Incorrect Answers

B:

That diagnostic evidence 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. For the stated incident, the decisive observation is compare image digests and dependency manifests across unit, integration and deployment stages.

C:

That diagnostic evidence is directed at a different validation testing situation: An end-to-end validation uses only a synthetic positive label and fails to detect a swapped positive/negative class mapping in inference. For the stated incident, the decisive observation is compare image digests and dependency manifests across unit, integration and deployment stages.

D:

That diagnostic evidence is directed at a different validation testing situation: A team hides all preprocessing logic inside one long notebook, making it hard to test independently without starting a Spark cluster. For the stated incident, the decisive observation is compare image digests and dependency manifests across unit, integration and deployment stages.

Question 909

In an enterprise ML workflow, the reported issue is: A platform engineer creates a custom serving endpoint manually and assumes the exact settings can be recovered after an accidental deletion. Before modifying the pipeline, which evidence should be collected first?

  1. Inspect rate-limit response headers, client retry timeline and duplicate request identifiers.
  2. Compare current endpoint settings with source-controlled deployment configuration and documented backup state.
  3. Compare serialized request JSON field names, batch dimensions and the model signature for a failing fixture.
  4. Inspect model artifact source, planned three-level Unity Catalog name and effective registration permissions.

Explanation

Correct Answer

B:

This is the most discriminating check for the observed symptoms. Compare current endpoint settings with source-controlled deployment configuration and documented backup state. The underlying technical issue is that repeatable endpoint deployment should preserve a controlled configuration definition and registered model identity.

Incorrect Answers

A:

That diagnostic evidence is directed at a different custom model serving situation: A real-time client retries every 429 rate-limit error immediately in an unbounded loop and multiplies load on the serving endpoint. For the stated incident, the decisive observation is compare current endpoint settings with source-controlled deployment configuration and documented backup state.

C:

That diagnostic evidence is directed at a different custom model serving situation: A notebook uses the MLflow Deployments SDK to send a column-major payload to a custom model endpoint expecting a different documented dataframe schema. For the stated incident, the decisive observation is compare current endpoint settings with source-controlled deployment configuration and documented backup state.

D:

That diagnostic evidence is directed at a different custom model serving situation: A research group wants to register a custom classification model in Unity Catalog but uses a local path as its complete model identity and has no governed model name. For the stated incident, the decisive observation is compare current endpoint settings with source-controlled deployment configuration and documented backup state.

Question 910

Consider the following fictional Databricks production case: An analyst loads a fitted LogisticRegressionModel but calls fit on it for every scored batch rather than transform. What consequence most specifically follows from leaving the issue unchanged?

  1. Complexity and cost increase while the tiny fit becomes slower rather than faster.
  2. Deployment performance may collapse on customers never seen during optimization.
  3. Unintended retraining or API failures compromise reproducibility of batch scores.
  4. A rare new category can fail an entire scoring batch rather than produce a controlled result.

Explanation

Correct Answer

C:

This consequence follows from the specific unresolved condition. Unintended retraining or API failures compromise reproducibility of batch scores. The causal constraint is: A fitted Model is a Transformer for scoring; retraining belongs to the corresponding Estimator.

Incorrect Answers

A:

That direct consequence is directed at a different using spark ml situation: A laboratory runs a linear regression every quarter on only 280 clean observations and proposes a 48-worker Spark cluster to reduce a two-second local fit. The more immediate risk here is unintended retraining or API failures compromise reproducibility of batch scores.

B:

That direct consequence 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 more immediate risk here is unintended retraining or API failures compromise reproducibility of batch scores.

D:

That direct consequence 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 more immediate risk here is unintended retraining or API failures compromise reproducibility of batch scores.

Certified Machine Learning Professional Practice Tests