Implement knowledge mining and information extraction solutions →hardMultiple ChoiceObjective-mapped
AI-102 Practice Question: Implement knowledge mining and information extraction solutions
You are designing an enterprise search solution using Azure AI Search. The solution must index data from multiple sources: SQL Database, SharePoint Online, and custom REST APIs. The search index must support faceted navigation and filtering by metadata such as department and document type. You also need to ensure that updates to source data are reflected in the index within 5 minutes. Which approach should you use?
⚠ Common exam trap
Watch out — candidates often assume a single indexer can handle multiple data sources or that a custom indexer can be built for any source, when in reality each indexer is tied to one specific data source type and custom REST APIs require the push API.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure indexers for SQL and SharePoint, and use the push API for the REST API. Schedule indexers to run every 5 minutes.
It combines the strengths of indexers (for SQL Database and SharePoint Online, which have native connectors) with the push API for custom REST APIs, which lack a built-in indexer. Scheduling the indexers to run every 5 minutes ensures that updates are reflected within the required latency window, while the push API can be triggered on demand or via a polling mechanism to meet the same 5-minute SLA.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use the push API to index all data from a custom application that polls all sources.
Why it's wrong here
Requires custom polling and does not leverage built-in indexers.
- ✗
Create a single indexer that reads from all three sources using a data source definition.
Why it's wrong here
An indexer can only have one data source.
- ✗
Use only indexers for all sources by creating a custom indexer for the REST API.
Why it's wrong here
Using only indexers, even with a custom indexer for the REST API, would rely on a scheduled pull mechanism. This approach struggles to guarantee updates within the strict 5-minute latency requirement for the custom REST API source, as indexers are inherently pull-based and might not capture changes immediately. This option is tempting because indexers provide a unified, declarative way to ingest data from many sources, including custom ones via a custom data source definition, making them suitable when update frequency is less critical or when the source system cannot actively push changes.
- ✓
Configure indexers for SQL and SharePoint, and use the push API for the REST API. Schedule indexers to run every 5 minutes.
Why this is correct
Combines indexers for native sources and push API for custom data.
Go deeper
Related to this question
About these practice questions
Courseiva writes every AI-102 question from scratch — 945 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AI-102 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AI-102 exam.