You are designing a Claude application that maintains user sessions across multi-turn conversations.

A is the correct lifecycle architecture. The supplied Claude Certified Developer Foundations item explicitly selects A . A session is a state boundary, so its lifecycle must define when accumulated conversation state remains valid and when that state must be discarded. Anthropic's Managed Agents documentation establishes that a session maintains conversation history across multiple interactions and provides explicit session operations including creation, update, archive, and deletion.

A therefore addresses all three required controls: expiration , reset , and fresh-session creation . Expiration prevents indefinitely retained conversational state. Reset triggers allow the application to clear state when events such as logout, workflow completion, tenant switching, or explicit user reset occur. Fresh-session rules prevent context belonging to an earlier task from influencing a logically unrelated conversation.

B relies exclusively on timeout and does not cover event-driven resets. C places lifecycle correctness on users instead of the application. D applies global reset behavior and omits independent per-session expiration semantics.

Relevant Claude Developer topics: Agent Architecture, session lifecycle, multi-turn state, context boundaries, state reset, stale-context prevention, and session management .

===============