AI-102 Practice Question: Implement knowledge mining and information extraction solutions

Correct answer & explanation

To filter by file type, set a data change detection policy or use a container query. However, the simplest way is to set a file extraction filter or use a custom indexer parameter. Option D is correct: set the 'dataToExtract' to 'contentAndMetadata' and add a 'parsingMode' for PDF. But the best answer is to set a query parameter to filter by .pdf extension. Option A is incorrect because connection string doesn't filter. Option B is incorrect because container name can't have filters. Option C is correct: set the 'query' field to filter by .pdf. Actually, the query field in the container object can be used to specify a blob prefix. For example, "*.pdf" is not valid; you need to use a prefix. The correct approach is to set a custom indexer parameter 'parsingMode' to 'jsonArray'? No. The proper way is to set the 'dataToExtract' to 'contentAndMetadata' and use a skillset to filter. However, the simplest is to change the container query to filter by folder or prefix. Typically, you would set the container query to a folder that contains only PDFs. Option C is plausible: set the query to filter by .pdf extension. But note that blob storage does not support wildcard queries in the container query; you need to set a prefix. Option D is incorrect because you cannot set file type in connection string. The correct answer is C: set the 'query' field to a prefix that includes only PDFs. However, the exhibit shows empty query. To filter PDFs, you would set a prefix like 'pdf/' if they are in a folder. But the question expects to set the 'parsingMode' to 'jsonArray'? No. Let me think: Azure AI Search has a feature to filter by file type using the 'parsedContent' skill. But the simplest is to set a data change detection policy. Actually, the correct answer is: Option C: Set the 'query' field to a blob prefix that corresponds to PDF files. But since the exhibit has empty query, you can set it to a folder. However, the distractors: Option A: Change the connection string -> no. Option B: Change the container name -> no. Option C: Set the 'query' field to filter by .pdf extension -> this is not directly supported; you need to use a prefix. Option D: Add a 'fileExtension' parameter to the container -> not a valid property. The correct way is to use a custom indexer parameter 'excludedFileNameExtensions' or 'includedFileNameExtensions' in the indexer's parameters. So the answer is: modify the indexer parameters to include only PDF files. But the question asks to modify the data source. Since the data source does not support file extension filtering, the best answer is to change the container query to point to a folder that contains only PDFs. Option C is the closest. I'll go with C.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.