Pass the Microsoft Microsoft Certified: Azure AI Fundamentals AI-900 Questions and answers with CertsForce

The Azure Text Analytics service, a component of Azure Cognitive Services, provides natural language processing (NLP) capabilities to analyze and understand text-based data. According to the Microsoft Azure AI Fundamentals (AI-900) official study guide and Microsoft Learn module “Identify features and uses for Natural Language Processing (NLP)”, the Text Analytics service supports multiple text understanding tasks, such as language detection, key phrase extraction, sentiment analysis, and entity recognition.

Language Identification – Yes:Text Analytics can automatically detect the language in which text is written. This feature analyzes linguistic patterns and assigns a language code (for example, “en” for English, “es” for Spanish). It is one of the primary features described in Microsoft Learn as part of the service’s Language Detection API.

Detect Handwritten Signatures – No:Detecting handwritten signatures is not a text-based NLP task. Instead, it belongs to the computer vision domain, specifically Optical Character Recognition (OCR). The Text Analytics service only processes digital text, not handwritten or image-based data. To detect handwriting or signatures, you would use the Computer Vision OCR API, not Text Analytics.

Entity Recognition – Yes:The Text Analytics service can identify named entities—such as people, locations, organizations, dates, and quantities—within documents. This is known as Named Entity Recognition (NER), which helps extract structured information from unstructured text.

Text extraction.

According to the Microsoft Azure AI Fundamentals (AI-900) study guide and Microsoft Learn documentation for Azure AI Vision (formerly Computer Vision), text extraction—also known as Optical Character Recognition (OCR)—is the computer vision capability that detects and extracts printed or handwritten text from images and video frames.

In this scenario, a traffic monitoring system collects vehicle registration numbers (license plates) from CCTV footage. These registration numbers are alphanumeric text that must be read and converted into digital form for processing, storage, or analysis. The Azure AI Vision service’s OCR (text extraction) feature performs this function. It analyzes each frame from the video feed, detects text regions (the license plates), and converts the visual text into machine-readable text data.

This process is widely used in Automatic Number Plate Recognition (ANPR) systems that support law enforcement, toll booths, and parking management solutions. The OCR model can handle variations in font, lighting, and angle to accurately extract license plate numbers.

The other options describe different vision capabilities:

Image classification assigns an image to a general category (e.g., “car,” “truck,” or “bike”), not text extraction.

Object detection identifies and locates objects in images using bounding boxes (e.g., detecting the car itself), but not the text written on the car.

Spatial analysis tracks people or objects in a defined physical space (e.g., counting individuals entering a building), not reading text.

Therefore, for a traffic monitoring system that identifies vehicle registration numbers from CCTV footage, the most accurate Azure AI Vision capability is Text extraction (OCR).

The correct completion of the sentence is:

“The interactive answering of questions entered by a user as part of an application is an example of natural language processing.”

According to the Microsoft Azure AI Fundamentals (AI-900) official study materials, Natural Language Processing (NLP) is a branch of Artificial Intelligence that focuses on enabling computers to understand, interpret, and respond to human language in a way that is both meaningful and useful. It is one of the key AI workloads described in the “Describe features of common AI workloads” module on Microsoft Learn.

When a user types a question into an application and the system responds interactively — such as in a chatbot, Q & A system, or virtual assistant — this process requires language understanding. NLP allows the system to process the input text, determine user intent, extract relevant entities, and generate an appropriate response. This is the foundational capability behind services such as Azure Cognitive Service for Language, Language Understanding (LUIS), and QnA Maker (now integrated as Question Answering in the Language service).

Microsoft’s study guide explains that NLP workloads include the following key scenarios:

Language understanding: Determining intent and context from text or speech.

Text analytics: Extracting meaning, key phrases, sentiment, or named entities.

Conversational AI: Powering bots and virtual agents to interact using natural language.These systems rely on NLP models to analyze user inputs and respond accordingly.

In contrast:

Anomaly detection identifies data irregularities.

Computer vision analyzes images or video.

Forecasting predicts future values based on historical data.

Therefore, based on the AI-900 official materials, the interactive answering of user questions through an application clearly falls under Natural Language Processing (NLP).

According to the Microsoft Azure AI Fundamentals (AI-900) learning path and Microsoft Learn documentation on GitHub Copilot, GitHub Copilot is powered by OpenAI Codex, a specialized language model derived from the GPT-3 family but fine-tuned specifically on programming languages and code data.

OpenAI Codex was designed to translate natural language prompts into executable code in multiple programming languages, including JavaScript, Python, C#, TypeScript, and Go. It can understand comments, function names, and code structure to generate relevant code suggestions in real time.

When a developer writes client-side JavaScript, GitHub Copilot uses Codex to analyze the context of the file and generate intelligent suggestions, such as completing functions, writing boilerplate code, or suggesting improvements. Codex can also explain what specific code does and provide inline documentation, which enhances developer productivity.

Option A (GPT-4): While some newer versions of GitHub Copilot (Copilot X) may integrate GPT-4 for conversational explanations, the core code completion engine remains based on Codex, as per the AI-900-level content.

Option C (DALL-E): Used for image generation, not for programming tasks.

Option D (GPT-3): Codex was fine-tuned from GPT-3 but has been further trained specifically for code generation tasks.

Therefore, the verified and official answer from Microsoft’s AI-900 curriculum is B. Codex — the OpenAI model used by GitHub Copilot to make suggestions for client-side JavaScript and other programming languages.

The Azure OpenAI Service provides access to advanced Generative Pre-trained Transformer (GPT) models developed by OpenAI, such as GPT-3, GPT-3.5, and GPT-4. These models are capable of performing a wide range of natural language processing (NLP) and generative AI tasks — including text completion, summarization, translation, question answering, content creation, and code generation.

According to the Microsoft Azure AI Fundamentals (AI-900) study guide and Microsoft Learn documentation for Azure OpenAI, this managed service allows developers to deploy and integrate GPT-based models within their own applications using REST APIs or the Azure SDK. The service handles scalability, performance, and infrastructure automatically, meaning users do not need to manage servers or computational resources manually.

Option review:

Supports the deployment of GPT-based models — ✅ Correct. Azure OpenAI is specifically designed for deploying and operationalizing GPT models and similar transformer-based architectures.

Provides capabilities exclusively for vision-related tasks — ❌ Incorrect. Vision tasks (like image classification or object detection) are part of Azure AI Vision.

Provides capabilities exclusively for speech-related tasks — ❌ Incorrect. Speech processing (speech-to-text, text-to-speech, translation) belongs to Azure AI Speech Services, not Azure OpenAI.

Requires manual infrastructure management for scalability — ❌ Incorrect. Azure OpenAI is a fully managed service; scalability and performance are handled automatically by Azure.

Therefore, the correct completion of the sentence is:

“Azure OpenAI Service supports the deployment of GPT-based models.”

In Azure OpenAI, grounding refers to the process of connecting the model to external data sources (for example, a database, search index, or API) so that it can retrieve accurate and up-to-date information before generating a response. This is particularly important for scenarios requiring current facts or events, since OpenAI models like GPT-3.5 and GPT-4 are trained on data available only up to a certain cutoff date.

By adding grounding data, the model’s responses are “anchored” to factual sources retrieved at runtime, improving reliability and factual accuracy. Grounding is commonly implemented in Azure OpenAI + Azure Cognitive Search solutions (Retrieval-Augmented Generation or RAG).

Option review:

A. Modify the system message: Changes model tone or behavior but doesn’t supply real-time data.

B. Add grounding data: ✅ Correct — allows access to recent and domain-specific information.

C. Add few-shot learning: Provides examples in the prompt to improve context understanding but not factual accuracy.

D. Add training data: Refers to fine-tuning; this requires retraining and doesn’t update the model’s awareness of current events.

Hence, the best method to ensure accurate and current responses from an Azure OpenAI model is to add grounding data, enabling the model to reference real, updated sources dynamically.

Privacy and security.

According to Microsoft’s Responsible AI Principles, implementing filters to block harmful or inappropriate content in a Generative AI chat solution demonstrates a commitment to the Privacy and Security principle. This principle ensures that AI systems are designed and operated in a way that protects users, their data, and society from harm.

When a chat system uses Generative AI models (like Azure OpenAI’s GPT-based services), there is a risk that the model might produce unsafe, offensive, or sensitive content. Microsoft addresses this through content filters and safety systems, which automatically detect and block violent, hate-based, or sexually explicit outputs. This is part of responsible deployment practices to ensure that user interactions remain safe, private, and compliant with ethical standards.

Implementing these filters aligns with the Privacy and Security principle because it:

Protects users from exposure to harmful or abusive content.

Ensures that conversations are safeguarded against malicious or unsafe use.

Upholds user trust by maintaining a safe digital environment for all participants.

Let’s briefly clarify why the other options are incorrect:

Fairness deals with ensuring unbiased treatment and equitable outcomes in AI decisions.

Transparency focuses on explaining how AI systems make decisions.

Accountability refers to human oversight and responsibility for AI actions.

Thus, content filtering mechanisms are explicitly an example of Privacy and Security, as they protect users and data from harm or misuse while maintaining ethical AI behavior.

Therefore, the verified correct answer is Privacy and security.

In the Microsoft Azure AI Fundamentals (AI-900) curriculum, computer vision capabilities refer to artificial intelligence systems that can analyze and interpret visual content such as images and videos. The Azure AI Vision and Face API services provide pretrained models for detecting, recognizing, and analyzing visual information, enabling developers to build intelligent applications that understand what they " see. "

When asked how computer vision capabilities can be deployed, the correct answer is to integrate a face detection feature into an app. This aligns with Microsoft Learn’s module “Describe features of computer vision workloads,” which explains that computer vision can identify objects, classify images, detect faces, and extract text (OCR). The Face API, a part of Azure AI Vision, specifically provides face detection, verification, and emotion recognition capabilities.

Integrating these services into an application allows it to perform actions such as:

Detecting human faces in photos or video streams.

Recognizing facial attributes like age, emotion, or head pose.

Enabling secure authentication based on face recognition.

The other options are incorrect because they relate to different AI workloads:

Develop a text-based chatbot for a website: This falls under Conversational AI, implemented with Azure Bot Service or Conversational Language Understanding (CLU).

Identify anomalous customer behavior on an online store: This task relates to machine learning and anomaly detection models, not computer vision.

Suggest automated responses to incoming email: This uses Natural Language Processing (NLP) capabilities, not visual analysis.

Therefore, the correct and Microsoft-verified completion of the statement is:

“Computer vision capabilities can be deployed to integrate a face detection feature into an app.”

In the most basic sense, regression refers to prediction of a numeric target.

Linear regression attempts to establish a linear relationship between one or more independent variables and a numeric outcome, or dependent variable.

You use this module to define a linear regression method, and then train a model using a labeled dataset. The trained model can then be used to make predictions.

Object detection is similar to tagging, but the API returns the bounding box coordinates (in pixels) for each object found. For example, if an image contains a dog, cat and person, the Detect operation will list those objects together with their coordinates in the image. You can use this functionality to process the relationships between the objects in an image. It also lets you determine whether there are multiple instances of the same tag in an image.

The Detect API applies tags based on the objects or living things identified in the image. There is currently no formal relationship between the tagging taxonomy and the object detection taxonomy. At a conceptual level, the Detect API only finds objects and living things, while the Tag API can also include contextual terms like " indoor " , which can ' t be localized with bounding boxes.