Databricks Certified Machine Learning Professional Practice Test 31
Question 300
A production ML review contains this situation: A recommender experiment computes all evaluation metrics on training interactions and reports the result as generalization to new customers. Which diagnostic check provides the strongest direct evidence?
- Compare training customer IDs with disjoint evaluation users or future interactions and inspect overlap.
- Compare the original StringIndexer type with the fitted StringIndexerModel and inspect its label mapping.
- Inspect micro-batch volume, supported streaming model transforms and the proposed driver-call throughput.
- Inspect evaluator.isLargerBetter or equivalent metric semantics alongside the ordered candidate RMSE values.
Explanation
Correct Answer
A:This is the most discriminating check for the observed symptoms. Compare training customer IDs with disjoint evaluation users or future interactions and inspect overlap. The underlying technical issue is that training-set fit does not establish out-of-sample predictive quality or cold-start behavior.
Incorrect Answers
B:That diagnostic evidence 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. For the stated incident, the decisive observation is compare training customer IDs with disjoint evaluation users or future interactions and inspect overlap.
C:That diagnostic evidence 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. For the stated incident, the decisive observation is compare training customer IDs with disjoint evaluation users or future interactions and inspect overlap.
D:That diagnostic evidence is directed at a different using spark ml situation: A SparkML grid-search experiment selects the model with the largest error metric even though the evaluator reports RMSE to minimize. For the stated incident, the decisive observation is compare training customer IDs with disjoint evaluation users or future interactions and inspect overlap.
Question 301
A production ML review contains this 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. What production-safe change best matches the evidence?
- Normalize and validate a supported timestamp field before applying the configured temporal profile.
- Improve authorized logging and table design before configuring fine-grained inference time-series analysis.
- Add an appropriately sustained alert condition or window aggregate instead of a one-minute peak trigger.
- Add delayed-ground-truth performance tracking alongside existing drift metrics and health signals.
Explanation
Correct Answer
A:This corrects the relevant failure boundary instead of merely hiding the symptom. Normalize and validate a supported timestamp field before applying the configured temporal profile. The issue matters because daily drift statistics reflect malformed time buckets rather than actual event periods.
Incorrect Answers
B:That corrective action 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 relevant corrective action here is normalize and validate a supported timestamp field before applying the configured temporal profile.
C:That corrective action is directed at a different drift detection and lakehouse monitoring situation: A monitor alerts whenever a ratio exceeds 0.3 for a single minute, although normal traffic produces brief spikes and operations require ten-minute persistence. The relevant corrective action here is normalize and validate a supported timestamp field before applying the configured temporal profile.
D:That corrective action is directed at a different drift detection and lakehouse monitoring situation: A risk service measures feature drift but neglects observed-label performance and continues serving an accurate-looking yet ineffective model. The relevant corrective action here is normalize and validate a supported timestamp field before applying the configured temporal profile.
Question 302
The engineering team encounters the following issue: A global model predicts late deliveries accurately overall, but all mistakes occur at one small coastal depot and the team never slices its results by site. Which technical principle most directly explains the root of the issue?
- Reference populations should match relevant seasonality and business context when interpreting drift.
- Serving memory headroom and resource trends are necessary to detect OOM risk in large-model releases.
- Slicing on operationally meaningful locations can reveal concentrated failures hidden in the global metric.
- Alert payloads should carry sufficient metric and lineage context for safe triage.
Explanation
Correct Answer
C:The technical constraint is specific to the reported failure. Slicing on operationally meaningful locations can reveal concentrated failures hidden in the global metric. To test it, compare model errors and sample sizes by depot against the aggregate baseline.
Incorrect Answers
A: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 slicing on operationally meaningful locations can reveal concentrated failures hidden in the global metric.
B:That underlying principle is directed at a different drift detection and lakehouse monitoring situation: A new model version uses twice the memory per replica, but capacity monitoring tracks only CPU and crash counts. The current incident instead turns on slicing on operationally meaningful locations can reveal concentrated failures hidden in the global metric.
D: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 slicing on operationally meaningful locations can reveal concentrated failures hidden in the global metric.
Question 303
A production ML review contains this situation: A company operates development and production models in one workspace under the same broad service account and frequently overwrites production tables during experiments. What is the most material immediate risk in this situation?
- A release fails when a renamed or unsupported field is assumed to work unchanged.
- The deployed resources exist but cannot run due to missing experiment or model access.
- A developer's experiment can alter production feature tables or serving configuration.
- Manual drift creates unreproducible endpoint permissions or traffic settings.
Explanation
Correct Answer
C:This consequence follows from the specific unresolved condition. A developer's experiment can alter production feature tables or serving configuration. The causal constraint is: Environment architecture should isolate access, data destinations and ownership for different stages.
Incorrect Answers
A:That direct consequence is directed at a different environment architectures situation: An ML platform moves its configuration from older Databricks Asset Bundles terminology to newer Declarative Automation Bundles references and assumes every resource schema stayed identical. The more immediate risk here is a developer's experiment can alter production feature tables or serving configuration.
B:That direct consequence is directed at a different environment architectures situation: A continuous-delivery job deploys a notebook change through a bundle but skips validation of referenced experiment paths and job permissions. The more immediate risk here is a developer's experiment can alter production feature tables or serving configuration.
D:That direct consequence is directed at a different environment architectures situation: A model serving endpoint is created manually in the UI and every staging deployment differs subtly from production because no deployment definition is saved. The more immediate risk here is a developer's experiment can alter production feature tables or serving configuration.
Question 304
The engineering team encounters the following issue: An experiment tunes 40 candidates but logs each trial as an unrelated root MLflow run, so reviewers cannot reconstruct which search produced a winner. Which technical principle most directly explains the root of the issue?
- Parent and nested child runs encode experiment-to-trial relationships while preserving each trial's parameters and metrics.
- MLflow run-level logging should attach parameters and evaluated metrics to the corresponding candidate run.
- The model's request-time feature contract should be compared with training-time feature semantics to avoid unintended skew.
- Experiment tracking must minimize sensitive data and enforce artifact permissions rather than treating all model logs as harmless.
Explanation
Correct Answer
A:The technical constraint is specific to the reported failure. Parent and nested child runs encode experiment-to-trial relationships while preserving each trial's parameters and metrics. To test it, inspect parent_run_id tags, candidate run IDs and the experiment's tracked search configuration.
Incorrect Answers
B:That underlying principle is directed at a different advanced mlflow usage situation: A training notebook reports F1 for several models but only logs the final model's parameters in MLflow, leaving metrics and hyperparameters disconnected. The current incident instead turns on parent and nested child runs encode experiment-to-trial relationships while preserving each trial's parameters and metrics.
C:That underlying principle 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. The current incident instead turns on parent and nested child runs encode experiment-to-trial relationships while preserving each trial's parameters and metrics.
D:That underlying principle is directed at a different advanced mlflow usage situation: A regulated analytics team uploads full customer identifiers inside MLflow model artifacts during troubleshooting. The current incident instead turns on parent and nested child runs encode experiment-to-trial relationships while preserving each trial's parameters and metrics.
Question 305
Review this production model incident: A feature-refresh task writes rows with event time in local timezone while the training join assumes UTC; unit tests of each component pass. Which failure risk follows most closely from the unresolved behavior?
- Production jobs waste resources or mutate test artifacts during business scoring.
- Predictions drift between restarts because identical labels occupy different vector positions.
- All units pass while the production workflow fails with a schema mismatch.
- A hidden offset causes training-serving skew and potential future-data leakage.
Explanation
Correct Answer
D:This consequence follows from the specific unresolved condition. A hidden offset causes training-serving skew and potential future-data leakage. The causal constraint is: Cross-component tests must validate shared time semantics and feature availability throughout the ML pipeline.
Incorrect Answers
A: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 a hidden offset causes training-serving skew and potential future-data leakage.
B:That direct consequence 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. The more immediate risk here is a hidden offset causes training-serving skew and potential future-data leakage.
C:That direct consequence is directed at a different validation testing situation: A team unit-tests each model component independently but its feature table and serving endpoint disagree on column names. The more immediate risk here is a hidden offset causes training-serving skew and potential future-data leakage.
Question 306
A production ML review contains this situation: An IoT classifier passes raw text categories directly into VectorAssembler ahead of StringIndexer and OneHotEncoder, generating incompatible vector inputs. Which statement best explains the failure mode?
- A SparkML Pipeline requires transformer stages in an order that produces the input types expected by later stages.
- Accuracy alone is misleading under extreme class imbalance; minority precision, recall and PR metrics carry critical information.
- Temporal evaluation must respect what data would have been available at the forecast origin, not simply use random folds.
- Distributed batch inference can apply a saved SparkML PipelineModel directly to a DataFrame without collecting every row.
Explanation
Correct Answer
A:The technical constraint is specific to the reported failure. A SparkML Pipeline requires transformer stages in an order that produces the input types expected by later stages. To test it, inspect intermediate stage schemas and the inputCol/outputCol contract immediately before vector assembly.
Incorrect Answers
B:That underlying principle 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 current incident instead turns on a SparkML Pipeline requires transformer stages in an order that produces the input types expected by later stages.
C:That underlying principle is directed at a different using spark ml situation: 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. The current incident instead turns on a SparkML Pipeline requires transformer stages in an order that produces the input types expected by later stages.
D:That underlying principle is directed at a different using spark ml situation: A logistics model must score 60 million daily routes already in Delta but the scoring script collects each route into Python before calling predict. The current incident instead turns on a SparkML Pipeline requires transformer stages in an order that produces the input types expected by later stages.
Question 307
In an enterprise ML workflow, the reported issue is: A serving client calls the REST endpoint expecting one number but the custom PyFunc returns a structured list of prediction and confidence fields. Which change addresses the real cause without undermining other requirements?
- Route changes through a single approved configuration source and verify the active endpoint after each change.
- Update the caller to handle the supported structured response and validate required keys and types.
- Grant only the required production deployment/model access to a dedicated controlled service identity.
- Log the supported custom PyFunc model and register it to an authorized governed model name.
Explanation
Correct Answer
B:This corrects the relevant failure boundary instead of merely hiding the symptom. Update the caller to handle the supported structured response and validate required keys and types. The issue matters because clients throw parsing errors or accidentally interpret confidence as the prediction.
Incorrect Answers
A:That corrective action 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. The relevant corrective action here is update the caller to handle the supported structured response and validate required keys and types.
C:That corrective action 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. The relevant corrective action here is update the caller to handle the supported structured response and validate required keys and types.
D:That corrective action 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. The relevant corrective action here is update the caller to handle the supported structured response and validate required keys and types.
Question 308
A production ML review contains this situation: A recommendation team wraps a large pandas UDF around entire customer histories, then discovers some partitions exceed worker memory while others finish quickly. Which statement best explains the failure mode?
- For a single-node algorithm, adequate local RAM or a compatible distributed alternative matters more than adding idle executors.
- Concurrent study workers need a supported shared trial-storage design and correct coordination, not a fragile local-only backend.
- Data parallelism is often more natural than model-parallel networking for a small model with large independent data.
- Pandas-function distribution requires bounded partition or group size, not just parallel execution of arbitrary large pandas objects.
Explanation
Correct Answer
D:The technical constraint is specific to the reported failure. Pandas-function distribution requires bounded partition or group size, not just parallel execution of arbitrary large pandas objects. To test it, inspect per-group record counts, Arrow batch sizes and executor spill or OOM traces.
Incorrect Answers
A:That underlying principle is directed at a different scaling and tuning situation: A single-node model training run spends almost all time swapping a 40 GB feature matrix on a 16 GB VM; no distributed version exists. The current incident instead turns on pandas-function distribution requires bounded partition or group size, not just parallel execution of arbitrary large pandas objects.
B:That underlying principle 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 current incident instead turns on pandas-function distribution requires bounded partition or group size, not just parallel execution of arbitrary large pandas objects.
C:That underlying principle is directed at a different scaling and tuning situation: A tabular classifier fits comfortably on one GPU and 100 million independent examples are available, but a team proposes splitting the small model's layers across hosts. The current incident instead turns on pandas-function distribution requires bounded partition or group size, not just parallel execution of arbitrary large pandas objects.
Question 309
A production ML review contains this situation: A test suite mocks every external interface so aggressively that even an incompatible feature table schema appears valid. Which statement best explains the failure mode?
- Test stages need appropriate data classification and isolation, not just increasingly realistic inputs.
- Mocks are appropriate for isolated logic but cannot prove real integration contracts.
- Deterministic function tests should include degenerate data distributions that violate assumed mathematical denominators.
- Cross-component tests must validate shared time semantics and feature availability throughout the ML pipeline.
Explanation
Correct Answer
B:The technical constraint is specific to the reported failure. Mocks are appropriate for isolated logic but cannot prove real integration contracts. To test it, compare mock schemas with actual feature-table and serving contracts in a controlled environment.
Incorrect Answers
A:That underlying principle is directed at a different validation testing situation: An engineer uses only production replay data to validate a code change and exposes customer events in an unrestricted test workspace. The current incident instead turns on mocks are appropriate for isolated logic but cannot prove real integration contracts.
C:That underlying principle 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 current incident instead turns on mocks are appropriate for isolated logic but cannot prove real integration contracts.
D:That underlying principle 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 current incident instead turns on mocks are appropriate for isolated logic but cannot prove real integration contracts.
Question 310
A production ML review contains this situation: A retailer needs one independent forecasting model per store but concatenates all store histories before fitting one global model. What is the most material immediate risk in this situation?
- Seasonal behavior is blurred and no store receives its required independent fit.
- The rewritten job runs only on one worker or fails during model serialization.
- Trials are lost or repeated even when compute nodes appear healthy.
- Every replica hits device OOM even though aggregate cluster memory appears ample.
Explanation
Correct Answer
A:This consequence follows from the specific unresolved condition. Seasonal behavior is blurred and no store receives its required independent fit. The causal constraint is: Group-specific training must preserve group identity when independent model parameters are required.
Incorrect Answers
B:That direct consequence is directed at a different scaling and tuning situation: A team switches a SparkML training stage to Ray without verifying that its chosen estimator supports Ray's distributed fit contracts. The more immediate risk here is seasonal behavior is blurred and no store receives its required independent fit.
C: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 seasonal behavior is blurred and no store receives its required independent fit.
D:That direct consequence is directed at a different scaling and tuning situation: An image model needs 90 GB accelerator memory for one training replica while each available GPU has 24 GB and engineers propose only adding more identical nodes. The more immediate risk here is seasonal behavior is blurred and no store receives its required independent fit.