AI-102 Practice Question: Implement natural language processing solutions
A company uses Azure AI Language Service with Custom Entity Recognition to extract invoice fields. The model correctly extracts invoice numbers but fails to extract dates in the format 'dd/mm/yyyy'. The training data includes dates in 'mm/dd/yyyy' format. What is the most likely issue?
⚠ Common exam trap
Test-takers frequently assume the model can infer date formats from context or that language detection handles locale-specific formatting, but Custom Entity Recognition strictly learns from labeled examples and does not apply automatic format normalization.
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
✓
The training data does not contain examples with the 'dd/mm/yyyy' format
Custom Entity Recognition in Azure AI Language Service learns patterns from labeled training data. Since the training data only contains dates in 'mm/dd/yyyy' format, the model has not seen any examples of 'dd/mm/yyyy' and therefore cannot generalize to that format. The model relies on the exact token sequences and date structures present in the training set, so missing format variations directly cause extraction failures.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The training data does not contain examples with the 'dd/mm/yyyy' format
Why this is correct
Custom Entity Recognition learns patterns from labelled examples, so a model trained only on 'mm/dd/yyyy' dates has no signal for the day-first format. Adding 'dd/mm/yyyy' examples is required for it to extract those dates correctly.
- ✗
The dates exceed the maximum entity length
Why it's wrong here
Date strings are short, well within entity length limits, so truncation cannot explain the misses. Length limits are tempting because they do cause extraction failures, but only for long spans; here the training data simply lacks the dd/mm/yyyy format the model must learn.
- ✗
The language detection is incorrectly identifying the locale
Why it's wrong here
Custom Entity Recognition is language-agnostic regarding date formatting; locale detection does not cause a model trained on mm/dd/yyyy to miss dd/mm/yyyy strings. Locale settings matter for built-in prebuilt entities, not custom extraction, so this misattributes the failure to the wrong component.
- ✗
The model is overfitting to invoice numbers
Why it's wrong here
Overfitting would degrade all labels, yet invoice numbers extract correctly, so the model is not over-committed to that entity. Overfitting is tempting whenever one label performs well, but the real gap is that training examples never showed the dd/mm/yyyy pattern the model must recognise.
Go deeper
Related to this question
About these practice questions
This AI-102 question is part of Courseiva's 761-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.