Explanation:

To let an Azure AI Agent access publicly available, recent web content, you add the Bing grounding tool. In the SDK, you first define a ToolConnectionList with the Bing connection ID (here, "bingConnectionId"), then construct a BingGroundingToolDefinition(connectionList) so the agent can call Bing Search with recency filters (e.g., last 90 days) when answering questions.
When creating the agent, tool definitions are passed via the tools: parameter of CreateAgentAsync(...) as a List<ToolDefinition>. The toolResources parameter is used when you must also supply resource descriptors (for example, an Azure AI Search index configuration), which is not needed here because the Bing grounding tool already references the connection through the ToolConnectionList.
Therefore:
* Use BingGroundingToolDefinition to ground the agent on current public web data.
* Provide that tool in tools: new List<ToolDefinition> { grounding } when calling CreateAgentAsync(...).
Microsoft Azure AI References (titles only)
* Azure AI Agent Service - Bing web grounding tool (tool definitions and connections)
* Azure AI Agent Service SDK - Agent creation (CreateAgentAsync parameters: tools vs toolResources)
* Azure AI Agent Service - Tool connections and ToolConnectionList usage

Explanation:

To deploy an agent and connect it to an existing Azure AI Search index (which already contains vectors), you first need the connection ID for the search resource. Using the Azure AI Projects/Agents client, you obtain that connection ID from your project's connections. Next, you configure the Azure AI Search tool by specifying the index_connection_id, index_name, and (optionally) the query type (simple, semantic, vector, or hybrid), which supports vectorized indexes. After the tool is configured, you create the agent with the tool enabled (passing tools and tool_resources). Finally, you validate the integration by starting a thread and asking questions grounded in the Azure AI Search index. This sequence matches the Microsoft guidance and minimizes effort because it reuses the existing index and only adds a configured tool to a new agent.
Microsoft References
* Use an existing index with the Azure AI Search tool (sequence: create client # configure tool # create agent with tool # ask questions). Microsoft Learn
* Azure AI Search tool overview (add the tool to an agent; supported search types including vector and hybrid). Microsoft Learn
* AzureAISearchTool and AzureAISearchQueryType (parameters, including connection ID and query types: simple, semantic, vector, hybrid).
* Vector and hybrid search in Azure AI Search (background for vector-enabled indexes and hybrid queries).

Explanation:

https://learn.microsoft.com/en-us/azure/cognitive-services/speech-service/custom-speech-overview#how-does- it-work With Custom Speech, you can upload your own data, test and train a custom model, compare accuracy between models, and deploy a model to a custom endpoint.
- Create a project and choose a model. Use a Speech resource that you create in the Azure portal. If you will train a custom model with audio data, choose a Speech resource region with dedicated hardware for training audio data.
- Upload test data. Upload test data to evaluate the speech to text offering for your applications, tools, and products.
- Train a model. Provide written transcripts and related text, along with the corresponding audio data. Testing a model before and after training is optional but recommended.
- Deploy a model. Once you're satisfied with the test results, deploy the model to a custom endpoint. With the exception of batch transcription, you must deploy a custom endpoint to use a Custom Speech model.

Explanation:
Project type: Object detection
* Domain: General (compact)
The scenario requires building a Custom Vision model for a factory with intermittent internet connectivity.
The solution must:
* Detect defects in packaging
* Locate the defects (provide bounding box information)
* Ensure each package contains four products
* Support offline use due to intermittent connectivity
Step 1 - Determine Project Type
* Image Classification: Assigns a label to an image, but cannot locate where objects/defects are in the image.
* Object Detection: Identifies what objects are present and their location (via bounding boxes).
* Since the requirement is to identify location of defects and count products, the correct choice is Object detection.
Step 2 - Determine Domain
* General domain: Standard general-purpose domain, optimized for cloud inference.
* General (compact) domain: A lightweight version designed for exporting models to run offline on edge devices (iOS, Android, ONNX, etc.). Perfect for scenarios with intermittent internet connectivity.
* Food domain: Specialized for food image classification, not defect detection in packaging.
* Logo domain: Specialized for logo recognition, irrelevant here.
Since the requirement includes offline capability, the correct domain is General (compact).
The answer:
* Project type: Object detection
* Domain: General (compact)
* Custom Vision project types: Classification vs Object detection
* Domains in Custom Vision (General, General compact, Food, Logo, etc.)
* Exporting compact models for offline use
Microsoft References

Explanation:

Azure AI Document Intelligence (formerly Form Recognizer) is provisioned as a Cognitive Services account with the kind set to FormRecognizer. In an ARM template, Document Intelligence is created under the resource provider Microsoft.CognitiveServices with the resource type accounts. Therefore:
* type must be "Microsoft.CognitiveServices/accounts"
* kind must be "FormRecognizer"
This aligns with Microsoft's ARM schema for Cognitive Services accounts and the documented way to deploy Document Intelligence.
Key references from Microsoft documentation:
* Azure Resource Manager template reference for Cognitive Services accounts - shows type: Microsoft.
CognitiveServices/accounts and supported kind values including FormRecognizer.https://learn.
microsoft.com/azure/templates/microsoft.cognitiveservices/accounts
* Azure AI Document Intelligence (Form Recognizer) resource creation guidance - indicates the service is deployed as a Cognitive Services account with kind FormRecognizer.https://learn.microsoft.com
/azure/ai-services/document-intelligence/overview
* Create Document Intelligence resources (portal/ARM/Bicep) - reiterates Cognitive Services account with FormRecognizer kind.https://learn.microsoft.com/azure/ai-services/document-intelligence/create- resources