The correct answer is to update the index schema to add the new field using the portal or REST API, then update the indexer to map the field. This works because Azure AI Search supports adding new fields to an existing index without reindexing all documents, provided the new field is nullable or has a default value—since 'promotionPrice' is an Edm.Double, it is nullable by default. On the AI-102 exam, this scenario tests your understanding of index schema evolution and indexer field mappings, a common trap being the mistaken belief that any schema change forces a full rebuild. The key exam context is that the indexer’s next scheduled run will automatically populate the new field for existing documents, while new documents include it from the start. Memory tip: think “schema first, map second”—update the index definition before touching the indexer’s field mappings, or the indexer will have nowhere to write the data.
AI-102 Plan and manage an Azure AI solution Practice Question
This AI-102 practice question tests your understanding of plan and manage an azure ai solution. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Your company has an existing Azure AI Search index used for e-commerce product search. The index is populated by an indexer that runs every hour. Recently, the product team added a new field 'promotionPrice' that should be searchable. You need to update the index to include this field without reindexing all documents. The field should be of type Edm.Double, searchable, filterable, and sortable. What should you do?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Update the index schema to add the new field using the portal or REST API. Then update the indexer to map the field.
Option B is correct because Azure AI Search allows you to add new fields to an existing index schema without reindexing all documents, as long as the new field is nullable or has a default value. After updating the index schema via the portal or REST API, you must update the indexer's field mappings to map the new 'promotionPrice' field from the data source to the index. The indexer will then populate the field for existing documents on its next run, and new documents will include the field automatically.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Add the new field to the data source mapping in the indexer. The indexer will automatically update the index schema.
Why it's wrong here
The indexer does not automatically update the schema; you must update the index first.
✓
Update the index schema to add the new field using the portal or REST API. Then update the indexer to map the field.
Why this is correct
No downtime; incremental update.
Related concept
Read the scenario before looking for a memorised answer.
✗
Change the indexer schedule to run every 5 minutes to pickup the new field faster.
Why it's wrong here
The indexer cannot add fields automatically; schema must be updated.
✗
Delete the index and recreate it with the new field. Then run the indexer to repopulate all documents.
Why it's wrong here
Causes downtime and unnecessary reindexing.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume the indexer can automatically update the index schema when a new field is added to the data source, but Azure AI Search requires explicit schema updates before the indexer can map and populate the new field.
Detailed technical explanation
How to think about this question
Under the hood, Azure AI Search uses a schema-on-write model where the index schema is defined independently of the data source. When adding a new field to an existing index, the field must be nullable (or have a default value) to avoid breaking existing documents that lack the field. The indexer's field mappings translate source fields (e.g., from a SQL database or blob storage) to index fields; if the mapping is missing, the indexer will ignore the source field. In a real-world scenario, if you add a field without updating the mapping, the indexer will not populate it, and you would need to run a full reindex to backfill existing documents.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Plan and manage an Azure AI solution — This question tests Plan and manage an Azure AI solution — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Update the index schema to add the new field using the portal or REST API. Then update the indexer to map the field. — Option B is correct because Azure AI Search allows you to add new fields to an existing index schema without reindexing all documents, as long as the new field is nullable or has a default value. After updating the index schema via the portal or REST API, you must update the indexer's field mappings to map the new 'promotionPrice' field from the data source to the index. The indexer will then populate the field for existing documents on its next run, and new documents will include the field automatically.
What should I do if I get this AI-102 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.