Question
You have a Microsoft Foundry project that processes procurement documents submitted by suppliers.
You need to implement two pipelines by using Azure Content Understanding in Foundry Tools. The solution must meet the following requirements:
- Include a pipeline named Pipeline1 that supports cost-effective, high-volume processing of standalone PDF invoices.
- Include a pipeline named Pipeline2 that supports cross-document validation by using multi-step reasoning and reference data.
How should you configure each pipeline? To answer, drag the appropriate configurations to the correct pipelines. Each configuration may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Explanation
Pipeline1 handles standalone invoices at high volume and low cost, so each file is its own task and standard mode provides straightforward field extraction without the extra reasoning cost. Pipeline2 must validate across documents by using reference data and multi-step reasoning, which calls for pro mode with multiple input files. Standard mode does not provide that reasoning, and pro mode on single files adds cost that Pipeline1 does not need and cannot compare documents for Pipeline2.
