nerdexam
Google

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.

Submitted by daniela_cl· Apr 18, 2026ML pipeline operationalization

Question

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 serving container, which accepts a string as input for each prediction instance. In each string, the feature values are separated by commas. You want to deploy this model to production for online predictions and monitor the feature distribution over time with minimal effort. What should you do?

Options

  • A
    1. Upload the model to Vertex AI Model Registry, and deploy the model to a Vertex AI endpoint
  • B
    1. Upload the model to Vertex AI Model Registry, and deploy the model to a Vertex AI endpoint
  • C
    1. Refactor the serving container to accept key-value pairs as input format
  • D
    1. Refactor the serving container to accept key-value pairs as input format

How the community answered

(60 responses)
  • A
    77% (46)
  • B
    3% (2)
  • C
    8% (5)
  • D
    12% (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.

A1. Upload the model to Vertex AI Model Registry, and deploy the model to a Vertex AI endpointCorrect

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.

B1. Upload the model to Vertex AI Model Registry, and deploy the model to a Vertex AI endpoint

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.

C1. Refactor the serving container to accept key-value pairs as input format

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.

D1. Refactor the serving container to accept key-value pairs as input format

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

#Vertex AI Model Deployment#Vertex AI Model Monitoring#Custom Prediction Containers#Feature Drift

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-MACHINE-LEARNING-ENGINEER Practice