A marketer at Northern Trail Outfitters wants to personalize an email by displaying a customer's...

Handlebars is the appropriate method because the scenario specifically requires conditional logic against values supplied by the Data Graph. Marketing Cloud Next's Handlebars implementation provides comparison and control helpers such as if, else if, equals, compare, and, or, and iif. These functions allow message content to change according to profile values such as Loyalty Tier or Points balance.

Marketing Cloud Next exposes the profile Data Graph through Handlebars, allowing deeply related profile attributes to be referenced and evaluated programmatically. Salesforce's developer documentation describes $dataGraph as the profile data graph loaded with marketing content and shows how nested attributes can be traversed.

Simple merge fields are appropriate when the requirement is only to print an attribute. They don't by themselves provide the richer branching logic requested here. Dynamic content variations can also implement marketer-configured targeting, but when the explicit requirement is conditional expression logic against Data Graph values, Handlebars is the more direct technical answer.

The uploaded source keys B.

Study Guide Reference: Campaign Design, Flow Orchestration and Content → Personalization → Handlebars Conditional Logic and Data Graph Data.

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