Skip to lesson
Exit
Security, Governance & Architecture1 / 2

2 min lesson

Model routing & data locality

Make the call in this situation. "A platform team wants to bring their own model API keys for full provider control. What governance change must you flag?" Explain what supports it.

Step 1 of 2

Model routing & data locality

Model selection is a trade-off you must be able to explain. Managed inference keeps ZDRZero Data Retention. A contractual guarantee that the model provider won't store your code or train on it. Press Enter for the full definition. terms intact and is the simplest posture. Bring-your-own keys gives the customer provider control but moves the data terms to that provider, which makes it a governance change. Models with provider-side retention are the second exception, so leave non-ZDR models off in model access control unless the customer opts in.

MANAGED INFERENCE VS. BRING-YOUR-OWN KEYS

Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.

diagram: compare

BYO keys is a governance change: flag the ZDR shift unprompted.