A SaaS multi-agent assistant stores short-term session state and long-term semantic memory for thousands of customer tenants. During a red-team exercise, Tenant A’s agent retrieved Tenant B’s prior case summaries through a shared vector store namespace. Which memory design change best remediates the cross-tenant leak while preserving per-tenant long-term memory?
Select an answer to reveal the explanation.
Short Explanation
Cross-tenant retrieval is a memory isolation failure, not a need-more-recall problem. You need to partition session and long-term memory by tenant with namespaces, filters, and keys tied to authenticated tenant identity so agents never search foreign partitions. Global shared memory makes the leak worse, turning memory off kills the product capability, and browser localStorage isn't a secure multi-tenant server control.
Full Explanation
The correct design is to enforce tenant-isolated memory namespaces and query filters for session and long-term stores so retrieval is scoped to the authenticated tenant’s partition. Multi-agent memory strategies must address security, compliance, lifecycle, storage, and session management—including tenant isolation for multi-tenant deployments. Isolated namespaces and mandatory tenant filters on vector/session stores prevent lateral retrieval of another tenant’s semantic memory while preserving per-tenant long-term memory. Merging all tenants into one global memory partition is incorrect because a single global partition maximizes cross-tenant leakage risk. Disabling long-term memory for everyone and relying only on the current user message is incorrect because it avoids the symptom by removing a required capability rather than fixing isolation. Storing memory exclusively in browser localStorage of end users without server-side controls is incorrect because client-only storage lacks centralized policy enforcement, multi-device consistency, and server-side isolation guarantees for SaaS agents. Exam focus: multi-tier memory requires tenant isolation as a first-class design constraint.