AI-103 Practice Question 90: Knowledge Store Projections
Microsoft Azure AI Apps and Agents Developer Associate (AI-103) · Test 9 · question 10 of 10
An enterprise runs an Azure AI Search indexer and skillset over scanned invoices, extracting key phrases, entities, and structured line-item tables. Separately, the data engineering team wants to run Power BI dashboards and a nightly Azure Data Factory job over that same enriched, extracted content (the tables and the per-document structured data) entirely independent of the search index, without querying Azure AI Search at query time. They also want the freedom to later change the search index's technology without breaking that downstream pipeline.
What should they add, and where does the enriched content land?
Show answer and explanation
Answer:
A knowledge store is secondary storage for a skillset's AI-enriched output, physically Azure Table Storage, Azure Blob Storage, or both. Table projections give tabular structures for tools like Power BI or Data Factory, and object projections write a hierarchical JSON document per enriched item to Blob Storage. Microsoft states the decoupling directly: "Any tool or process that can connect to Azure Storage can consume the contents of a knowledge store," and "there's no query support in Azure AI Search for retrieving content from a knowledge store", so the downstream pipeline never touches the search index or its query API, satisfying both the independence and the future index-technology-change requirements.
- A is wrong because semantic ranker is a query-time relevance feature for the search index itself; using it still means Power BI queries Azure AI Search, which is exactly the coupling the team wants to remove. - C is wrong because it's the plausible trap: knowledge store projections are Azure Table Storage and Blob Storage only. Cosmos DB isn't a documented knowledge store projection target; it's the technology behind a different feature (Foundry Agent Service's bring-your-own thread storage), not this one. - D is wrong because a second search index still requires Power BI and Data Factory to query Azure AI Search, and it doubles indexing cost and complexity instead of decoupling anything.
Reference: Knowledge store concepts