Multi-language OmniScripts use Salesforce translation infrastructure and custom labels. In normal Salesforce runtime usage, the language shown to the user is driven by the user’s Salesforce language setting, not simply by the browser language or by a random session variable. The default OmniScript language is only the fallback/base design language; it does not decide which translated bundle is displayed for each user when translations exist. Option A is wrong because a global Session Variable is not the standard translation selector. Option B is also wrong in this context because OmniScript translations are tied to Salesforce language and Translation Workbench/custom-label behavior. Therefore, the user’s Salesforce language setting is the correct controlling source for displayed translations.

================