1.1: Architecture and Runtime Selection
1.An expense agent may approve small claims by itself, but policy says any claim above a fixed amount needs a named human's sign-off, recorded for audit. How should this be built into the architecture?
- A.Put a rule in the system prompt requiring sign-off over the limit, and have the agent log the approver
- B.Add a code-level check that halts the run over the limit until a person signs off, and log the approver
- C.Add a reviewer model that screens claims over the limit for risk, and log its verdict as the approval
- D.Let the agent flag claims it judges risky for sign-off, and log the approver when one is requested
Show answer & explanation
Correct answer: B — Add a code-level check that halts the run over the limit until a person signs off, and log the approver
- A. Incorrect: a prompt rule is an instruction the model can misread, skip or be talked out of, so a mandatory sign-off would not be enforced. A log the agent writes itself is also not a trustworthy audit record of who approved.
- B. Correct: the policy is mandatory and needs an audit trail, so it must not depend on model compliance. A deterministic check outside the model that stops processing above the amount until a person signs off, and records that person, enforces both parts.
- C. Incorrect: a second model's risk screening is probabilistic and cannot stand in for a named human's approval. Claims it rates as low risk would pass without sign-off, and its verdict is not a record of who approved.
- D. Incorrect: this leaves the decision to the agent's own judgement of risk instead of the fixed amount. A large claim the agent considers safe would be approved with no human sign-off, so the policy is not enforced.