1. A support ticketing system wants to automatically detect the language of an incoming ticket and route it to the correct queue, while also translating a short preview snippet into English for triage staff. Which approach BEST fits both needs?
- A. Azure Translator (or an LLM-powered translation flow) to detect language and produce the English preview snippet✓ Correct
- B. Sentiment detection to infer both the language and a translated preview simultaneously
- C. Text-to-speech to read the ticket aloud in the original language for triage staff
- D. Entity extraction limited to product names, with no language handling
Explanation
Translation services such as Azure Translator (or an LLM-powered flow) typically support language detection alongside translation, making them well suited to both routing by detected language and producing an English preview. Option B misapplies sentiment detection, which analyzes tone, not language identity or translation. Option C produces audio, not a text preview, and does not address routing. Option D extracts only product entities and provides no language detection or translation capability.