AI-102 Plan and manage an Azure AI solution Practice Question
Exhibit
Refer to the exhibit.
{
"name": "MyBot",
"kind": "bot",
"location": "westus",
"properties": {
"displayName": "MyBot",
"description": "Customer service bot",
"endpoint": "https://mybot.azurewebsites.net/api/messages",
"msaAppId": "12345678-1234-1234-1234-123456789012",
"luisAppIds": [],
"developerAppInsightsKey": "<key>",
"developerAppInsightsApplicationId": "<appId>"
}
}You see the exhibit representing an Azure Bot resource configuration. The bot is not responding to user messages. What should you verify first?
⚠ Common exam trap
The trap here is that candidates often jump to authentication or AI service configuration issues, but the most immediate and common cause of a non-responsive bot is a simple connectivity or endpoint misconfiguration.
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
✓
Check that the endpoint URL is correct and the web app is running
The most common reason a bot fails to respond to user messages is that the endpoint URL configured in the Azure Bot resource does not match the actual URL of the running web app, or the web app itself is stopped or unresponsive. Without a correct and reachable endpoint, the Bot Framework Service cannot forward messages to the bot's message handler, causing a complete communication breakdown.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Check that the endpoint URL is correct and the web app is running
Why this is correct
A bot that receives messages but never replies usually has a broken messaging endpoint. Verifying the endpoint URL and confirming the hosting web app is running tests the actual message delivery path before investigating channels, credentials, or configuration.
- ✗
Ensure that LUIS app IDs are provided
Why it's wrong here
LUIS app IDs only matter once the bot reaches natural-language understanding; a bot that never responds fails earlier, at channel or endpoint configuration. Supplying LUIS IDs is tempting because intent recognition is central to conversational bots, but it would be the right check when the bot replies yet misinterprets utterances.
- ✗
Verify that the Application Insights key is valid
Why it's wrong here
Application Insights telemetry records bot conversations and errors but does not govern message routing, so an invalid key would not stop replies. It tempts because telemetry is bot-adjacent, yet the messaging endpoint and channel registration must be verified first.
- ✗
Confirm that the msaAppId is a valid GUID
Why it's wrong here
A malformed msaAppId GUID would prevent the bot's channel registration from authenticating, but the exhibit already shows a syntactically valid value, so this check yields nothing. Verifying the app ID is tempting because authentication failures do stop responses, yet the first check should target the messaging endpoint configuration.
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.