Explanation:

* First blank: speech_recognition_language
* Second blank: add_target_language
speech_translation_config = speechsdk.translation.SpeechTranslationConfig( subscription=os.environ.get('SPEECH_KEY'), region=os.environ.get('SPEECH_REGION') )
# Source (recognition) language: English (US)
speech_translation_config.speech_recognition_language = "en-US"
# Target translation language: Italian
speech_translation_config.add_target_language("it")
audio_config = speechsdk.audio.AudioConfig(use_default_microphone=True) recognizer = speechsdk.translation.TranslationRecognizer( translation_config=speech_translation_config, audio_config=audio_config ) Comprehensive Detailed Explanation along with All References available from Microsoft Azure AI Solution at the end of the explanation To translate speech, configure a SpeechTranslationConfig with (1) the recognition language of the input audio and (2) one or more target languages for translation. In Python, you set the input language with the speech_recognition_language property (e.g., "en-US"), and you add a target with add_target_language ("<locale>") (e.g., "it" for Italian). This exactly matches the SDK guidance and examples for speech translation. Microsoft Learn
* speech_recognition_language specifies the locale used by the recognizer to understand the spoken input.
* add_target_language("it") adds Italian as a translation output language.
Microsoft References
* How to translate speech with the Speech SDK (Python examples show translation_config.
speech_recognition_language = from_language and translation_config.add_target_language(...)).
Microsoft Learn
* SpeechTranslationConfig (Python) reference - add_target_language(language: str). Microsoft Learn
* Recognize speech (property usage for speech_recognition_language). Microsoft Learn
* Language support for Speech service (locales and codes for recognition/translation)

Explanation:

Scenario Recap:
* You have an Azure OpenAI resource with multiple deployed models.
* You are using the Chat playground to build a chatbot.
* Requirements:
* Generate text in concise, formal business language.
* Reduce cost of running the model.
* Maintain the size of the chatbot history window (i.e., context length).
Step 1: Ensuring concise, formal business languageIn the Chat playground setup panel, you can configure System message instructions.
Example:
You are an AI assistant that responds in concise formal business language.
This controls tone, style, and response behavior.
So one setting is: System message / Instructions.
Step 2: Reducing cost while maintaining chat history windowCosts in Azure OpenAI are tied to:
* The model used (larger models = more expensive).
* The context window size (token usage).
Since we must maintain the size of the chat history window, we cannot shrink context length.
Therefore, to reduce cost: select a smaller/cheaper deployed model (e.g., GPT-3.5 instead of GPT-4).
So the second setting is: Deployment (model selection).
* Configure Deployment # choose a smaller/cheaper model.
* Configure System message instructions # specify "concise formal business language."
# Final Answer:
Microsoft References:
* Azure OpenAI Chat playground
* Best practices for reducing token cost

Explanation:


Comprehensive Detailed ExplanationThe requirement is to build an Adaptive Card for the chatbot that supports multilingual product display and meets accessibility requirements.
* Product Name Display
* The product JSON stores localized names like "name": { "en": "...", "es": "...", "pt": "..." }.
* To dynamically render based on the current language, you must use name[language].
* This ensures the product name shown in the card adapts automatically to the user's preferred language.
* Stock Level Warning
* Business rules require warnings when stock is low or out of stock.
* This means you display the stock warning only when stockLevel is not 'OK'.
* Therefore, the correct condition is:"$when": "${stockLevel != 'OK'}"
* Image Alt Text for Accessibility
* Accessibility requirements specify that all images must have alt text in English, Spanish, and Portuguese.
* In the product JSON, "alttext" is also localized:
* "altText": { "en": "Bicycle", "es": "Bicicleta", "pt": "Bicicleta" }
* To render the correct localized alt text dynamically, use image.altText[language].
Correct Selections:
* First blank: name[language]
* Second blank: "$when": "${stockLevel != 'OK'}"
* Third blank: image.altText[language]
* Adaptive Cards Templating
* Adaptive Card $when property
* Multilingual data in Azure Cognitive Search and Adaptive Cards
Microsoft References

Batch anomaly detection is a type of anomaly detection that scans the entire dataset at once for outliers and unusual patterns. Batch anomaly detection is suitable for offline analysis of historical data, such as sensor data from the previous 24 hours. Batch anomaly detection can use various techniques, such as statistical methods, machine learning methods, or hybrid methods, to identify anomalies in the data123.

Explanation:
Semi-structured data
Let's break down the options:
* Graph data
* Used in graph databases (e.g., Azure Cosmos DB Gremlin API, Neo4j).
* Represents nodes and edges with relationships.
* JSON is not graph data.
* Relational data
* Stored in relational databases with tables, rows, and columns.
* JSON does not follow a fixed schema with rows/columns.
* Semi-structured data
* Correct.
* JSON, XML, and Avro are common examples of semi-structured data.
* They don't require a rigid schema like relational data, but still have organizational elements (tags, key-value pairs).
* JSON is widely used in NoSQL/document databases like Azure Cosmos DB.
* Unstructured data
* Examples: images, videos, free text, audio.
* JSON does not fit here because it has a defined structure with keys and values.
The answer: Semi-structured data
* Structured, semi-structured, and unstructured data
* What is semi-structured data?
* Azure Cosmos DB and JSON data model
Microsoft References