MicrosoftArchitect multi-agent solutions

Memory Architecture & Identity Design — AI-500 Practice Question

A representative Microsoft Multi-Agent AI Solutions Expert (AI-500) exam question on Memory Architecture & Identity Design. Work through it below, then read why each option is right or wrong.

This question is part of the free Microsoft Multi-Agent AI Solutions Expert practice test.

Short answer

The correct answer is D. Implement isolated conversation stores per client with agent identity scoped to each session; use a separate shared knowledge store for aggregate market data indexed by market segment, not client identity..

Isolating conversation stores per client with scoped identity ensures client data privacy and prevents cross-contamination. A separate shared knowledge store for aggregate insights (indexed by market segment, not client identity) enables knowledge sharing without exposing sensitive client data. Role-based filtering at query time is brittle and creates data exposure risk. In-memory caching without proper isolation fails under concurrent load and loses data on restart. Shared vector databases with metadata filters are vulnerable to filter bypass and identity confusion.

The Question

A financial advisory multi-agent system must maintain separate conversation contexts for each client while ensuring agents can share aggregate market insights without exposing individual client portfolios. The system processes 500+ concurrent client sessions. Which memory and identity architecture best meets these requirements?

ACache all conversation data in agent memory with periodic synchronization to a central database; implement identity through session tokens only.
BStore all conversation history in a single shared database with role-based filtering applied at query time; use client ID in agent identity tokens to control access.
CUse a single shared vector database for all client conversations with client ID as a metadata filter; assign all agents a generic identity to simplify communication.
DImplement isolated conversation stores per client with agent identity scoped to each session; use a separate shared knowledge store for aggregate market data indexed by market segment, not client identity.Correct

Why D is correct

Isolating conversation stores per client with scoped identity ensures client data privacy and prevents cross-contamination. A separate shared knowledge store for aggregate insights (indexed by market segment, not client identity) enables knowledge sharing without exposing sensitive client data. Role-based filtering at query time is brittle and creates data exposure risk. In-memory caching without proper isolation fails under concurrent load and loses data on restart. Shared vector databases with metadata filters are vulnerable to filter bypass and identity confusion.

Why the other options are wrong

Option A: Cache all conversation data in agent memory with periodic synchronization to a central database; implement identity through session tokens only.

Option A does not satisfy the requirement in the scenario. Review the explanation above: the correct choice (D) is the only one that fully meets every constraint stated in the question.

Option B: Store all conversation history in a single shared database with role-based filtering applied at query time; use client ID in agent identity tokens to control access.

Option B does not satisfy the requirement in the scenario. Review the explanation above: the correct choice (D) is the only one that fully meets every constraint stated in the question.

Option C: Use a single shared vector database for all client conversations with client ID as a metadata filter; assign all agents a generic identity to simplify communication.

Option C does not satisfy the requirement in the scenario. Review the explanation above: the correct choice (D) is the only one that fully meets every constraint stated in the question.

Key idea: Memory Architecture & Identity Design

Isolating conversation stores per client with scoped identity ensures client data privacy and prevents cross-contamination. A separate shared knowledge store for aggregate insights (indexed by market segment, not client identity) enables knowledge sharing without exposing sensitive client data. Role-based filtering at query time is brittle and creates data exposure risk. In-memory caching without proper isolation fails under concurrent load and loses data on restart. Shared vector databases with metadata filters are vulnerable to filter bypass and identity confusion. On the AI-500 exam, questions in the "Architect multi-agent solutions" domain test whether you can map a scenario's constraints to the right choice. Read the requirement carefully, eliminate options that violate any single constraint, and pick the one that satisfies all of them with the least operational overhead.

Ready to see how you'd score?

Take the free practice quiz and find out which Microsoft Multi-Agent AI Solutions Expert domains you need to focus on. No signup required.

Practice 5 similar questions

Same cert, same or adjacent domain. Use these after reviewing the explanation.

Related Microsoft Multi-Agent AI Solutions Expert Practice Questions

Official sources used

Verify program and exam details at the source before scheduling.