Microsoft Updated AI-900 Exam Questions and Answers by clemmie

The correct answer is Azure AI Language, which includes the Question Answering capability (previously known as QnA Maker). According to the Microsoft Azure AI Fundamentals (AI-900) study guide and Microsoft Learn documentation, the Azure AI Language service can be used to create a knowledge base from frequently asked questions (FAQ) and other structured or semi-structured text sources.

This service allows developers to build intelligent applications that can understand and respond to user questions in natural language by referencing prebuilt or custom knowledge bases. The Question Answering feature extracts pairs of questions and answers from documents, websites, or manually entered data and uses them to construct a searchable knowledge base. This knowledge base can then be integrated with Azure Bot Service or other conversational platforms to create interactive, self-service chatbots.

Here’s how it works:

Developers upload FAQ documents, URLs, or structured content.

Azure AI Language processes the content and identifies logical question-answer pairs.

The model stores these pairs in a knowledge base that can be queried by user input.

When users ask questions, the model finds the best matching answer using natural language understanding techniques.

In contrast:

Azure AI Document Intelligence (Form Recognizer) is used to extract structured data from forms and documents, not to create FAQ knowledge bases.

Azure AI Bot Service is for managing and deploying conversational bots but does not generate knowledge bases.

Microsoft Bot Framework SDK provides tools for building conversational logic but still requires a knowledge source like Question Answering from Azure AI Language.

Therefore, the service that can create a knowledge base from FAQ content is Azure AI Language.

According to the Microsoft Azure AI Fundamentals (AI-900) official study guide and the Microsoft Learn module “Identify features of conversational AI workloads on Azure”, a Language Understanding (LUIS) model is designed to interpret natural language input by identifying intents (the purpose of an utterance) and entities (specific data items in the utterance).

Every LUIS model automatically includes a special intent called “None.” This intent is used to handle utterances that do not fall into any of the model’s defined intents. Adding examples of irrelevant or out-of-scope utterances to the None intent helps the model learn to recognize when a user’s input does not match any existing categories.

For example, if your e-commerce chatbot handles intents such as “TrackOrder” and “CancelOrder,” but a user says “What’s your favorite color?”, that input should be mapped to the None intent so the bot can respond appropriately, such as “I’m not sure how to answer that.”

The AI-900 curriculum emphasizes that including diverse None intent examples improves model robustness and prevents false matches, thereby enhancing user experience.

Other options are incorrect:

A. Test the model by using new utterances: Testing is important but does not define how to detect out-of-scope inputs.

C. Create a prebuilt task entity: Entities extract specific data but are unrelated to intent classification.

D. Create a new model: Unnecessary; handling out-of-scope utterances is done within the same model via the None intent.

✅ Final Answer: B. Add utterances to the None intent

A transformer model is the foundational architecture behind many modern natural language processing systems such as GPT and BERT. It processes text data through multiple key stages. According to the Microsoft Azure AI Fundamentals (AI-900) curriculum and Microsoft Learn materials, the major stages of a transformer-based large language model are tokenization, embedding calculation, and next token prediction.

Tokenization (C) – The first step converts raw text into smaller units called tokens (words, subwords, or characters). This process allows the model to handle text in a structured numerical form rather than as raw language.

Embedding Calculation (B) – After tokenization, the tokens are mapped into high-dimensional numeric vectors, known as embeddings. These embeddings capture semantic relationships between words and phrases so that the model can understand context and meaning.

Next Token Prediction (D) – This stage is the heart of transformer operation, where the model predicts the next likely token in a sequence based on prior tokens. Repeated next-token predictions enable text generation, summarization, or translation.

Options A (object detection) and E (anonymization) are incorrect because they relate to vision and privacy workflows, not language modeling.

According to the Microsoft Azure AI Fundamentals (AI-900) official study materials and the Microsoft Learn module: “Describe features of common AI workloads”, conversational AI solutions like chatbots can be created using various methods—not only through custom code. Azure provides both no- code/low-code and developer-focused approaches. For instance, users can design chatbots using Power Virtual Agents, which requires no programming knowledge, or they can use Azure Bot Service with the Bot Framework SDK for fully customized scenarios. Hence, the statement “Chatbots can only be built by using custom code” is False (No) because Azure supports multiple levels of technical involvement for building bots.

The second statement is True (Yes) because the Azure Bot Service is designed specifically to host, manage, and connect conversational bots to users across different channels. Microsoft Learn explicitly explains that the service provides integrated hosting, connection management, and telemetry for bots built using the Bot Framework or Power Virtual Agents. It acts as the foundation for deploying, scaling, and managing chatbot workloads in Azure.

The third statement is also True (Yes) because Azure Bot Service supports integration with Microsoft Teams, among many other channels such as Skype, Facebook Messenger, Slack, and web chat. Microsoft documentation states that Azure-hosted bots can communicate directly with Teams users through the Teams channel, enabling intelligent virtual assistants within the Teams environment.