Question

A financial services company builds a Bedrock Agent that handles loan pre-qualification. The agent must call three action groups in sequence (credit check, income verification, and eligibility calculation), but developers observe that the agent frequently skips the income verification step and calls the eligibility calculator prematurely with incomplete data. The action group definitions and function schemas are correct, and each Lambda works when invoked directly. Which approach most directly addresses the agent's flawed step selection during orchestration?

Accepted Answer

Customize the orchestration prompt template in the agent's advanced prompt configuration to explicitly instruct the model on the required sequence and preconditions before invoking eligibility calculation.

Answer

Enable Provisioned Throughput for the agent's foundation model so it has enough capacity to evaluate all action groups.

Answer

Increase the Lambda timeout and memory for the income verification action group so it completes before the eligibility step runs.

Answer

Attach a Bedrock Guardrail that blocks responses when required fields are missing from the eligibility output.