Q: 1
Universal Containers is expanding into French- and German-speaking regions. The team wants to
ensure that product names and descriptions appear in the correct language when customers browse
the catalog via APIs. Which configuration is required to support this multilingual API response?
Options
Discussion
Gotta go with C here. Enabling data translation is the key step or else those APIs won’t actually serve up localized product data. I think B sounds close but misses that config piece.
C imo. You have to actually enable data translation first so the Product List and Product Details APIs return the right language data for each locale. Just providing translations (B) isn't enough by itself, at least from what I've seen in real configs. Agree?
Its C for this. Without enabling data translation, those APIs won’t switch product names/descriptions by locale. Providing translations alone (like B) won’t trigger the language-aware API behavior in Salesforce. Pretty sure that’s what the config needs here but open if someone has seen a different approach.
Nah, B is tempting but misses that you have to enable data translation first. C.
Probably C here. If data translation isn't enabled, the Product List and Product Details APIs won't deliver the right language content regardless of what translations exist. I think B gets close but skips that activation step. Open to better logic though.
B . Trap is thinking you must enable something extra, but just providing data translations through the Product2 APIs could be enough for some setups, right?
B for me. Had something like this in a mock and just providing translations via the standard Product2 APIs was enough, didn’t have to specifically enable data translation. Could be missing some niche config though.
C vs B here. Similar question showed up in a practice exam, and official docs back the need to enable data translation settings for locale support. I'd trust the official guide over anything else.
C, not B. Only way APIs give back localized product info is if data translation's actually enabled in config.
Not totally sold on C if we're talking pure API config. If the Translation Workbench were set up to update metadata real-time for Product2, then A could be right, but pretty sure in Salesforce it's data translation specifically for these APIs. Anyone disagree?
Be respectful. No spam.
