AI-102 Practice Question: Implement natural language processing solutions
You are building a chatbot using Azure AI Language and need to handle user intents that are not covered by the predefined intents. What should you implement?
⚠ Common exam trap
Test-takers frequently confuse the 'None' intent with a fallback mechanism in QnA Maker or assume that custom entities can substitute for intent handling, leading them to pick options that address different aspects of NLP processing rather than the specific requirement for unrecognized intents.
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
✓
A 'None' intent in a conversational language understanding project
In a Conversational Language Understanding (CLU) project, the 'None' intent is specifically designed to capture utterances that do not match any of the defined intents. This intent acts as a catch-all for unrecognized user inputs, ensuring the chatbot can gracefully handle out-of-scope or ambiguous queries without misclassifying them into a predefined intent.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Custom entities to capture unknown phrases
Why it's wrong here
Custom entities extract values from utterances; they do not define or route unmatched intents, so unknown requests remain unhandled. They are tempting because entity extraction is central to conversational AI, and it is the right choice when you need to pull domain-specific terms such as product names from user text.
- ✗
A fallback intent in the QnA Maker knowledge base
Why it's wrong here
A QnA Maker fallback handles questions with no matching knowledge-base answer; it does not classify unmatched conversational intents, so the chatbot still cannot route them. It is tempting because fallback behaviour sounds equivalent, and it is correct for question-answering bots that must respond gracefully to unknown FAQs.
- ✓
A 'None' intent in a conversational language understanding project
Why this is correct
A 'None' intent in conversational language understanding captures utterances matching no predefined intent, satisfying the requirement to handle uncovered user intents. Microsoft Entra ID is unrelated here; the mechanism is intent classification fallback, where unmatched utterances route to 'None' so the chatbot can respond gracefully rather than misclassifying them.
- ✗
A prebuilt intent from the LUIS catalog
Why it's wrong here
A prebuilt LUIS intent recognises a fixed catalogue of common intents, so it cannot cover intents specific to this application that fall outside that catalogue. It is tempting because prebuilt models remove training effort, and they are correct when your scenario matches a supported domain such as calendar or email.
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.