Marketing Cloud Connect ' s integration user requires both the API User checkbox enabled - which designates the account as a dedicated, non-interactive system/integration user rather than a standard human login, exempting it from normal password-expiration and login-count restrictions that would otherwise break the integration - and sufficiently elevated role permissions to perform the full range of actions Marketing Cloud Connect needs, which is why Salesforce ' s documented setup specifies both the Administrator and Marketing Cloud Administrator roles be applied to this user. Together, these two settings ensure the integration user can reliably authenticate on an ongoing, unattended basis while having the necessary permissions across both the Marketing Cloud and Salesforce sides of the connection to support synchronization, triggered sends, and Connect app functionality. Option B leaves the user without the roles needed to actually perform Connect ' s required operations, which would cause integration failures. Options C and D both leave the API User checkbox deselected, meaning the account behaves as a standard interactive user subject to expiration and session policies unsuited to an always-on system integration, and option D ' s Marketing Cloud Viewer role is read-only and insufficient for an integration user that must write and synchronize data. Reference: Marketing Cloud Connect API User Setup.

MuleSoft is Salesforce's integration platform that allows data transformation, API orchestration, and real-time integration between systems like a POS and Marketing Cloud.
It can modify and deliver data in the proper format required by the Triggered Send API.

BuildRowSetFromJSON() is the AMPscript function documented by Salesforce specifically for parsing a JSON payload - such as an order-details object from a commerce platform - directly into an AMPscript rowset that can be looped through with RowCount() and Field() to render order line items, quantities, and prices inline in email content. Because AMPscript executes natively at send time within Content Builder emails, this is the correct, in-content mechanism for the scenario described. Option D, the SSJS platform function ParseJSON, is a real Marketing Cloud function, but it operates in server-side JavaScript context (used in Script Activities and CloudPages), not natively inside AMPscript-based email content - it is the wrong layer for formatting JSON directly within an email ' s AMPscript. Option A, ' ParseJSON content block within Content Builder, ' is not a real Content Builder block type; ParseJSON is a function, not a drag-and- drop content block. Option B, TransformJSON(), does not exist as an AMPscript or SSJS function in Marketing Cloud ' s documented function library and should be treated as a fabricated distractor. Consultants should default to BuildRowSetFromJSON() whenever the requirement is parsing and displaying JSON- structured order or product data directly within AMPscript email content. Reference: AMPscript BuildRowSetFromJSON() Function.