Security reviews, residency and other objections
Prepare the standard answers on data use, retention, residency, access and model risk, and know which are yours to answer.
| Objection | What they need to hear | Evidence |
|---|---|---|
| "Will our data train your models?" | The vendor's actual data-use terms for this product tier | The provider's published commercial terms and DPA; never paraphrase from memory |
| "Where is our data processed and stored?" | Regions, sub-processors, residency options | Architecture diagram; provider documentation |
| "Who can see prompts and outputs?" | Access controls, logging, retention period | RBAC design, audit logs, retention settings |
| "What if it gives a wrong answer?" | Human review points, evals, liability boundaries | Eval results, escalation flow |
| "How do you stop prompt injection?" | Layered controls and least-privilege tools | Threat model (see the security track) |
| "Can we run it in our cloud tenancy?" | Deployment options that exist today | Cloud marketplace / private deployment documentation |
Never improvise answers about a provider's legal or data terms. Say you will confirm, and route to the owner. Getting this wrong is how deals and trust are lost.
Your Azure background is an asset here: many enterprises consume frontier models through their existing cloud agreements and landing zones. Be ready to talk private networking, managed identity, key management and policy in the customer's own terms.
Practice
Written for this site to drill the lesson. Not reported interview questions.
- Answer the six objections above for a system you have built, in two sentences each.
- A customer's architect asks for a data-flow diagram by tomorrow. Draw it for the enterprise Q&A system in the design track.
Check yourself
What do you do when asked about a provider's data-use terms and you are unsure?
Say you will confirm and route to the owner; never improvise.
Saved in this browser.