Select the answer that correctly completes the sentence.

When content is submitted to Azure Content Understanding in Foundry Tools, the analysis is asynchronous . This means the service does not return results immediately within the same HTTP request. Instead, it uses the standard Azure long-running operation (LRO) pattern — you call begin_analyze() to submit the content, which immediately returns a poller object, and then call poller.result() to wait for processing to complete and retrieve the structured extraction results.

Why the other options are wrong:

Synchronous is incorrect — the analysis pipeline involves multiple AI steps (OCR, speech transcription, schema mapping) that take time; a blocking synchronous call is not supported.

Returned only as unstructured plain text is incorrect — Azure Content Understanding returns richly structured JSON output with named fields mapped to your defined schema, not plain unstructured text.

Limited to OCR-only processing is incorrect — Content Understanding goes far beyond OCR; it supports document, audio, image, and video analyzers, and performs semantic field extraction using AI, not just character recognition.

This asynchronous design is consistent across all Azure AI services that perform complex, multi-step content processing.