A 40-person operations team spends 12 hours weekly copying vendor invoices from email into a tracker, checking totals against purchase orders, and routing mismatches to finance. The process is rule-based, high-volume, and error-prone. Which use case should the manager prioritize for optimization by an agentic workflow?

The correct response is right because it preserves the full end-to-end workflow described in the scenario: weekly intake from email, extraction into the tracker, validation of invoice totals against purchase orders, and active routing of mismatches to finance, which matches the textbook profile for agentic automation as rule-based, high-volume, and error-prone with clear decision logic and handoffs. The budget-validation alternative fails on control concept because checking totals against budgets supports spend governance but does not perform the required three-way operational match against purchase orders, so PO discrepancies would still require manual rework. The archiving alternative fails on workflow closure because passively storing exceptions for later audit breaks the stated handoff to finance for timely resolution, turning an actionable routing step into record-keeping and leaving the bottleneck intact. The daily-intake alternative fails on scoping and cadence because redefining a defined 12-hour weekly batch as continuous daily processing misstates volume, staffing, and scheduling assumptions used to justify prioritization. As an exam caveat, beware attractive choices that improve one step while quietly substituting source documents, destinations, or timing, since certification questions test precise fit to stated facts rather than general usefulness. As a practical check, confirm email volume, PO match rate, and finance service-level expectations for exceptions before automating to ensure extraction accuracy and routing rules actually eliminate the manual hours.