Ai Coding And Product Systems medium
An enterprise customer of your code assistant requires that their source code is never mixed with other customers' data and is never used to train models. You are building an embedding index over customer repositories for context retrieval. Which design satisfies this?
- A Use tenant-scoped indexes with per-tenant keys, enforce tenant ID at query time, and default to no training on customer code.
- B Use one shared global index for all customers, since embeddings are irreversible vectors and cannot leak the original source code.
- C Keep a shared index but hash file paths and identifiers before embedding so other tenants cannot recognize matching code chunks.
- D Store code only in the customer's region and train a shared model on it, since regional residency satisfies the isolation requirement.
Answer: A. Use tenant-scoped indexes with per-tenant keys, enforce tenant ID at query time, and default to no training on customer code.
**Tenant-scoped indexes** with no training by default trade shared-infrastructure efficiency for isolation customers can audit. The shared index (B) is tempting, but embeddings can be partially inverted and nearest-neighbor results can surface another tenant's chunks. Data residency (D) addresses location, not training or isolation. A shared index is acceptable only for public open-source code that carries no confidentiality requirement.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- Your assistant uses a classifier to route queries to a small or large model, which saves 60% of GPU spend. Analysis shows about 20% of hard queries are misrouted to the small model, which then gives confident wrong answers, and regenerate clicks on those threads have doubled. What should you do?
- Your workspace AI retrieves the top-k chunks from a shared vector index and passes them to the model with ACL metadata and a system prompt saying 'only use documents this user can access.' A user just received an answer quoting a private HR page they cannot open. What is the correct fix?
- Your support bot answers billing questions. One user has asked the same refund question three times, and retrieval confidence for that topic is low. What should the bot do next?
- Your AI review system receives a 4,000-line pull request spanning 60 files. Sending the whole diff in one prompt yields shallow, generic comments, and real bugs in files near the middle of the diff are missed. How should you structure the review?
- In your ChatGPT-style assistant, power users keep single threads running for weeks, reaching about 150K tokens. Cost per turn keeps climbing, latency is rising, and the model increasingly misses facts from early in the thread. What should you do?
- Your workspace AI filters retrieval using ACLs stored in the vector index, which is rebuilt nightly. An admin removes an employee from a confidential project page, but for the rest of the day the employee can still get AI answers drawn from it. What is the right fix?