Study Databricks GENAI-ASSOC Unity Catalog and Endpoints: key concepts, common traps, and exam decision cues.
Deployment questions often hide governance and state-management details inside them. The current guide expects you to connect governed registration, endpoint access, persistent memory, and batch inference use appropriately.
| Need | Better first instinct |
|---|---|
| governed registration of the app or model | Unity Catalog plus MLflow registration |
| control access to serving resources | endpoint access controls |
| store intermediate memory or structured state | persistent datastore selection |
| run inference across data in batch | ai_query() where appropriate |
| If the problem is mainly about… | Better first read |
|---|---|
| governed registration | UC plus MLflow registration boundary |
| who can invoke the endpoint | endpoint access control |
| where state lives between steps | persistent datastore and state design |
| non-interactive inference at scale | batch inference path such as ai_query() |
| Trap | Better rule |
|---|---|
| assuming deployment is only about serving the endpoint | registration, access, and state also matter |
| mixing endpoint access with retrieval filters | endpoint access protects resources; filters shape retrieval scope |
| forgetting memory or structured state for stateful apps | state has to live somewhere intentionally |
A deployed app works in demos, but production users should not all have the same serving access, and the app also needs durable conversation state between turns. Which two deployment layers should you classify first?
Correct answer: A. This is a deployment-boundary question about protected access and statefulness, not about retrieval alone.
Governed deployment questions usually ask where lifecycle and registration live. If the exam asks how to register a model or chain in the governed catalog, think Unity Catalog registration through MLflow. If the application needs memory across interactions, think persistent datastore rather than just bigger prompts. The weak answer usually confuses serving with registration or persistence.