Least-Overhead Agentic Solution for Freight Optimization
A logistics company is building an agentic GenAI-powered solution to automate freight optimization. The solution must retrieve data in real time from multiple internal and external systems. The solution must include a human-in-the-loop approval step before the optimization process is finished. The solution must support modular growth as the number of integrations and amount of logic increases. Which solution will meet these requirements with the LEAST operational overhead?
Community Insight
The question tests choosing an agentic architecture that satisfies real-time retrieval, human approval, and modular scalability at once; the trap is picking a single-agent design that looks simpler but collapses as integrations multiply.
This scenario asks which agentic GenAI architecture delivers real-time multi-system retrieval, a human-in-the-loop approval gate, and modular growth with the least operational overhead. The analysis shows a coordinated multi-agent system built on the Strands Agents SDK and Amazon Bedrock AgentCore, with MCP messaging and AWS Step Functions for approval, satisfies every constraint.
Option D is the most tempting wrong pick because a single Bedrock AgentCore agent with Lambda tools appears to have the fewest moving parts, but it forces every new integration into one agent's tool list, defeating the stated modular-growth requirement.
Community Discussion (1 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option B satisfies all three stated constraints simultaneously: specialized agents delegate through a coordinator so each new system integration is added as a new agent rather than another tool bolted onto one prompt, MCP standardizes inter-agent messaging instead of custom glue code, and AWS Step Functions provides a managed pause/resume (waitForTaskToken) pattern for human approval without building a bespoke UI. Because Bedrock AgentCore and Step Functions are managed services, the coordination, state, and retry logic is handled by AWS, which is what keeps operational overhead low while still delivering real-time tool invocation. Step Functions also keeps the approval step durable and auditable, which a hand-rolled web app in Option A does not. This is the pattern AWS documents for scalable multi-agent collaboration, and as TNT87 chose, it is the answer that best matches the requirement wording.Why the Other Options Are Wrong
Option A has an LLM endpoint directly calling databases and external APIs, which couples model logic to data access, provides no orchestration layer, and requires a custom web application for approval—highest overhead and weakest governance. Option C is batch-oriented: Glue, S3, and Athena aggregate data on a schedule, so it cannot retrieve data in real time, and SNS notifications to supervisors are not a controlled approval workflow. Option D, a single agent with Lambda tools plus Step Functions, does deliver managed approval, but it concentrates all internal and external integrations into one agent, so tool count, prompt size, and blast radius grow unboundedly, directly violating the modular-growth requirement. As integrations and logic accumulate, Option D's maintenance cost exceeds Option B's despite looking simpler today.Community Comment Notes
The lone community comment supports Option B, with TNT87 stating "Build a hierarchical system by using the Strands Agents SDK and Amazon Bedrock AgentCore" as the pick. The reasoning aligns with the question's emphasis on delegating tasks to specialized agents and using MCP for inter-agent messaging. No dissenting comments were posted, so the vote record offers corroboration rather than independent evidence—the decision above rests on the requirement wording and AWS's documented multi-agent pattern.Official Reference
Exam Strategy
Read the constraints first and score each option against every one of them before judging simplicity; a design that fails even one hard requirement (real time, human approval, modular growth) can never be the least-overhead answer. Reserve the term "least operational overhead" for the option that meets all requirements using managed services rather than the one with the fewest named components.
Frequently Asked Questions
Why is a single Bedrock AgentCore agent with Lambda tools not the least-overhead option?
It looks simpler today, but every new internal and external system becomes another tool in one agent's prompt, so complexity, prompt bloat, and failure impact grow unbounded—breaking the modular-growth requirement.
How does AWS Step Functions provide the human-in-the-loop approval?
Step Functions pauses the workflow using a callback token, waits for an approver to approve or reject the optimization, then resumes or terminates the run with a durable, auditable record.
Related Analysis
Practice All AIP-C01 Questions
Access 110 questions with complete answers and detailed explanations.
View Full AIP-C01 Practice Test →