* When deploying Cognitive Services containers (such as Anomaly Detector), the container requires a billing parameter in the docker run command.
* This parameter points to the Azure resource key and endpoint for billing.
* Fluentd is for logging.
* Http Proxy is optional for outbound connectivity.
* Mounts are used for local storage but are not mandatory for billing.
The answer: B
Reference: Run Cognitive Services containers - Billing settings

Explanation:

There are two main types of data workloads: Batch and Streaming.
* Batch Workload
* Processes data in large groups (batches) at scheduled intervals.
* Common when real-time is not required.
* Examples: daily sales reports, hourly data refreshes, periodic ETL (Extract, Transform, Load).
* Streaming Workload
* Processes data in real time or near real time as it arrives.
* Used for scenarios where immediate insights or actions are required.
* Examples: fraud detection, IoT sensor monitoring, live purchase tracking.
* "Data for a product catalog will be loaded every 12 hours to a data warehouse."
* This is scheduled, not continuous. # Batch
* "Thousands of data sets per second for online purchases will be loaded into a data warehouse in real time."
* This requires real-time processing. # Streaming
* "Updates to inventory data will be loaded to a data warehouse every 1 million transactions."
* Data is grouped and loaded after reaching a threshold (1 million). # Batch Correct Matches:
* Product catalog (12 hours) # Batch
* Online purchases (real time) # Streaming
* Inventory data (1 million transactions) # Batch
* Batch processing vs. Stream processing in Azure
* Azure Stream Analytics overview
* Data processing approaches: Batch vs Real-time

* Requirement: The chatbot must classify user input into categories.
* The categories must be dynamic and defined at inference time.
* Custom text classification (Language service) requires training beforehand and fixed labels.
* OpenAI text classification can dynamically handle categories via prompting at inference.
* Therefore, Azure OpenAI text classification is correct.
Microsoft Reference:
Classification with Azure OpenAI

Explanation:

Box 1: mcr.microsoft.com/azure-cognitive-services/textanalytics/sentiment To run the Sentiment Analysis v3 container, execute the following docker run command.
docker run --rm -it -p 5000:5000 --memory 8g --cpus 1 \
mcr.microsoft.com/azure-cognitive-services/textanalytics/sentiment \
Eula=accept \
Billing={ENDPOINT_URI} \
ApiKey={API_KEY} is the endpoint for accessing the Text Analytics API. https://<your-custom-subdomain>.
cognitiveservices.azure.com
Box 2: https://contoso.cognitiveservices.azure.com
{ENDPOINT_URI} is the endpoint for accessing the Text Analytics API: https://<your-custom-subdomain>.
cognitiveservices.a The endpoint for accessing the Text Analytics API. zure.com Reference:
https://docs.microsoft.com/en-us/azure/cognitive-services/text-analytics/how-tos/text-analytics-how-to-install- containers?tabs=sentiment

Explanation:

Looking at the exhibit:
* The GetWeather dialog is set up with a trigger phrase:
* "what is the weather like in {city=Seattle}"
* Here, city is an entity (ex: Seattle, New York, London, etc.).
* Since "New York" matches the city entity, the bot will correctly identify New York as a city entity.
* It will not confuse it with a state entity, nor default to Seattle, because entity recognition extracts the correct city name dynamically.
Correct choice: Identify New York as a city entity
* In Bot Framework Composer, the trigger type determines how the dialog is activated.
* Since GetWeather is linked to the intent "GetWeather" from the Language Understanding model (LUIS
/CLU), the trigger is Language Understanding Intent recognized.
* This means whenever the user utterance maps to the GetWeather intent, the dialog starts.
Correct choice: Language Understanding Intent recognized
* Identify New York as a city entity
* Language Understanding Intent recognized
* Bot Framework Composer - Triggers
* Entities in Conversational Language Understanding