Refer to the exhibit. You send this request to the Conversational Language Understanding API. The response includes the intent 'BookFlight' with entities 'FromCity: Seattle' and 'ToCity: Boston', but the 'Date' entity is missing. What is the most likely cause?
If the Date entity was not included in training, the model will not extract it.
Why this answer
The Conversational Language Understanding (CLU) API returns only intents and entities that the deployed model was explicitly trained to recognize. If the training data did not include labeled 'Date' entities, the model will not extract them regardless of the input text. The API itself supports entity extraction, and the endpoint and string index type settings do not affect whether a specific entity type is recognized.
Exam trap
The trap here is that candidates may assume the API automatically extracts common entities like dates (similar to LUIS's prebuilt entities), but CLU requires all entities to be explicitly defined and trained in the model.
How to eliminate wrong answers
Option A is wrong because the stringIndexType parameter (e.g., 'Utf16CodeUnit') controls how offsets are returned, not whether entities are extracted; it has no impact on entity recognition. Option B is wrong because all stable versions of the Conversational Language Understanding API (e.g., 2023-04-01) support entity extraction as a core feature. Option C is wrong because pointing to the wrong deployment would cause a deployment-not-found error or return results from a different model, but the response correctly returned the 'BookFlight' intent and two city entities, indicating the correct deployment was used.