In Azure Cognitive Search, a knowledge store is an optional capability that allows you to persist the enriched data from a skillset (enrichment pipeline) into an Azure Storage account. This is often used when you want to further analyze or visualize enriched content, e.g., sentiment analysis results from social media posts.
When defining a knowledge store, you need:
storageConnectionString
This is required so the enrichment pipeline can connect to your Azure Storage account.
Without it, the knowledge store cannot persist any data.
storageContainer
This specifies the container in Blob Storage where enriched documents or projections will be stored.
This allows you to persist the original documents and enriched outputs such as sentiment analysis scores.
Other options (not correct in this case):
tables # This is a projection type used within a knowledge store to structure output in Table Storage, but it's not required in the definition itself.
files # Another projection type for storing enriched documents as files in Blob Storage, but again, not a required field in the definition itself.
objects # A projection type used for representing enriched documents as JSON objects in Blob Storage.
Thus, while tables, files, and objects are used inside projections within a knowledge store, the definition itself always requires a storage connection string and storage container.
A). storageContainer
C). storageConnectionString
Microsoft References
Knowledge store in Azure Cognitive Search
How to define a knowledge store

We need to design a Conversational Language Understanding (CLU) model for smart home commands.
The sample utterances:
"Set all the lights to on." # Intent = change setting, Entity = device (lights)
"Turn off the lights in the living room." # Intent = change setting, Entities = device (lights) + location (living room)
"What is the current thermostat temperature?" # Intent = query setting, Entity = device (thermostat)
"Lower the temperature of the thermostat by five degrees." # Intent = change setting, Entity = device (thermostat) Breakdown:
Intents needed:
Change setting intent (D): Covers actions like turning devices on/off, lowering temperature.
Query setting intent (E): Covers questions about current state, like "What is the thermostat temperature?" Entities needed:
Device entity (F): Identifies devices such as lights and thermostat .
Why not the others:
A). a location intent # Location (like "living room") should be modeled as an entity, not an intent.
B). a change setting entity # Change setting is an action (intent), not an entity.
C). a device intent # Devices are entities, not intents.
The answer:
D). a change setting intent
E). a query setting intent
F). a device entity
Microsoft References
Intents and entities in CLU
CLU model design best practices

Explanation:

To create a single multi-service Cognitive Services resource (now Azure AI Services) that provides one key
/endpoint for multiple services , consolidates billing, and allows adding services like Text Analytics (sentiment analysis) and Computer Vision (OCR) from the same resource, you must:
Use the Azure Resource Manager (ARM) REST API with PUT to create or update the account:
PUT /subscriptions/{subId}/resourceGroups/{rg}/providers/Microsoft.CognitiveServices/accounts/{name}?
api-version=2017-04-18
Set " kind " : " CognitiveServices " to create the multi-service account (not a single-service kind like ComputerVision or TextAnalytics).
This satisfies the requirements: single key/endpoint, consolidated billing, and future Computer Vision use.
Microsoft Azure AI Solution References
ARM REST for Cognitive Services accounts (create/update via PUT , multi-service " kind " : " CognitiveServices " ).
https://learn.microsoft.com/azure/ai-services/management/resource-manager-create-account Azure AI Services multi-service resource (single endpoint/key across services).
https://learn.microsoft.com/azure/ai-services/multi-service-resource

Explanation:

1. api-nam.cognitive.microsofttranslator.com
2. translate
https://learn.microsoft.com/en-us/azure/cognitive-services/Translator/reference/v3-0-reference#base-urls Requests to Translator are, in most cases, handled by the datacenter that is closest to where the request originated. If there ' s a datacenter failure when using the global endpoint, the request may be routed outside of the geography.
To force the request to be handled within a specific geography, use the desired geographical endpoint. All requests are processed among the datacenters within the geography.
- United States
api-nam.cognitive.microsofttranslator.com
https://learn.microsoft.com/en-us/azure/cognitive-services/translator/reference/rest-api-guide
- translate
Translate specified source language text into the target language text.

You are developing an app that uses the Azure AI Speech service , and you must ensure the app can authenticate using a Microsoft Entra ID (Azure AD) token , rather than the standard key-based authentication.
According to the official Microsoft documentation :
"To authenticate with a Microsoft Entra token, the Speech resource must have a custom subdomain and use a private endpoint. The Speech service uses custom subdomains with private endpoints only."
- Microsoft Learn: Azure AI Speech service - Role-based access control
Therefore, two prerequisites must be configured for Entra ID token-based authentication:
1. Create (Certify) a Custom Subdomain (Option D)
When you create an Azure AI Speech resource, you can specify a custom subdomain name (e.g., contoso.
cognitiveservices.azure.com).
The custom subdomain ensures that each Speech endpoint has a unique URL.
Microsoft Entra token authentication depends on this subdomain for token validation.
Without a custom subdomain, Entra ID tokens cannot be used for authentication.
Hence, this is required.
2. Create a Private Endpoint (Option B)
For Microsoft Entra ID authentication, the Speech resource must be secured within a private endpoint .
Private endpoints provide a secure, private connection from your virtual network to the Azure AI Speech resource.
The Speech service only supports Entra ID token authentication when the resource is configured with a private endpoint.
Hence, this is required.
Why Not the Other Options:
A). Create a Conditional Access - Conditional Access policies restrict user access but do not configure token authentication for services.
C). Request an X.509 certificate - Certificates are not used for Speech service authentication.
E). Enable a virtual network service endpoint - The Speech service uses private endpoints , not service endpoints, for Entra ID token authentication.