Question 990A mortgage operations team needs feature attribution evidence for an approved risk model. What controlled validation most directly confirms the approach worked? Run allowed and denied access tests using the actual serving identity and audit role grants. Test a suite of adversarial and unauthorized prompts and verify sensitive output is blocked and auditable. Compare local attribution stability on similar cases and check against controlled perturbations and business rules. Replay shifted fixture data and confirm configured drift thresholds and alert routing work as expected. ExplanationCorrect Answer C:Compare local attribution stability on similar cases and check against controlled perturbations and business rules. This tests the underlying failure: Feature attribution describes how inputs relate to predictions, but explanations are not necessarily causal proof. Other Answers A:IAM controls cloud API permissions independently of whether a model produces accurate or safe predictions. That does not establish the required outcome; verify it by checking: Compare local attribution stability on similar cases and check against controlled perturbations and business rules. B: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: Compare local attribution stability on similar cases and check against controlled perturbations and business rules. D:Data drift is a change in input distributions and can occur even when prediction-outcome labels are delayed. That does not establish the required outcome; verify it by checking: Compare local attribution stability on similar cases and check against controlled perturbations and business rules.
Question 991A mortgage operations team needs feature attribution evidence for an approved risk model. What preventive release checklist item best protects the intended outcome? Version explainability methodology and require explanation quality reviews when features or architectures change. Maintain policy test suites and review false refusals whenever model and safety-filter versions change. Maintain prompt-injection regression tests, least-privilege retrieval and incident review for new knowledge sources. Define attribution-change alert policies and require domain analysis before model replacement. ExplanationCorrect Answer A:Version explainability methodology and require explanation quality reviews when features or architectures change. This protects the selected approach because Feature attribution describes how inputs relate to predictions, but explanations are not necessarily causal proof. The immediate solution is: Use supported model-explainability methods on Agent Platform and validate attribution against domain expectations. Other Answers B:Model instructions are probabilistic and safety guardrails need separate policy checks at input and output boundaries. The continuing safeguard required here is: Version explainability methodology and require explanation quality reviews when features or architectures change. C:Prompt injection is untrusted input attempting to override application instructions and can cause data leakage without isolation. The continuing safeguard required here is: Version explainability methodology and require explanation quality reviews when features or architectures change. D:Attribution drift can signal changes in how a model uses information that overall aggregate metrics may miss. The continuing safeguard required here is: Version explainability methodology and require explanation quality reviews when features or architectures change.
Question 992An internal reviewer cannot reconcile why similar applications obtained different prediction scores. What should the team change to address the specific technical requirement? Redact or minimize sensitive prompt and response fields and restrict monitoring access with a documented retention policy. Use supported model-explainability methods on Agent Platform and validate attribution against domain expectations. Use supported safety filters and explicit application-level response validation rather than relying on prompts alone. Configure Agent Platform Model Monitoring to alert on meaningful feature-distribution drift from a valid reference dataset. ExplanationCorrect Answer B:Feature attribution describes how inputs relate to predictions, but explanations are not necessarily causal proof. To validate the correction: Compare local attribution stability on similar cases and check against controlled perturbations and business rules. 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: Use supported model-explainability methods on Agent Platform and validate attribution against domain expectations. C:Model instructions are probabilistic and safety guardrails need separate policy checks at input and output boundaries. It does not resolve the specific failure; the targeted correction is: Use supported model-explainability methods on Agent Platform and validate attribution against domain expectations. D:Data drift is a change in input distributions and can occur even when prediction-outcome labels are delayed. It does not resolve the specific failure; the targeted correction is: Use supported model-explainability methods on Agent Platform and validate attribution against domain expectations.
Question 993An internal reviewer cannot reconcile why similar applications obtained different prediction scores. Which technical mechanism is most relevant to this outcome? Aggregate accuracy can obscure uneven subgroup errors and biased training labels or sampling distributions. Concept drift changes the relationship between features and targets rather than necessarily changing feature marginals. IAM controls cloud API permissions independently of whether a model produces accurate or safe predictions. Feature attribution describes how inputs relate to predictions, but explanations are not necessarily causal proof. ExplanationCorrect Answer D:Feature attribution describes how inputs relate to predictions, but explanations are not necessarily causal proof. This supports the specific implementation: Use supported model-explainability methods on Agent Platform and validate attribution against domain expectations. A suitable independent check is: Compare local attribution stability on similar cases and check against controlled perturbations and business rules. Other Answers A:Aggregate accuracy can obscure uneven subgroup errors and biased training labels or sampling distributions. The cause in the stated scenario is different: Feature attribution describes how inputs relate to predictions, but explanations are not necessarily causal proof. B:Concept drift changes the relationship between features and targets rather than necessarily changing feature marginals. The cause in the stated scenario is different: Feature attribution describes how inputs relate to predictions, but explanations are not necessarily causal proof. C:IAM controls cloud API permissions independently of whether a model produces accurate or safe predictions. The cause in the stated scenario is different: Feature attribution describes how inputs relate to predictions, but explanations are not necessarily causal proof.
Question 994An internal reviewer cannot reconcile why similar applications obtained different prediction scores. What controlled validation most directly confirms the approach worked? Apply a safe controlled load and verify p95 latency, error-rate and resource alarms trigger with clear ownership. Inject synthetic secrets and verify redaction, log access denials and retention configuration. Compare local attribution stability on similar cases and check against controlled perturbations and business rules. Submit defined unsafe test inputs and inspect filter decisions, false positives and user-safe fallback responses. ExplanationCorrect Answer C:Compare local attribution stability on similar cases and check against controlled perturbations and business rules. This tests the underlying failure: Feature attribution describes how inputs relate to predictions, but explanations are not necessarily causal proof. 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: Compare local attribution stability on similar cases and check against controlled perturbations and business rules. B:Observability data can itself expose confidential training or inference content if logs are collected without safeguards. That does not establish the required outcome; verify it by checking: Compare local attribution stability on similar cases and check against controlled perturbations and business rules. D:Model instructions are probabilistic and safety guardrails need separate policy checks at input and output boundaries. That does not establish the required outcome; verify it by checking: Compare local attribution stability on similar cases and check against controlled perturbations and business rules.
Question 995An internal reviewer cannot reconcile why similar applications obtained different prediction scores. Which repeatable process control should the ML engineering team adopt? Version explainability methodology and require explanation quality reviews when features or architectures change. Define attribution-change alert policies and require domain analysis before model replacement. Maintain prompt-injection regression tests, least-privilege retrieval and incident review for new knowledge sources. Apply data-classification and logging reviews before enabling verbose AI application diagnostics. ExplanationCorrect Answer A:Version explainability methodology and require explanation quality reviews when features or architectures change. This protects the selected approach because Feature attribution describes how inputs relate to predictions, but explanations are not necessarily causal proof. The immediate solution is: Use supported model-explainability methods on Agent Platform and validate attribution against domain expectations. Other Answers B:Attribution drift can signal changes in how a model uses information that overall aggregate metrics may miss. The continuing safeguard required here is: Version explainability methodology and require explanation quality reviews when features or architectures change. C:Prompt injection is untrusted input attempting to override application instructions and can cause data leakage without isolation. The continuing safeguard required here is: Version explainability methodology and require explanation quality reviews when features or architectures change. D:Observability data can itself expose confidential training or inference content if logs are collected without safeguards. The continuing safeguard required here is: Version explainability methodology and require explanation quality reviews when features or architectures change.
Question 996A generative AI workflow accidentally logs full confidential prompts in an unrestricted troubleshooting dashboard. What should the team change to address the specific technical requirement? Run continuous groundedness, citation relevance and task-completion evaluations on a held-out generative AI dataset. Evaluate model outcomes and error rates across relevant groups and apply documented responsible-AI mitigations. Redact or minimize sensitive prompt and response fields and restrict monitoring access with a documented retention policy. Restrict the workload service account to least-privilege roles and the minimum approved resource set. ExplanationCorrect Answer C:Observability data can itself expose confidential training or inference content if logs are collected without safeguards. To validate the correction: Inject synthetic secrets and verify redaction, log access denials and retention configuration. Other Answers A: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: Redact or minimize sensitive prompt and response fields and restrict monitoring access with a documented retention policy. B:Aggregate accuracy can obscure uneven subgroup errors and biased training labels or sampling distributions. It does not resolve the specific failure; the targeted correction is: Redact or minimize sensitive prompt and response fields and restrict monitoring access with a documented retention policy. D: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: Redact or minimize sensitive prompt and response fields and restrict monitoring access with a documented retention policy.
Question 997A generative AI workflow accidentally logs full confidential prompts in an unrestricted troubleshooting dashboard. What Google Cloud or model behavior explains the best solution? Observability data can itself expose confidential training or inference content if logs are collected without safeguards. IAM controls cloud API permissions independently of whether a model produces accurate or safe predictions. Prompt injection is untrusted input attempting to override application instructions and can cause data leakage without isolation. Generative AI answer quality can regress through retrieval or prompt changes even when infrastructure is healthy. ExplanationCorrect Answer A:Observability data can itself expose confidential training or inference content if logs are collected without safeguards. This supports the specific implementation: Redact or minimize sensitive prompt and response fields and restrict monitoring access with a documented retention policy. A suitable independent check is: Inject synthetic secrets and verify redaction, log access denials and retention configuration. Other Answers B:IAM controls cloud API permissions independently of whether a model produces accurate or safe predictions. The cause in the stated scenario is different: Observability data can itself expose confidential training or inference content if logs are collected without safeguards. C:Prompt injection is untrusted input attempting to override application instructions and can cause data leakage without isolation. The cause in the stated scenario is different: Observability data can itself expose confidential training or inference content if logs are collected without safeguards. 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: Observability data can itself expose confidential training or inference content if logs are collected without safeguards.
Question 998A generative AI workflow accidentally logs full confidential prompts in an unrestricted troubleshooting dashboard. Which evidence would best demonstrate that this ML solution meets the requirement? Inject synthetic secrets and verify redaction, log access denials and retention configuration. Compare recent labeled metrics and calibration to a frozen prior period under comparable evaluation rules. Run allowed and denied access tests using the actual serving identity and audit role grants. Compare local attribution stability on similar cases and check against controlled perturbations and business rules. ExplanationCorrect Answer A:Inject synthetic secrets and verify redaction, log access denials and retention configuration. This tests the underlying failure: Observability data can itself expose confidential training or inference content if logs are collected without safeguards. 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: Inject synthetic secrets and verify redaction, log access denials and retention configuration. C:IAM controls cloud API permissions independently of whether a model produces accurate or safe predictions. That does not establish the required outcome; verify it by checking: Inject synthetic secrets and verify redaction, log access denials and retention configuration. 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: Inject synthetic secrets and verify redaction, log access denials and retention configuration.
Question 999A generative AI workflow accidentally logs full confidential prompts in an unrestricted troubleshooting dashboard. Which repeatable process control should the ML engineering team adopt? Apply data-classification and logging reviews before enabling verbose AI application diagnostics. Version explainability methodology and require explanation quality reviews when features or architectures change. Establish label-lag-aware concept-drift reviews and trigger retraining only after confirmed degradation. Maintain prompt-injection regression tests, least-privilege retrieval and incident review for new knowledge sources. ExplanationCorrect Answer A:Apply data-classification and logging reviews before enabling verbose AI application diagnostics. This protects the selected approach because Observability data can itself expose confidential training or inference content if logs are collected without safeguards. The immediate solution is: Redact or minimize sensitive prompt and response fields and restrict monitoring access with a documented retention policy. Other Answers B:Feature attribution describes how inputs relate to predictions, but explanations are not necessarily causal proof. The continuing safeguard required here is: Apply data-classification and logging reviews before enabling verbose AI application diagnostics. C:Concept drift changes the relationship between features and targets rather than necessarily changing feature marginals. The continuing safeguard required here is: Apply data-classification and logging reviews before enabling verbose AI application diagnostics. D:Prompt injection is untrusted input attempting to override application instructions and can cause data leakage without isolation. The continuing safeguard required here is: Apply data-classification and logging reviews before enabling verbose AI application diagnostics.
Question 1000A model-serving application writes sensitive user document fragments into broadly accessible telemetry events. Which implementation response is most appropriate for this ML engineering situation? Use supported safety filters and explicit application-level response validation rather than relying on prompts alone. Run continuous groundedness, citation relevance and task-completion evaluations on a held-out generative AI dataset. Restrict the workload service account to least-privilege roles and the minimum approved resource set. Redact or minimize sensitive prompt and response fields and restrict monitoring access with a documented retention policy. ExplanationCorrect Answer D:Observability data can itself expose confidential training or inference content if logs are collected without safeguards. To validate the correction: Inject synthetic secrets and verify redaction, log access denials and retention configuration. Other Answers A:Model instructions are probabilistic and safety guardrails need separate policy checks at input and output boundaries. It does not resolve the specific failure; the targeted correction is: Redact or minimize sensitive prompt and response fields and restrict monitoring access with a documented retention policy. 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: Redact or minimize sensitive prompt and response fields and restrict monitoring access with a documented retention policy. 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: Redact or minimize sensitive prompt and response fields and restrict monitoring access with a documented retention policy.