Microsoft AI-102 - Designing and Implementing a Microsoft Azure AI Solution

Box 1: " categories " : [ " Locations " , " Persons " , " Organizations " ],

Locations, Persons, Organizations are in the outputs.

Scenario: Contoso plans to develop a searchable knowledgebase of all the intellectual property

Note: The categories parameter is an array of categories that should be extracted. Possible category types: " Person " , " Location " , " Organization " , " Quantity " , " Datetime " , " URL " , " Email " . If no category is provided, all types are returned.

Box 2: { " name " : " entities " }

The include wikis, so should include entities in the outputs.

Note: entities is an array of complex types that contains rich information about the entities extracted from text, with the following fields

name (the actual entity name. This represents a " normalized " form)

wikipediaId

wikipediaLanguage

wikipediaUrl (a link to Wikipedia page for the entity)

etc.

The wiki contains text in English, French and Portuguese.

Scenario: All planned projects must support English, French, and Portuguese.

The Document Extraction skill extracts content from a file within the enrichment pipeline. This allows you to take advantage of the document extraction step that normally happens before the skillset execution with files that may be generated by other skills.

Note: The Translator Text API will be used to determine the from language. The Language detection skill is not required.

C: Analyze Receipt - Get Analyze Receipt Result.

Query the status and retrieve the result of an Analyze Receipt operation.

Request URL: https://{endpoint}/formrecognizer/v2.0-preview/prebuilt/receipt/analyzeResults/{resultId}

E: POST {Endpoint}/vision/v3.2/read/analyze

Use this interface to get the result of a Read operation, employing the state-of-the-art Optical Character Recognition (OCR) algorithms optimized for text-heavy documents.

Scenario: Contoso plans to develop a document processing workflow to extract information automatically from PDFs and images of financial documents

The document processing solution must be able to process standardized financial documents that have the following characteristics:

- Contain fewer than 20 pages.

- Be formatted as PDF or JPEG files.

- Have a distinct standard for each office.

*The document processing solution must be able to extract tables and text from the financial documents.

The document processing solution must be able to extract information from receipt images.

In the Azure portal, the Keys and Endpoint blade for a Cognitive Service resource provides:

API keys (for authentication)

Endpoint URL (the REST interface base URL)

Identity blade relates to managed identities.

Properties blade shows metadata (resource ID, location, subscription ID).

Networking blade controls network access and firewall rules.

Correct Answer: B. Keys and Endpoint

Step 1: Create a new project and load sample documents

Create a new project. Projects store your configurations and settings.

Step 2: Label the sample documents

When you create or open a project, the main tag editor window opens.

Step 3: Train a custom model.

Finally, train a custom model.

The requirements state:

All AI solution responses must have a confidence score ≥ 70%.

If the response confidence score is < 70%, the response must be improved by human input.

Members of the Consultant-Bookkeeper group must be able to process financial documents, which includes performing manual review when the AI confidence is below threshold.

Looking at the provided JSON:

" fields " : {

" ReceiptType " : {

" type " : " string " ,

" valueString " : " Itemized " ,

" confidence " : 0.672

},

" MerchantName " : {

" type " : " string " ,

" valueString " : " Tailwind " ,

" confidence " : 0.913

}

}

ReceiptType.confidence = 0.672 → this is below 0.7.

MerchantName.confidence = 0.913 → this is above 0.7.

Therefore, the correct condition for triggering manual review is:

documentResults.fields. < field > .confidence < 0.7

Now, evaluating the options:

A. documentResults.docType == " prebuilt:receipt "

Always true for receipts, does not check confidence. Not correct.

B. documentResults.fields.*.confidence < 0.7

This is the correct general expression: trigger manual review whenever any field confidence is below 0.7.

C. documentResults.fields.ReceiptType.confidence > 0.7

This would bypass manual review when ReceiptType has high confidence. The requirement is to trigger review when confidence < 0.7, so this is the opposite.

D. documentResults.fields.MerchantName.confidence < 0.7

This only checks one field (MerchantName). In the JSON, MerchantName has confidence 0.913 ( > 0.7), so this condition would not trigger, but ReceiptType clearly needs review. Too narrow.

Correct Answer: B. documentResults.fields.*.confidence < 0.7

Microsoft References

Azure AI Document Intelligence – Confidence scores

Human-in-the-loop for Document Intelligence

You are calling the Face API to find similar faces from an existing list called employeefaces.

Key facts from the scenario:

The list contains 60,000 images.

In Face API:

faceListId → limited to 1,000 faces.

largeFaceListId → designed for very large lists, up to 1,000,000 faces.

Since employeefaces has 60,000 images, you must use LargeFaceListId, not faceListId.

Parameters in the Request Body

" faceId " : " 18c51a87-3a69-47a8-aedc-a54745f708a1 "

This is the face to search for.

" largeFaceListId " : " employeefaces "

Must use LargeFaceListId because the list has 60,000 images.

" maxNumOfCandidatesReturned " : 1

Limits the number of matches returned.

" mode " : " matchFace "

Two options exist:

" matchFace " → returns the most similar individual faces.

" matchPerson " → groups faces by person.

Since the requirement is find similar faces, use " matchFace " .

Completed Answer

{

" faceId " : " 18c51a87-3a69-47a8-aedc-a54745f708a1 " ,

" largeFaceListId " : " employeefaces " ,

" maxNumOfCandidatesReturned " : 1 ,

" mode " : " matchFace "

}

Correct Values to Drag and Drop

LargeFaceListId → " employeefaces "

matchFace → " mode "

Final Answer:

First blank: LargeFaceListId

Second blank: matchFace

Microsoft References

Face API – Find Similar

Face API – Large Face List operations

Comprehensive Detailed Explanation

To move a Question Answering project to a different Azure region, you migrate the project data and then re-deploy it in the target region:

Export the existing project (source region).

In Language Studio (Question Answering), you first export the project. This produces a package (JSON/ZIP) containing your knowledge bases, sources, synonyms, and settings. Exporting is the supported way to move a project between resources/regions.

Import the project into the new Language service instance (target region).

In the target region’s Language service instance, use Language Studio to import the previously exported file. This recreates the project (KBs and configuration) under the new resource.

Train and publish from the new instance.

After import, you must train (build) and then publish the project so that an endpoint is created under the new regional resource. Clients can then point to the new endpoint and key.

Actions like “enable custom text classification” or “regenerate the keys” are not required for moving a Question Answering project, and training/publishing from the original instance won’t deploy to the target region.

Microsoft Azure AI Solution References

Export and import Question Answering projects in Language Studio (move between resources/regions):

Microsoft Learn – Export and import projects (Question Answering) .

https://learn.microsoft.com/azure/ai-services/language-service/question-answering/how-to/export-import-project

Train and publish a Question Answering project:

Microsoft Learn – Create, train, and publish projects (Question Answering) .

https://learn.microsoft.com/azure/ai-services/language-service/question-answering/how-to/create-test-deploy

Language service overview and regional deployment concepts:

Microsoft Learn – What is Azure AI Language?

https://learn.microsoft.com/azure/ai-services/language-service/overview

Azure AI Document Intelligence offers pre-built models for common document types like invoices, which extract key fields (e.g., vendor, amount, date) with minimal setup. For custom forms like internal authorization requests, the pre-built general document model handles layout and text extraction, but to minimize development effort, use the pre-built invoice model where applicable and a custom model only if pre-built options fall short. However, the standard recommendation prioritizes pre-built for both to avoid training.