Reference:
https://docs.microsoft.com/en-us/azure/machine-learning/concept-designer#deploy

Explanation:

According to the Microsoft Azure AI Fundamentals (AI-900) official study guide and Microsoft Learn module "Identify features of Natural Language Processing (NLP) workloads and services," the Azure Cognitive Service for Language - Question Answering capability is designed to allow applications to respond to user questions using information from a prebuilt or custom knowledge base. It relies on Natural Language Processing (NLP) to match user queries to the most relevant answers but does not directly execute queries against databases or infer user intent.
* "You can use Language Service's question answering to query an Azure SQL database." # NOThe Question Answering feature does not connect directly to or query structured databases such as Azure SQL. Instead, it retrieves answers from unstructured or semi-structured content (FAQs, manuals, documents). Querying SQL databases would require traditional database access, not a cognitive service.
* "You should use Language Service's question answering when you want a knowledge base to provide the same answer to different users who submit similar questions." # YESThis statement is correct and aligns exactly with Microsoft's official documentation. Question Answering enables organizations to create a knowledge base that can automatically answer repeated or similar customer queries using natural language understanding. For instance, two users asking "How do I reset my password?" and
"Can you help me change my password?" would receive the same predefined response.
* "Language Service's question answering can determine the intent of a user utterance." # NODetermining user intent is handled by Language Understanding (LUIS) or Conversational Language Understanding, not by Question Answering. While both belong to the Language Service, Question Answering focuses on retrieving relevant answers, whereas LUIS focuses on intent detection and entity extraction.

Section: Describe features of computer vision workloads on Azure
Explanation:
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.
Reference:
https://docs.microsoft.com/en-us/azure/cognitive-services/computer-vision/concept-object-detection