Assembling and Deploying Applications1 / 5
A team wants to A/B test two different prompt strategies for their customer support agent. How should they set this up using Databricks serving?
CorrectIncorrect
Alex
A/B testing GenAI agents on Databricks uses the traffic_config in a serving endpoint to split requests between served entities. Each agent version is deployed as a separate served_entity on the same endpoint, with traffic_percentage controlling the split (must sum to 100). Each version's responses are logged separately in the inference table, enabling comparison of quality, latency, and user feedback. Distractor analysis: The option “Use Feature Serving to tag each request and route…” is wrong—Feature Serving is for feature lookup, not prompt routing. The option “Deploy a single endpoint with a pre-processing hook…” is wrong—pre-processing hooks don't provide proper traffic management or independent logging. The option “Register each prompt version in MLflow Model Registry…” is wrong—custom routing notebooks bypass Databricks' built-in traffic management and inference logging. Ref: docs.databricks.com/en/machine-learning/model-serving/serve-multiple-models-to-serving-endpoint.html
Sourcedocs.databricks.com
Follow-up answers are available in the app. Create a free account — no credit card required.
Question 1 of 5
Create a free account