How to Add Accurate Predictive Explanations to an Existing Custom ML Model?
You work for a bank. You have created a custom model to predict whether a loan application should be flagged for human review. The input features are stored in a BigQuery table. The model is performing well, and you plan to deploy it to production. Due to compliance requirements the model must provide explanations for each prediction. You want to add this functionality to your model code with minimal effort and provide explanations that are as accurate as possible. What should you do?
Community Votes
84% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Tests understanding of Vertex Explainable AI integration patterns, with the common trap being manually embedding explanation logic in the serving container instead of using platform-native configuration.
To add compliant, per-prediction explanations to an existing custom model with minimal effort, leverage Vertex AI's native Explainable AI service. The community consensus strongly favors configuring feature-based attribution via Sampled Shapley over modifying serving containers or rebuilding the model.
Option D is frequently chosen because it seems like direct code control, but updating the custom serving container requires significant development effort and maintenance, violating the "minimal effort" requirement.
Community Discussion (8 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option C correctly utilizes Vertex Explainable AI’s feature-based attribution capabilities. By registering the existing custom model in Vertex AI Model Registry and enabling explainability configurations, you get per-prediction attributions without altering the model code. This approach natively supports methods like Sampled Shapley, which provides highly accurate, mathematically rigorous explanations that meet strict compliance standards. It aligns perfectly with the requirement for minimal engineering overhead while maximizing explanation quality.Why the Other Options Are Wrong
Options A and B require rebuilding the model from scratch, directly contradicting the premise that the current custom model is already performing well. Option D suggests hardcoding explanation logic into the serving container, which increases deployment complexity and testing burden. Platform-native XAI configurations are explicitly designed to decouple explanation generation from model inference code.Community Comment Notes
Multiple top-voted comments highlight that Vertex Explainable AI supports feature attribution across all model types without code modification [1][2]. Users emphasize that the phrase “minimal effort” combined with “accurate as possible” points directly to cloud-native configuration rather than custom implementation [4][5]. Several candidates initially considered option D but switched to C after reviewing official documentation confirming native attribution support for custom models [6][8].Official Reference
Exam Strategy
Focus on keywords like "minimal effort" and "existing model" to eliminate rebuild options. When a question emphasizes compliance and accuracy without code changes, prioritize managed platform services like Vertex Explainable AI over custom container modifications.
Related Analysis
Practice All PMLE Questions
Access 65 questions with complete answers and detailed explanations.
View Full PMLE Practice Test →