A company uses this skillset in an Azure AI Search enrichment pipeline. They notice that the enrichment pipeline fails when processing a document larger than 5000 characters. What is the most likely cause?
The output 'pages' must be mapped to a collection field in the index.
Why this answer
The enrichment pipeline fails because the output field mapping is missing or incorrect. When a skillset processes documents, the output of each skill must be explicitly mapped to an index field; if this mapping is absent or misconfigured, the pipeline cannot store the enriched data and fails, especially for larger documents that produce more output data.
Exam trap
The trap here is that candidates often attribute pipeline failures to text splitting or language settings, but the real issue is the missing output field mapping, which is a common misconfiguration in skillset definitions.
How to eliminate wrong answers
Option A is wrong because the maximum page length setting in the text split skill controls chunk size, not the overall document size limit; a 5000-character document is well within typical limits. Option B is wrong because an unsupported language code would cause a language detection or translation skill error, not a generic pipeline failure tied to document size. Option C is wrong because the text split mode (e.g., 'pages' vs 'sentences') affects how text is chunked, but does not cause a pipeline failure solely due to document size; the failure is related to output mapping, not splitting logic.