Generative AI Engineer is helping a cinema extend its website’s chat bot to be able to respond to questions about specific showtimes for movies currently playing at their local theater. They already have the location of the user provided by location services to their agent, and a Delta table which is continually updated with the latest showtime information by location. They want to implement this new capability in their RAG application. Which option will do this with the least effort and in the most performant way?
Select an option, then click Submit answer.
Reference / correct answer:
Query the Delta table directly via a SQL query constructed from the user’s input using a text-to-SQL LLM in the agent logic / tool implementation.
Most accepted answer: B. Query the Delta table directly via a SQL query constructed from the user’s input using a text-to-SQL LLM in the agent logic / tool implementation.
Community votes: A=2, B=2
Selected Answer: B The most efficient and effective path is to query the source of truth directly. upvoted 1 times
Selected Answer: A Online Feature Store syncs live from Delta table → always up-to-date upvoted 3 times
Selected Answer: B This scenario describes: A RAG (Retrieval-Augmented Generation) application. A Delta table that is continuously updated with showtimes by location. The agent already knows the user’s location. The engineer wants the simplest and most performant way to query fresh data. Why Option B is correct Querying the Delta table directly is: Low effort — the data already exists in Databricks. Real-time — Delta is always up to date. Performant — optimized storage and indexing under the hood. Easy integration. upvoted 2 times
Selected Answer: A Feature Serving Endpoint with Online Store: This approach is specifically designed for providing low-latency access to feature data in real-time. The cinema's continuously updated showtime data can be synced from the Delta table to an online store, such as the Databricks Feature Store's online store. upvoted 4 times