AIP-C01 practice question: Building agents (Strands Agents, AgentCore Runtime, multi-agent patterns) (1 of 2)
Implementation and Integration A free question from our original AIP-C01 practice exam. Try it, then open the answer to see why each option is right or wrong.
A tax preparation software company has built a conversational agent with the open-source Strands Agents SDK. The agent calls a model on Amazon Bedrock and three internal tools, and each user session can hold personal tax documents.
The company wants to move the agent off a shared container and into a managed runtime. Each user session must run in its own isolated environment, so that one customer's files and in-memory state can never be read by another session. Sessions can last several hours, and the team does not want to manage clusters or patch hosts.
Which deployment meets these requirements with the LEAST operational overhead?
Choose one answer.
AA. Rewrite the agent as an AWS Lambda function behind Amazon API Gateway, and store each user's session state under a separate prefix in a DynamoDB table.
BB. Deploy the agent on an Amazon EKS cluster with one namespace for each customer and network policies that block traffic between namespaces.
CC. Run the agent on an Amazon EC2 Auto Scaling group that starts one instance per active user session, with a user data script that installs the agent.
DD. Deploy the Strands agent to Amazon Bedrock AgentCore Runtime, which runs each user session in its own isolated microVM and needs no clusters or hosts.
Show the answer and explanation
Answer: D
A. Wrong: Lambda handles short requests well, but its 15-minute limit makes multi-hour sessions awkward. Isolation then depends on application code that filters keys, not on a per-session boundary the platform enforces.
B. Wrong: Namespaces separate resources logically, but pods from different customers still share nodes and a kernel. The platform team would also run cluster upgrades, node patching and scaling, which the company wants to avoid.
C. Wrong: A dedicated instance per session gives strong isolation, but instances take minutes to start and cost money while idle. The team would still manage AMIs, patching and scaling policies for the fleet.
D. Right: AgentCore Runtime is a serverless host for agents built with frameworks such as Strands Agents, so the team manages no clusters or hosts. It meets the session isolation rule by design, which removes the need for custom isolation code. Learn more: Overview of Amazon Bedrock AgentCore (opens in a new tab)
Explanation
AgentCore Runtime hosts agents built with any framework, including Strands Agents, and gives each session its own isolated microVM with no infrastructure for the team to run. Lambda, EKS namespaces and per-session EC2 instances each leave either a weaker isolation boundary or more infrastructure to operate.
Want more on Building agents (Strands Agents, AgentCore Runtime, multi-agent patterns)? The 5 full-length practice sets have 6 more Building agents (Strands Agents, AgentCore Runtime, multi-agent patterns) questions, 375 in all, none of them in the free exam. One payment of $14.99, no subscription. See the practice sets →