You are deploying a Language Understanding (LUIS) container. When running LUIS in Docker, the model must first be exported from the Language Understanding portal, and then provided to the container at runtime.

Step-by-step reasoning:

From the Language Understanding portal, export the solution as a package file.

The trained LUIS model must be exported from the portal into a .json package file.

This is required because the container cannot access the hosted service directly.

From the host computer, move the package file to the Docker input directory.

Containers expect the model to be available locally.

The package file is placed into the input directory that the container maps for models.

From the host computer, run the container and specify the input directory.

When starting the container, you specify --volume < local_input > :/input so the container has access to the package file.

This makes the exported model available inside the container for processing.

Why not the other options?

Retain the model in the portal is not sufficient; the container cannot pull directly from the cloud.

Build the container and specify the output directory is not required; the container image is already available from MCR and is not custom-built for this step.

Correct Answer Order:

Export the solution as a package file.

Move the package file to the Docker input directory.

Run the container and specify the input directory.

Microsoft References

Run LUIS containers

Use containers with Azure AI services

 Service endpoint → Computer Vision analyze images

 Property → imageType

The task:

" You have a library with thousands of images. You need to tag the images as photographs, drawings, or clipart. "

Which service endpoint?

Computer Vision analyze images → Provides a broad analysis including categories, tags, descriptions, and image type (photo, drawing, clipart). ✅

Computer Vision object detection → Identifies objects (people, cars, animals), not image type.

Custom Vision image classification / object detection → Requires custom training, not needed since the built-in Computer Vision service already supports this.

Correct: Computer Vision analyze images

Which property?

categories → Provides predefined categories (e.g., outdoor, indoor, people), not specifically drawing/clipart/photo.

description → Generates captions in natural language, not classification into photo/drawing/clipart.

imageType → Identifies if an image is a photograph, line drawing, or clipart. ✅

metadata → Provides size, format, dimensions.

objects → Lists detected objects, not image type.

Correct: imageType

Correct Answer:

Service endpoint → Computer Vision analyze images

Property → imageType

Microsoft References

Computer Vision Analyze API

ImageType property in Computer Vision

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

Detect the incoming language:

Service: Speech to Text

Reasoning: The Speech to Text service can transcribe spoken language into text and includes language identification capabilities, allowing the system to detect whether the caller is speaking French or English.

Respond in the callers ' own language:

Service: Text to Speech

Reasoning: The Text to Speech service can convert text responses into spoken language in the detected language (French or English), enabling the system to respond to callers in their own language.

Ordered Mapping:

Detect the incoming language: Speech to Text

Respond in the callers ' own language: Text to Speech

Box 1: Text Analytics

The Language Detection feature of the Azure Text Analytics REST API evaluates text input for each document and returns language identifiers with a score that indicates the strength of the analysis.

Box 2: Translator

Translator is a cloud-based neural machine translation service that is part of the Azure Cognitive Services family of REST APIs. Translator can be used with any operating system and powers many Microsoft products and services used by thousands of businesses worldwide to perform language translation and other language-related operations.

A view is a virtual table based on the result set of a query.

Views allow you to encapsulate complex queries (including joins and calculated columns) and make them reusable by other users.

Index improves performance but does not store or rerun queries.

Scalar function returns a single value, not a tabular result.

Table stores raw data, not queries.

Box 1: Classification

Box 2: Multiclass

A multiclass classification project is for classifying images into a set of tags, or target labels. An image can be assigned to one tag only.

Box 3: General

General: Optimized for a broad range of image classification tasks. If none of the other specific domains are appropriate, or if you ' re unsure of which domain to choose, select one of the General domains.