Microsoft Updated AI-102 Exam Questions and Answers by ioan

You created five bots with Microsoft Bot Framework Composer, but want to make them appear as one unified bot for users, with dynamic routing depending on user input.

This is exactly the Bot Framework Orchestrator scenario. Orchestrator is the recognizer that allows you to dispatch incoming utterances to the correct skill (bot) or dialog.

Step 1 – Install Orchestrator package

To use Orchestrator inside Bot Framework Composer, you first install the Orchestrator package.

This provides the functionality for language understanding and routing.

Correct answer: F.

Step 2 – Change Recognizer/Dispatch type

By default, a bot project might use LUIS recognizer or Regex recognizer.

To use Orchestrator, you need to change the recognizer type to Orchestrator in Composer.

Correct answer: B.

Step 3 – Create an Orchestrator model

Orchestrator requires a trained model that maps utterances to intents or routes them to the correct skill/bot.

You must create an Orchestrator model for dispatch.

Correct answer: A.

Other Options (Incorrect):

C. Create a Composer extension → Not required for orchestrating multiple bots.

D. Enable WebSockets → Useful for streaming scenarios, not for bot orchestration.

E. Create a custom recognizer JSON file → Applies to building custom recognizers, not needed with Orchestrator.

You are asked to build an app that translates speech from English into French, German, and Spanish using Azure AI Speech Translation.

Step 1 – Define target languages

The SpeechTranslationConfig object requires language codes (not full names like " French " , " German " , " Spanish " ).

Valid language codes:

French → " fr "

German → " de "

Spanish → " es "

Therefore, the correct syntax for the output languages is:

var languages = new List < string > { " fr " , " de " , " es " };

Step 2 – Choose the recognizer type

IntentRecognizer : Used for intent recognition with LUIS, not translation.

SpeakerRecognizer : Used for speaker identification/verification, not translation.

SpeechSynthesizer : Used for text-to-speech, not translation.

TranslationRecognizer : Used specifically for speech-to-speech or speech-to-text translation.

Therefore, the correct recognizer is TranslationRecognizer.

Correct Answer:

Output Languages: { " fr " , " de " , " es " }

Recognizer: TranslationRecognizer

Microsoft References

Speech Translation with Azure AI Speech

TranslationRecognizer Class (C# API)

Supported language codes

Azure AI Document Intelligence (Standard S0) enforces input constraints: images must be between 50×50 and 10,000×10,000 pixels and typical file size limits apply (images/PDFs well below hundreds of MB; an 800-MB PDF is far beyond supported sizes).

File1.pdf (800 MB) – exceeds supported size limits → cannot be analyzed.

File2.jpg (25×25 px) – below the 50×50 px minimum → cannot be analyzed.

File3.tiff (5,000×5,000 px; 5 MB) – within pixel and size limits → can be analyzed.

References

Document Intelligence service limits (file size/page and image dimension constraints).

https://learn.microsoft.com/azure/ai-services/document-intelligence/concept-limits

Document Intelligence supported file types.

https://learn.microsoft.com/azure/ai-services/document-intelligence/overview#supported-formats

Comprehensive Detailed Explanation

You’re creating a resource that will handle sentiment analysis (Language) and OCR (Vision) with a single key and endpoint. That is a Cognitive Services multi-service (Azure AI services) account.

When creating any Azure resource via ARM (HTTP/REST), the URL must be scoped to a subscription, not a tenant, and use the correct resource provider.

Scope segment: Use

https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{rg}/providers/...

Therefore, choose subscriptions/8d3591aa-96b8-4737-ad09-00f9b1ed35ad (not the tenant scope).

Resource provider: Multi-service cognitive account is under Microsoft.CognitiveServices.

The full path to create would be like:

/providers/Microsoft.CognitiveServices/accounts/{accountName}?api-version=2021-10-01

This creates a single Cognitive Services (Azure AI services) resource that provides one endpoint and one key across multiple services (e.g., Language for sentiment analysis and Vision for OCR).

Microsoft Azure AI Solution References

Azure Resource Manager: Create Cognitive Services account (Microsoft.CognitiveServices/accounts) using REST and API version 2021-10-01.

Azure AI services (Cognitive Services) multi-service resource overview—single key/endpoint across services.