One pipeline must handle documents, images, audio and video in a defined output format. What fits?
Why C is the answer
Content Understanding
Content Understanding ingests these content types into a user-defined format.
In detail
- Content Understanding handles documents, images, audio and video.
- It returns a format you define.
- Define one schema for all content types.
Use case
An illustrative scenario, not a real incident.
A media firm handles documents, images, audio and video in one output format. Content Understanding covers them all.
See it in different ways
flowchart TD
A{"Source content"} -->|"Structured documents, exact fields"| B["Document Intelligence"]
A -->|"Documents, images, audio, video"| C["Content Understanding"]
B --> D["Structured output"]
C --> D
D --> E["Search index or agent"]stateDiagram-v2 [*] --> Extract Extract --> Review: low confidence Extract --> Index: high confidence Review --> Index: corrected Index --> [*]
mindmap
root(("Content Understanding"))
n1["Inputs"]
n2["Documents"]
n3["Images"]
n4["Audio"]
n5["Video"]
n6["Output"]
n7["Your defined format"]Key point: Content Understanding spans many content types.
Why the other options are wrong
- A. A managed identity for each type of content
- An identity is about access.
- B. Azure Translator
- Translator handles text.
- D. Prompt Shields
- Prompt Shields detect attacks.