Helping Hand Questions for AI-102

Comprehensive Detailed Explanation

You are tasked with building a solution using Custom Vision to detect faults in factory components. Custom Vision follows a defined workflow:

Create a project

Before anything else, you must create a Custom Vision project in the Azure AI portal.

This project specifies the type of model you are building: classification (classifying entire images) or object detection (locating items within images).

Since the question is about detecting faults in specific components (a business-specific scenario), it aligns with classification unless explicitly stated otherwise.

Upload and tag images

You must provide training data.

Upload a set of images showing both faulty and non-faulty components.

Tag each image correctly so that the model can learn from labeled examples.

Train the classifier model

Once images are tagged, you run training on the dataset to generate the classifier model.

The model can then be published and used for inference via API calls.

Why not the other options?

Initialize the training dataset: This is not a direct step in Custom Vision; instead, uploading and tagging images inherently prepares the training dataset.

Train the object detection model: Object detection is used if you need bounding boxes around items within an image. Since the question is about recognizing faults in a component (faulty vs non-faulty), a classifier model is appropriate.

Correct Sequence:

Create a project

Upload and tag images

Train the classifier model

Microsoft References

Quickstart: Build an image classification project with the Custom Vision portal

Custom Vision overview

Train and test a Custom Vision model

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