An insurer wants to extract named fields such as policy number, claimant name, and total amount from millions of scanned claim PDFs that follow a small set of fixed layouts. The team needs structured key-value output, high accuracy on these specific forms, and the lowest ongoing per-document cost rather than free-form reasoning. Which Google Cloud approach best fits this requirement?
- APrompt a general Gemini model with each page image and ask it to return the fields as JSON, relying on its multimodal reasoning over the scans.
- BTrain a Document AI custom extractor on the known layouts so it returns the policy fields as structured key-value pairs per document. Correct
- CUse the Vision API text detection feature to read all characters, then write rules to locate each field by its position on the page.
- DTranslate every document with the Translate API first to normalise the text, then apply a keyword search to pull out the required values.
Why A is wrong: Gemini can read documents, but per-document inference on millions of pages is costly and its general reasoning is less consistent for fixed-layout field extraction than a model trained on those forms, so it does not meet the accuracy-and-cost goal best.
Why B is correct: Document AI custom extractors are purpose-built to learn fixed layouts and emit structured key-value entities with high accuracy at a predictable per-page price, which directly satisfies the structured-output, accuracy, and low-cost requirements.
Why C is wrong: Vision text detection returns raw characters without document structure, so brittle position rules are needed to recover key-value pairs; this tempts teams who think OCR alone is enough but it lacks the form understanding Document AI provides.
Why D is wrong: Translate changes language and does nothing to detect layout or extract structured fields, so it is the wrong service entirely for a same-language field-extraction task even though it sounds like a preprocessing step.