Question 1030A recommendation service's input feature histogram shifts after a source-system update, even before labels become available. Which implementation response is most appropriate for this ML engineering situation? Redact or minimize sensitive prompt and response fields and restrict monitoring access with a documented retention policy. Configure Agent Platform Model Monitoring to alert on meaningful feature-distribution drift from a valid reference dataset. Monitor feature-attribution drift alongside outcome and input metrics on representative authorized samples. Run continuous groundedness, citation relevance and task-completion evaluations on a held-out generative AI dataset. ExplanationCorrect Answer B:Data drift is a change in input distributions and can occur even when prediction-outcome labels are delayed. To validate the correction: Replay shifted fixture data and confirm configured drift thresholds and alert routing work as expected. Other Answers A:Observability data can itself expose confidential training or inference content if logs are collected without safeguards. It does not resolve the specific failure; the targeted correction is: Configure Agent Platform Model Monitoring to alert on meaningful feature-distribution drift from a valid reference dataset. C:Attribution drift can signal changes in how a model uses information that overall aggregate metrics may miss. It does not resolve the specific failure; the targeted correction is: Configure Agent Platform Model Monitoring to alert on meaningful feature-distribution drift from a valid reference dataset. D:Generative AI answer quality can regress through retrieval or prompt changes even when infrastructure is healthy. It does not resolve the specific failure; the targeted correction is: Configure Agent Platform Model Monitoring to alert on meaningful feature-distribution drift from a valid reference dataset.
Question 1031A recommendation service's input feature histogram shifts after a source-system update, even before labels become available. What Google Cloud or model behavior explains the best solution? Data drift is a change in input distributions and can occur even when prediction-outcome labels are delayed. Attribution drift can signal changes in how a model uses information that overall aggregate metrics may miss. Observability data can itself expose confidential training or inference content if logs are collected without safeguards. Training-serving skew can degrade predictions without any change to the underlying fitted model weights. ExplanationCorrect Answer A:Data drift is a change in input distributions and can occur even when prediction-outcome labels are delayed. This supports the specific implementation: Configure Agent Platform Model Monitoring to alert on meaningful feature-distribution drift from a valid reference dataset. A suitable independent check is: Replay shifted fixture data and confirm configured drift thresholds and alert routing work as expected. Other Answers B:Attribution drift can signal changes in how a model uses information that overall aggregate metrics may miss. The cause in the stated scenario is different: Data drift is a change in input distributions and can occur even when prediction-outcome labels are delayed. C:Observability data can itself expose confidential training or inference content if logs are collected without safeguards. The cause in the stated scenario is different: Data drift is a change in input distributions and can occur even when prediction-outcome labels are delayed. D:Training-serving skew can degrade predictions without any change to the underlying fitted model weights. The cause in the stated scenario is different: Data drift is a change in input distributions and can occur even when prediction-outcome labels are delayed.
Question 1032A recommendation service's input feature histogram shifts after a source-system update, even before labels become available. Which measurement or test should the team perform after implementation? Replay shifted fixture data and confirm configured drift thresholds and alert routing work as expected. Compare recent labeled metrics and calibration to a frozen prior period under comparable evaluation rules. Replay identical raw cases in both environments and compare feature vectors and model outputs. Compare group metrics and representative false negatives on consented and legally appropriate audit samples. ExplanationCorrect Answer A:Replay shifted fixture data and confirm configured drift thresholds and alert routing work as expected. This tests the underlying failure: Data drift is a change in input distributions and can occur even when prediction-outcome labels are delayed. Other Answers B:Concept drift changes the relationship between features and targets rather than necessarily changing feature marginals. That does not establish the required outcome; verify it by checking: Replay shifted fixture data and confirm configured drift thresholds and alert routing work as expected. C:Training-serving skew can degrade predictions without any change to the underlying fitted model weights. That does not establish the required outcome; verify it by checking: Replay shifted fixture data and confirm configured drift thresholds and alert routing work as expected. D:Aggregate accuracy can obscure uneven subgroup errors and biased training labels or sampling distributions. That does not establish the required outcome; verify it by checking: Replay shifted fixture data and confirm configured drift thresholds and alert routing work as expected.
Question 1033A recommendation service's input feature histogram shifts after a source-system update, even before labels become available. Which ongoing standard would make this result reliable for future model versions? Version explainability methodology and require explanation quality reviews when features or architectures change. Version retrieval indexes and evaluation prompts and gate releases on grounded-answer regression tests. Refresh reference distributions only after approved investigation and maintain source-drift incident runbooks. Maintain separate service reliability and model-quality SLOs with tested incident escalation paths. ExplanationCorrect Answer C:Refresh reference distributions only after approved investigation and maintain source-drift incident runbooks. This protects the selected approach because Data drift is a change in input distributions and can occur even when prediction-outcome labels are delayed. The immediate solution is: Configure Agent Platform Model Monitoring to alert on meaningful feature-distribution drift from a valid reference dataset. Other Answers A:Feature attribution describes how inputs relate to predictions, but explanations are not necessarily causal proof. The continuing safeguard required here is: Refresh reference distributions only after approved investigation and maintain source-drift incident runbooks. B:Generative AI answer quality can regress through retrieval or prompt changes even when infrastructure is healthy. The continuing safeguard required here is: Refresh reference distributions only after approved investigation and maintain source-drift incident runbooks. D:Reliability metrics expose serving failures independently from predictive model quality and training drift. The continuing safeguard required here is: Refresh reference distributions only after approved investigation and maintain source-drift incident runbooks.
Question 1034An inventory forecast begins receiving drastically different sensor values from a recently replaced field device. Which implementation response is most appropriate for this ML engineering situation? Configure Agent Platform Model Monitoring to alert on meaningful feature-distribution drift from a valid reference dataset. Monitor labeled performance and investigate concept drift using refreshed ground truth instead of input drift alone. Restrict the workload service account to least-privilege roles and the minimum approved resource set. Instrument request latency, availability, utilization and queueing with production Model Monitoring and cloud telemetry. ExplanationCorrect Answer A:Data drift is a change in input distributions and can occur even when prediction-outcome labels are delayed. To validate the correction: Replay shifted fixture data and confirm configured drift thresholds and alert routing work as expected. Other Answers B:Concept drift changes the relationship between features and targets rather than necessarily changing feature marginals. It does not resolve the specific failure; the targeted correction is: Configure Agent Platform Model Monitoring to alert on meaningful feature-distribution drift from a valid reference dataset. C:IAM controls cloud API permissions independently of whether a model produces accurate or safe predictions. It does not resolve the specific failure; the targeted correction is: Configure Agent Platform Model Monitoring to alert on meaningful feature-distribution drift from a valid reference dataset. D:Reliability metrics expose serving failures independently from predictive model quality and training drift. It does not resolve the specific failure; the targeted correction is: Configure Agent Platform Model Monitoring to alert on meaningful feature-distribution drift from a valid reference dataset.
Question 1035An inventory forecast begins receiving drastically different sensor values from a recently replaced field device. Which technical mechanism is most relevant to this outcome? Data drift is a change in input distributions and can occur even when prediction-outcome labels are delayed. Concept drift changes the relationship between features and targets rather than necessarily changing feature marginals. Feature attribution describes how inputs relate to predictions, but explanations are not necessarily causal proof. Generative AI answer quality can regress through retrieval or prompt changes even when infrastructure is healthy. ExplanationCorrect Answer A:Data drift is a change in input distributions and can occur even when prediction-outcome labels are delayed. This supports the specific implementation: Configure Agent Platform Model Monitoring to alert on meaningful feature-distribution drift from a valid reference dataset. A suitable independent check is: Replay shifted fixture data and confirm configured drift thresholds and alert routing work as expected. Other Answers B:Concept drift changes the relationship between features and targets rather than necessarily changing feature marginals. The cause in the stated scenario is different: Data drift is a change in input distributions and can occur even when prediction-outcome labels are delayed. C:Feature attribution describes how inputs relate to predictions, but explanations are not necessarily causal proof. The cause in the stated scenario is different: Data drift is a change in input distributions and can occur even when prediction-outcome labels are delayed. D:Generative AI answer quality can regress through retrieval or prompt changes even when infrastructure is healthy. The cause in the stated scenario is different: Data drift is a change in input distributions and can occur even when prediction-outcome labels are delayed.
Question 1036An inventory forecast begins receiving drastically different sensor values from a recently replaced field device. What is the most relevant acceptance check for the proposed ML change? Apply a safe controlled load and verify p95 latency, error-rate and resource alarms trigger with clear ownership. Replay shifted fixture data and confirm configured drift thresholds and alert routing work as expected. Test a suite of adversarial and unauthorized prompts and verify sensitive output is blocked and auditable. Compare recent labeled metrics and calibration to a frozen prior period under comparable evaluation rules. ExplanationCorrect Answer B:Replay shifted fixture data and confirm configured drift thresholds and alert routing work as expected. This tests the underlying failure: Data drift is a change in input distributions and can occur even when prediction-outcome labels are delayed. Other Answers A:Reliability metrics expose serving failures independently from predictive model quality and training drift. That does not establish the required outcome; verify it by checking: Replay shifted fixture data and confirm configured drift thresholds and alert routing work as expected. C:Prompt injection is untrusted input attempting to override application instructions and can cause data leakage without isolation. That does not establish the required outcome; verify it by checking: Replay shifted fixture data and confirm configured drift thresholds and alert routing work as expected. D:Concept drift changes the relationship between features and targets rather than necessarily changing feature marginals. That does not establish the required outcome; verify it by checking: Replay shifted fixture data and confirm configured drift thresholds and alert routing work as expected.
Question 1037An inventory forecast begins receiving drastically different sensor values from a recently replaced field device. What governance or operational safeguard should accompany the implementation? Refresh reference distributions only after approved investigation and maintain source-drift incident runbooks. Apply data-classification and logging reviews before enabling verbose AI application diagnostics. Require preprocessing digest parity and contract tests for every model and feature pipeline update. Establish label-lag-aware concept-drift reviews and trigger retraining only after confirmed degradation. ExplanationCorrect Answer A:Refresh reference distributions only after approved investigation and maintain source-drift incident runbooks. This protects the selected approach because Data drift is a change in input distributions and can occur even when prediction-outcome labels are delayed. The immediate solution is: Configure Agent Platform Model Monitoring to alert on meaningful feature-distribution drift from a valid reference dataset. Other Answers B:Observability data can itself expose confidential training or inference content if logs are collected without safeguards. The continuing safeguard required here is: Refresh reference distributions only after approved investigation and maintain source-drift incident runbooks. C:Training-serving skew can degrade predictions without any change to the underlying fitted model weights. The continuing safeguard required here is: Refresh reference distributions only after approved investigation and maintain source-drift incident runbooks. D:Concept drift changes the relationship between features and targets rather than necessarily changing feature marginals. The continuing safeguard required here is: Refresh reference distributions only after approved investigation and maintain source-drift incident runbooks.
Question 1038A customer churn model sees a new categorical distribution after the company launches in another country. Which proposed approach best resolves the described model engineering problem? Configure Agent Platform Model Monitoring to alert on meaningful feature-distribution drift from a valid reference dataset. Run continuous groundedness, citation relevance and task-completion evaluations on a held-out generative AI dataset. Monitor labeled performance and investigate concept drift using refreshed ground truth instead of input drift alone. Redact or minimize sensitive prompt and response fields and restrict monitoring access with a documented retention policy. ExplanationCorrect Answer A:Data drift is a change in input distributions and can occur even when prediction-outcome labels are delayed. To validate the correction: Replay shifted fixture data and confirm configured drift thresholds and alert routing work as expected. Other Answers B:Generative AI answer quality can regress through retrieval or prompt changes even when infrastructure is healthy. It does not resolve the specific failure; the targeted correction is: Configure Agent Platform Model Monitoring to alert on meaningful feature-distribution drift from a valid reference dataset. C:Concept drift changes the relationship between features and targets rather than necessarily changing feature marginals. It does not resolve the specific failure; the targeted correction is: Configure Agent Platform Model Monitoring to alert on meaningful feature-distribution drift from a valid reference dataset. D:Observability data can itself expose confidential training or inference content if logs are collected without safeguards. It does not resolve the specific failure; the targeted correction is: Configure Agent Platform Model Monitoring to alert on meaningful feature-distribution drift from a valid reference dataset.
Question 1039A customer churn model sees a new categorical distribution after the company launches in another country. What Google Cloud or model behavior explains the best solution? Feature attribution describes how inputs relate to predictions, but explanations are not necessarily causal proof. Training-serving skew can degrade predictions without any change to the underlying fitted model weights. Attribution drift can signal changes in how a model uses information that overall aggregate metrics may miss. Data drift is a change in input distributions and can occur even when prediction-outcome labels are delayed. ExplanationCorrect Answer D:Data drift is a change in input distributions and can occur even when prediction-outcome labels are delayed. This supports the specific implementation: Configure Agent Platform Model Monitoring to alert on meaningful feature-distribution drift from a valid reference dataset. A suitable independent check is: Replay shifted fixture data and confirm configured drift thresholds and alert routing work as expected. Other Answers A:Feature attribution describes how inputs relate to predictions, but explanations are not necessarily causal proof. The cause in the stated scenario is different: Data drift is a change in input distributions and can occur even when prediction-outcome labels are delayed. B:Training-serving skew can degrade predictions without any change to the underlying fitted model weights. The cause in the stated scenario is different: Data drift is a change in input distributions and can occur even when prediction-outcome labels are delayed. C:Attribution drift can signal changes in how a model uses information that overall aggregate metrics may miss. The cause in the stated scenario is different: Data drift is a change in input distributions and can occur even when prediction-outcome labels are delayed.
Question 1040A customer churn model sees a new categorical distribution after the company launches in another country. Which measurement or test should the team perform after implementation? Apply a safe controlled load and verify p95 latency, error-rate and resource alarms trigger with clear ownership. Compare sampled source citations and factuality against approved references before and after the index update. Replay shifted fixture data and confirm configured drift thresholds and alert routing work as expected. Compare local attribution stability on similar cases and check against controlled perturbations and business rules. ExplanationCorrect Answer C:Replay shifted fixture data and confirm configured drift thresholds and alert routing work as expected. This tests the underlying failure: Data drift is a change in input distributions and can occur even when prediction-outcome labels are delayed. Other Answers A:Reliability metrics expose serving failures independently from predictive model quality and training drift. That does not establish the required outcome; verify it by checking: Replay shifted fixture data and confirm configured drift thresholds and alert routing work as expected. B:Generative AI answer quality can regress through retrieval or prompt changes even when infrastructure is healthy. That does not establish the required outcome; verify it by checking: Replay shifted fixture data and confirm configured drift thresholds and alert routing work as expected. D:Feature attribution describes how inputs relate to predictions, but explanations are not necessarily causal proof. That does not establish the required outcome; verify it by checking: Replay shifted fixture data and confirm configured drift thresholds and alert routing work as expected.