AIP-C01 practice question: Tool integration and MCP servers (Lambda, ECS, AgentCore Gateway) (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 retail analytics team wants its generative AI assistant to call internal tools through the Model Context Protocol (MCP). Four of the tools are light: each returns in about two seconds, keeps no state between calls, and is called only a few times an hour. The fifth tool runs a demand forecast that takes about 40 minutes and keeps a large model loaded in memory between calls.

The team does not want to patch servers for the light tools, and it wants them to cost almost nothing when nobody is using the assistant. The forecast tool must keep its model warm and must finish a 40-minute job.

Which TWO actions meet these requirements? (Choose two.)

Choose two answers.

A. Implement the four light tools as stateless AWS Lambda functions, and add them as Lambda targets in Amazon Bedrock AgentCore Gateway, which exposes them as MCP tools.
B. Host the forecast tool on AWS Lambda with provisioned concurrency, so that the model stays loaded in the warm execution environments between calls.
C. Run all five tools as one MCP server on a single Amazon EC2 instance in an Auto Scaling group with a minimum size of one, and patch the instance on a monthly schedule.
D. Run the forecast tool as an MCP server in a long-running task on Amazon ECS with AWS Fargate, where the model stays loaded in the task's memory between calls.
E. Place the four light tools in one Amazon ECS service with a minimum of two tasks, so that they stay available if one task fails.

Show the answer and explanation

Answers: A, D

A. Right: Stateless tools fit Lambda, which costs nothing while idle and has no servers to patch. AgentCore Gateway turns the Lambda functions into MCP tools that the assistant can discover and call. Learn more: Amazon Bedrock AgentCore Gateway (opens in a new tab)
B. Wrong: Provisioned concurrency keeps environments warm, but Lambda stops every invocation after 15 minutes, so a 40-minute job cannot finish. The design fails the forecast requirement.
C. Wrong: The instance runs and bills even when the assistant is idle, and the team must patch it. This fails both the idle cost requirement and the no-servers requirement for the light tools.
D. Right: A long-running container has no 15-minute limit, so a 40-minute forecast can finish, and the loaded model stays in memory between calls. Fargate removes the need to manage the underlying hosts.
E. Wrong: Two always-on tasks cost money every hour, even when no one is using the assistant. Availability is good, but it works against the idle-cost requirement for light tools.

Explanation

Lambda suits the light, stateless tools because it costs nothing while idle and needs no servers, and AgentCore Gateway presents those functions as MCP tools. The forecast needs a long-running container with its model in memory, since Lambda cannot run a job that lasts 40 minutes. Always-on servers, a provisioned Lambda forecast and always-on light tasks each miss one requirement.

AIP-C01 practice question: Tool integration and MCP servers (Lambda, ECS, AgentCore Gateway) (1 of 2)

Explanation

Study

Keep practicing