Implement generative AI and agentic solutions 2.2 Build agents by using Foundry
A shopping agent uses Foundry Agent Service memory (preview).
Study guide skill: Build agents that integrate retrieval, function-calling, and conversation memory
Question B8-021
A shopping agent uses Foundry Agent Service memory (preview). Privacy rules require that memories expire automatically after a set period, and that when a user says 'forget my home address' the change happens immediately. Which two capabilities should you use? (Choose two.)
Select 2 answers.
Answer: A, E
Memory supports a store-level default TTL for entries and direct memory commands for immediate remember-or-forget changes, plus item-level create, read, update, and delete. In the latest preview, some store defaults, such as the default TTL, are configured when the store is created, so check whether your API version supports changing them afterward. Consolidation merges duplicates and resolves conflicting facts, and Foundry memory is designed for long-term memory.
Deep dive
How it works
Memory in Foundry Agent Service (preview) is designed for long-term memory, and it includes management and retention controls for production. Two of them match the privacy rules directly:
- Store-level default retention: set a default TTL (in seconds) for memory entries created in a store, so memories expire on their own.
- Direct memory commands: apply immediate remember-or-forget behavior when users explicitly request memory changes, such as "forget my home address".
Also available is item-level memory CRUD: create, read, update, list and delete individual memory items. That's useful for admin tools and data-subject requests.
One preview detail: in the latest preview, some memory store defaults, such as the default TTL, are configured at store creation time. Microsoft says to verify whether your API version supports changing them after creation, so set the TTL when you create the store.
The other options, and when you'd use them
- Short-term session memory: Foundry memory is designed for long-term memory, not session-only memory.
- Rely on consolidation: Consolidation keeps the store efficient and relevant by consolidating extracted memories. It isn't described as a way to honor a user's forget request. Direct memory commands are.
- Delete and re-create the store: Item-level CRUD lets you delete individual memory items, and direct commands handle explicit forget requests.
Exam tip
Auto-expiry = store-level default TTL (set at creation in the latest preview). "Forget this" now = direct memory commands. Single item = item-level CRUD.
References
Last reviewed: