Which Azure endpoint generates multilingual image tags with minimal effort?
You plan to build an app that will generate a list of tags for uploaded images. The app must meet the following requirements: • Generate tags in a user’s preferred language. • Support English, French, and Spanish. • Minimize development effort. You need to build a function that will generate the tags for the app. Which Azure service endpoint should you use?
Community Insight
This question tests selection of a prebuilt multimodal image service with request-time language localization; the trap is assuming Custom Vision or a separate translator is required.
Azure Vision in Foundry Tools Image Analysis is the correct endpoint for generating image tags because it provides prebuilt tagging with a language parameter. This lets the app return tags in English, French, or Spanish without training a custom model.
A common mistake is selecting Azure Custom Vision image classification, which requires labeled training images and custom model management and does not natively produce multilingual tags with minimal effort.
Community Discussion (1 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Azure Vision in Foundry Tools Image Analysis exposes prebuilt image analysis features, including tags, and the analyze call accepts a language parameter. That parameter is designed for localized output such as English, French, and Spanish, so the app can request the user’s preferred language directly. Because the model is pre-trained, no custom dataset, training run, or translation pipeline is required, which directly satisfies the minimize-development-effort requirement. The endpoint therefore returns a tag list in the requested language from the same service call.Why the Other Options Are Wrong
Azure Custom Vision image classification (B) can tag images only after you train and deploy a custom model, and it does not provide built-in multilingual tag generation, so it adds effort. Content Safety in Foundry Control Plane (C) is for moderating harmful content, not describing or tagging images. Custom Translator (D) translates text and would require a separate image-tagging source plus a translation workflow, increasing complexity. None of these options matches the combination of built-in image tags and language selection as directly as Image Analysis.Community Comment Notes
The sole visible comment, from Srikantha, also selects A and highlights “localized tag output” through a “target language query parameter” as the reason. That aligns with the service behavior: the language setting is applied at request time rather than requiring a separate model per language. The comment further emphasizes minimal development effort, which is the deciding requirement in this scenario. No conflicting community evidence is present.Official Reference
Exam Strategy
When a question asks for generated image metadata in multiple languages with minimal effort, look for a prebuilt vision service that accepts a language parameter rather than a custom model or separate translation step. Confirm that the option directly supports the requested languages and does not require training data.
Frequently Asked Questions
Why is Azure Custom Vision image classification wrong for multilingual tags?
It needs a trained custom model and does not expose built-in localized tag output, so it adds training and translation work rather than minimizing development effort.
Does Azure Vision Image Analysis support English, French, and Spanish tags?
Yes. Its language parameter lets the analyze request return tags in the user’s selected language without a separate translation service.
Related Analysis
Practice All AI-103 Questions
Access 88 questions with complete answers and detailed explanations.
View Full AI-103 Practice Test →