PROFESSIONAL-MACHINE-LEARNING-ENGINEER · Question #199
You work at a bank. You have a custom tabular ML model that was provided by the bank's vendor. The training data is not available due to its sensitivity. The model is packaged as a Vertex AI Model ser
The correct answer is A. 1. Upload the model to Vertex AI Model Registry, and deploy the model to a Vertex AI endpoint. To deploy a vendor-provided custom model container to Vertex AI Endpoints for online predictions and monitor feature distribution with minimal effort, upload it to the Model Registry and enable request-response logging and monitoring.
Question
Options
- A
- Upload the model to Vertex AI Model Registry, and deploy the model to a Vertex AI endpoint
- B
- Upload the model to Vertex AI Model Registry, and deploy the model to a Vertex AI endpoint
- C
- Refactor the serving container to accept key-value pairs as input format
- D
- Refactor the serving container to accept key-value pairs as input format
How the community answered
(60 responses)- A77% (46)
- B3% (2)
- C8% (5)
- D12% (7)
Why each option
To deploy a vendor-provided custom model container to Vertex AI Endpoints for online predictions and monitor feature distribution with minimal effort, upload it to the Model Registry and enable request-response logging and monitoring.
Vertex AI Model Monitoring relies on request-response logging and metadata about input features to monitor feature distribution and drift. Uploading the model to the Model Registry and deploying it to an endpoint with logging enabled allows the monitoring service to automatically extract features from the input string for analysis, requiring minimal changes to the vendor container.
Configuring `predict_instance_schema_uri` and `predict_input_drift_threshold` are components of setting up model monitoring, but option A describes the overarching process including deployment and implicitly the necessary logging for monitoring.
Refactoring the serving container to accept key-value pairs would require modifying the vendor-provided code, which contradicts the goal of 'minimal effort' and may not be feasible.
Refactoring the serving container to accept key-value pairs would require modifying the vendor-provided code, which contradicts the goal of 'minimal effort' and may not be feasible.
Concept tested: Vertex AI Model Monitoring for custom containers
Source: https://cloud.google.com/vertex-ai/docs/model-monitoring/collect-metadata
Topics
Community Discussion
No community discussion yet for this question.