Language Understanding: An AI service that allows users to interact with your applications, bots, and IoT devices by using natural language.
QnA Maker is a cloud-based Natural Language Processing (NLP) service that allows you to create a natural conversational layer over your data. It is used to find the most appropriate answer for any input from your custom knowledge base (KB) of information.
Text Analytics: Mine insights in unstructured text using natural language processing (NLP)-no machine learning expertise required. Gain a deeper understanding of customer opinions with sentiment analysis. The Language Detection feature of the Azure Text Analytics REST API evaluates text input Reference:
https://azure.microsoft.com/en-us/services/cognitive-services/text-analytics/
https://docs.microsoft.com/en-us/azure/cognitive-services/qnamaker/overview/overview

Comprehensive Detailed Explanation
You are asked to construct a URI for the Microsoft Translator API call that:
Translates webpage content into Greek (el).
Returns a transliteration in the Roman alphabet (Latin script).
The base URI given is:
https: //api.cognitive.microsofttranslator.com/translate?api-version=3.0 Now, let's evaluate the required query parameters.
1. to=el
This specifies the target language for translation.
Since the requirement is to translate into Greek, we must include:
to =el
Correct
2. textType=html
The source content is from a webpage.
Translator API requires textType=html for web page or HTML-formatted content.
If omitted, the default is plain text.
Correct
3. toScript=Latn
By default, Greek text is written in its native Greek script.
To provide a transliteration in the Roman alphabet, we must set toScript=Latn .
Latn = Latin script.
Correct
Incorrect Options
A). toScript=Cyrl
Cyrl = Cyrillic script. Not required here.
B). from=el
This would mean the source language is Greek.
In the requirement, the target is Greek, so this is incorrect.
E). textType=plain
Incorrect, since we are translating HTML webpage content, not plain text.
The answer: C. textType=html, D. to=el, F. toScript=Latn
Microsoft References
Translator Text API v3.0 Reference - Translate
Language and Script Parameters (to, from, toScript)

Explanation:

Comprehensive Detailed Explanation
A custom neural voice (professional voice) project in Azure AI Speech requires that you follow Responsible AI and consent steps before any model training. The correct workflow in Speech Studio / Azure AI Foundry is:
Create a custom voice project - This is the container that will hold the voice talent consent, your training datasets, models, and deployments. Each project is scoped to a locale and other attributes. Microsoft Learn Collect and upload consent - Microsoft requires explicit authorization from the voice talent. In practice, you add the voice talent consent to the project. The platform requires the verbal consent recording (WAV); many guidance and exam items also include the signed consent document (PDF) as part of consent capture to meet Responsible AI expectations. The consent step is performed before uploading training data.
Upload the voice talent's verbal consent as a WAV file - The consent audio verifies that the person who granted consent is the same as the speaker in your training data. The documentation shows consent is a recorded statement uploaded to the project. Microsoft Learn Analyze the quality of the audio data and fix issues - After data upload, Speech Studio runs validation and provides a per-utterance analysis (format checks, sampling rate, script match, pronunciation/noise scoring).
You must resolve issues and run Analyze data before the dataset can be used for training. Microsoft Learn Train the model using a neural training method - Start model training from the project and choose Neural as the training type for custom neural voice. Microsoft Learn Why not "upload speech samples as WMA/MP3 files"?
For the standard, recommended Individual utterances + matching transcript data type used to fine-tune a professional neural voice, the audio files must be WAV/RIFF PCM; the docs explicitly reference ".wav" throughout data checks and corrections. WMA isn't supported, and MP3 isn't accepted for this core data type.
(Long audio / audio-only workflows can accept MP3 for preprocessing, but the canonical training dataset for custom neural voice is WAV.) Microsoft Azure AI References Create a project for professional voice (Speech Studio/Azure AI Foundry): Project contains consent, datasets, models, endpoints. Microsoft Learn Add voice talent consent to the professional voice project: Upload the recorded consent statement for the voice talent. Microsoft Learn Professional voice fine-tuning data - required formats: Individual utterances + transcript require WAV/RIFF PCM; guidance on sample rate and transcript format. Microsoft Learn Add a professional voice training dataset & resolve data issues: Data validation, pronunciation/noise checks, and the Analyze data step prior to training. Microsoft Le arn Train your professional voice model: Start training and select Neural method. Microsoft Learn

According to the Microsoft documentation, Computer Vision is a cloud-based service that provides developers with access to advanced algorithms for processing images and returning information. By uploading an image or specifying an image URL, Computer Vision algorithms can analyze visual content in different ways based on inputs and user choices.
According to the Microsoft documentation, image type detection is one of the features of Computer Vision that can categorize an image as either a photograph or a drawing. You can use the image type detection feature by calling the Analyze Image API with the visualFeatures parameter set to ImageType. The API will return a JSON response with an imageType field that indicates whether the image is a photo or a clipart.
According to the Microsoft documentation, image descriptions is another feature of Computer Vision that can generate a caption for an image. You can use the image descriptions feature by calling the Analyze Image API with the visualFeatures parameter set to Description. The API will return a JSON response with a description field that contains a list of captions for the image, each with a confidence score.
Therefore, by using these two features of Computer Vision, you can achieve your app requirements with minimal development effort. You don't need to use any other services, such as object detection, content tags, or Custom Vision, which are designed for different purposes.