You need to extract text from a multi-page PDF document using Azure AI Vision Read API. How are pages represented in the JSON response structure?
The Read API's analyze result groups extracted content by page, exposing each under a 'readResult.pages' or 'pages' array, with lines and words nested beneath. This structure satisfies the stem's multi-page PDF scenario by keeping per-page results addressable.
Why this answer
The Read API (and the newer Image Analysis/Read model) returns an analyze result that includes a pages array (or readResult.pages in older SDK shapes), where each page contains lines, words, and their bounding polygons plus angle and dimensions. This page-level structure lets you map extracted text back to specific pages of a multi-page PDF.
Exam trap
The trap is assuming the Read API requires one call per page or returns a flat string; candidates overlook the asynchronous single-call, page-array response model.
How to eliminate wrong answers
Option B is wrong because the Read API does not merge all pages into one unstructured string; it preserves page boundaries with per-page line and word arrays. Option C is wrong because the API returns JSON, not a ZIP of JPEGs; image rendering is a separate concern and not part of the Read response. Option D is wrong because a single POST to the Read/analyze endpoint processes the entire multi-page PDF asynchronously and returns all pages in one result — you do not need one transaction per page.