Explanation
A Sender Authentication Package (SAP) is a set of features that authenticate an email sender's identity and reputation, such as a private domain, a dedicated IP address, a link customization, and a reply mail management. By having an additional SAP for the new domain comms.nto.com.au, NTO can send emails from their new domain without impacting deliverability. An additional IP address is not required if they already have one for their SAP. An additional private domain is not enough to authenticate their sender identity and reputation. Registering the new domain in From Address Management is not necessary if they have an SAP for the new domain. References:
https://help.salesforce.com/articleView?id=sf.mc_es_sender_authentication_package.htm&type=5
https://help.salesforce.com/articleView?id=sf.mc_es_from_address_management.htm&type=5

Explanation
This setting allows the consultant to verify the sender's identity and configure the incoming email settings.
Reference: https://help.salesforce.com/articleView?id=mc_es_sap_overview.htm&type=5 To redirect its emails to Marketing Cloud servers for processing, Northern Trail Outfitters should use a Sender Authentication Package. A Sender Authentication Package is a feature that allows marketers to authenticate their email sends with their own domain and branding, instead of using Marketing Cloud's default domain and branding. This will improve email deliverability and reputation, as well as provide more control over email settings and preferences. References:
https://help.salesforce.com/s/articleView?id=sf.mc_es_sender_authentication_package.htm&type=5

Explanation
A decision split activity is a journey builder activity that allows branching the journey based on attribute values or engagement behavior of each contact. Contact data refers to data that is stored outside the journey, such as in data extensions or data views. Journey data refers to data that is captured at the moment of entry into the journey, such as from a Salesforce entry event. By using both contact and journey data in a decision split activity, NTO can compare attribute values from different sources using an attribute-to-attribute comparison. For example, they can compare the promo code from the transaction data extension (contact data) with the promo code from the entry event (journey data) and divert contacts who have redeemed the promo code before reminder emails are sent. References:
https://help.salesforce.com/articleView?id=sf.mc_jb_decision_split.htm&type=5
https://help.salesforce.com/articleView?id=sf.mc_jb_attribute_to_attribute_comparison.htm&type=5

Explanation
Performing large-scale segmentation in Automation Studio before admitting contacts into Journey Builder can help reduce the amount of contacts admitted into the journey, thereby increasing the performance of the journey.
Creating prefiltered, sendable copies of data extensions for each journey instead of using the same entry source can also help optimize journey performance as it reduces the number of contacts that have to be processed for each journey. This can help with performance as the data extension is already filtered and therefore the journey has to do less work in terms of filtering the participants. For more information, see the Salesforce Certified Marketing Cloud Consultant Exam Study Guide[1] or the Salesforce documentation on Journey Performance[2].
[1] https://trailhead.salesforce.com/content/learn/certifications/marketing-cloud-consultant/marketing-cloud-cons

Explanation
To format the JSON payload from their commerce platform within the email, Northern Trail Outfitters should use the BuildRowSetFromJSON() AMPscript function. The BuildRowSetFromJSON() AMPscript function is a function that allows marketers to parse a JSON string and return a rowset object that can be used to display data within an email message. The BuildRowSetFromJSON() AMPscript function can handle nested JSON objects and arrays. References:
https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-programmatic-content.meta/mc-programmatic-co