The requirement is to process images of forms with Azure Form Recognizer (now part of Azure AI Document Intelligence) while ensuring that the image files are not stored in the cloud.
When sending images directly to the Form Recognizer REST API endpoint, you have two options:
Send the file as binary data in the request body (for local file upload).
Send a URL reference (if the file is stored in Azure Blob Storage or another public location).
Since the requirement explicitly states that the image files must not be stored in the cloud, you cannot send a URL. Instead, you must send the raw binary content of the file directly in the request body.
Option A - raw image binary
Correct. This allows you to directly send the local image file to the API without uploading/storing it in the cloud.
Option B - form URL encoded
Incorrect. Form Recognizer does not accept URL-encoded form data.
Option C - JSON
Incorrect. JSON is only used when providing the API with the URL of a cloud-stored document, not when sending the actual file.
The Answer: A. raw image binary
Microsoft References
Form Recognizer REST API - Analyze a document
Quickstart: Extract layout and text - Document Intelligence
" If your document is available locally, pass the file as binary data in the request body. "

Explanation:
Comprehensive Detailed Explanation
You're adding multiple images for each person into a PersonGroup using the Face API SDK.
File.OpenRead(imagePath) returns a Stream, so the using declaration must declare Stream t = File.OpenRead (imagePath) .
To upload an image from a stream to a person in a person group, call
faceClient.PersonGroupPerson.AddFaceFromStreamAsync(personGroupId, personId, t); Putting it together:
Parallel.For( 0 , PersonCount, async i = >
{
Guid personId = persons[i].PersonId;
string personImageDir = $ " /path/to/person/ {i} /images " ;
foreach ( string imagePath in Directory.GetFiles(personImageDir, " *.jpg " ))
{
using (Stream t = File.OpenRead(imagePath))
{
await faceClient.PersonGroupPerson.AddFaceFromStreamAsync(
personGroupId, personId, t);
}
}
});
This loops the images for each person, opens each as a stream, and adds the face to the specified person in the person group.
References
Microsoft Docs - Face API: Add a face to a person ( AddFaceFromStreamAsync , AddFaceFromUrlAsync ) in PersonGroupPerson operations.
https://learn.microsoft.com/azure/ai-services/face/ (see SDK/PersonGroupPerson methods) NET File.OpenRead returns Stream .
https://learn.microsoft.com/dotnet/api/system.io.file.openread

Explanation:
Comprehensive Detailed Explanation
You have 1,000 untagged images and want to retrain the Custom Vision model as quickly as possible. The key is to avoid manually tagging every image, since that is time-consuming.
Step 1: Upload all the images
First, bulk upload all the untagged images into the Custom Vision project.
At this stage, they will have no labels.
Step 2: Get suggested tags
The Custom Vision portal offers an auto-suggest feature that uses the current trained model to predict tags for new, untagged images.
This dramatically reduces manual tagging effort.
Step 3: Review the suggestions and confirm the tags
Auto-suggestions are not always 100% accurate, so you must confirm or correct them.
Once confirmed, the dataset is labeled properly and ready for retraining.
Why not the other options?
Upload the images by category / group into category folders: This is only helpful if the images already have known categories, but here they arrive untagged.
Tag the images manually: This would take much longer and contradicts the requirement to minimize time.
Correct Sequence
Upload all the images.
Get suggested tags.
Review the suggestions and confirm the tags.
Microsoft References
Custom Vision - Tag images
Custom Vision - Suggested tags with predictions

Explanation:

You are securing an Azure Cognitive Search resource with two specific requirements:
Prevent access to Search1 from the internet
The correct way is to use a private endpoint.
A private endpoint connects the Cognitive Search resource directly into your virtual network (VNet), blocking public internet access.
Configuring an IP firewall can restrict access to specific IP ranges but does not fully prevent internet access.
Azure roles and authentication do not address network-level restrictions.
Limit the access of each app to specific queries
This is done via Azure role-based access control (RBAC).
You can assign different Azure roles or API keys with query rights to control what each app can do.
Key authentication alone only provides coarse-grained access (admin/query keys) but does not allow fine- grained per-app restrictions.
RBAC ensures principle of least privilege is enforced.
The Answer:
Prevent access from internet # Create a private endpoint
Limit access to queries # Use Azure roles
Microsoft References
Secure access to Azure Cognitive Search using private endpoints
Role-based access control in Azure Cognitive Search