Ai Coding And Product Systems hard
Enterprise customers of your code assistant require contractually that their source code can never influence suggestions shown to another company. Infra wants a shared embedding index and a shared semantic response cache to cut costs. Which design meets the requirement?
- A Use one shared vector index with a tenant_id filter applied after retrieval, plus a global semantic cache keyed on prompt embedding.
- B Fine-tune a shared completion model weekly on aggregated customer repos, stripping secrets with a scanner before each training run.
- C Partition indexes and caches per tenant, scope cache keys by tenant, and exclude customer code from training unless opted in.
- D Encrypt embeddings at rest in a shared index so other tenants cannot decode the vectors, and keep the global cache for latency.
Answer: C. Partition indexes and caches per tenant, scope cache keys by tenant, and exclude customer code from training unless opted in.
Source privacy needs **tenant-scoped indexes and caches and no training on customer data by default**. The cost is a lower cache hit rate and more index overhead. Option A looks efficient, but a global semantic cache will serve tenant X's code-derived answer to a similar prompt from tenant Y, whatever the index filter does. Encryption at rest (D) protects storage, not query-time mixing.
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?