A customer wants to implement an AEM solution to serve localized content to several regional websites. Which AEM capability should the Architect recommend?

Question

Options

• AUse translation connector and Multi Site Manager
• BUse il8N API and Multi Site Manager
• CUse translation connector and il8N API
• DUse translation connector and translation workflows

• A
  9% (4)
• B
  5% (2)
• C
  84% (36)
• D
  2% (1)

Explanation

Option C is correct because serving localized content in AEM requires two complementary layers: the Translation Connector (Translation Integration Framework) bridges AEM with external translation providers to translate actual page content, while the i18n API handles internationalization at the component/UI level by resolving dictionary-based strings (labels, button text, static UI copy). Together they cover the full localization stack - content and interface.

Why the distractors fail:

• A (Translation Connector + MSM): MSM manages site structure via blueprints and live copies - it's for multi-site governance, not localization. It doesn't translate anything.
• B (i18n API + MSM): Same MSM problem, plus this pairing has no mechanism to actually translate authored content - i18n API only handles pre-defined dictionary strings.
• D (Translation Connector + Translation Workflows): Translation Workflows are orchestrated by the Translation Connector - they're not a separate, additive capability. Choosing both is redundant and still misses the i18n API.

Memory tip: Think of it as two tiers - "Content goes to Connector, Code goes to i18n." The Translation Connector ships your authored content out to a translator; the i18n API localizes what developers hard-coded into components. You need both tiers for a complete solution.

No community discussion yet for this question.