To inject contacts into journey B based on email engagement in journey A, Northern Trail Outfitters should use an engagement split followed by an update contact activity to a Boolean field on an engagement data extension in journey A, and query the engagement data extension for journey B injection. An engagement split is an activity that allows marketers to route contacts based on their engagement with email messages, such as opens or clicks. An update contact activity is an activity that allows marketers to update contact attributes or data extension fields based on journey data. A query activity is an activity that allows marketers to retrieve data from data extensions using SQL queries. Reference: https://help.salesforce.com/s/articleView?id=sf.mc_jb_engagement_split.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.mc_jb_update_contact_activity.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.mc_as_query_activity.htm&type=5

Three tasks that a consultant would suggest for using Journey Builder instead of Automation Studio are:
Building simple segmented campaigns without SQL queries. Journey Builder allows marketers to create simple segmented campaigns using filters and rules without writing SQL queries. Automation Studio requires SQL queries for creating complex segments using data extensions.
Designing decision logic via an intuitive user interface. Journey Builder allows marketers to design decision logic using activities such as decision splits, engagement splits, or random splits via an intuitive user interface. Automation Studio requires scripting or coding for creating decision logic using activities such as script activities or verification activities.
Setting behavior-based goals. Journey Builder allows marketers to set behavior-based goals using criteria such as email opens, clicks, conversions, or custom events. Automation Studio does not have a feature for setting behavior-based goals.
Processing zipped encrypted files containing subscriber data is a task that a consultant would suggest for using Automation Studio instead of Journey Builder, as Automation Studio has activities such as file transfer activities or import file activities that can handle zipped encrypted files. Creating customer segments from multiple data extensions is a task that a consultant would suggest for using Automation Studio instead of Journey Builder, as Automation Studio has activities such as query activities or filter activities that can create customer segments from multiple data extensions. Reference: https://help.salesforce.com/s/articleView?id=sf.mc_jb_journey_builder.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.mc_as_automation_studio.htm&type=5

To automate exclusion of identified email addresses from all future sends that use specific sender profiles, Northern Trail Outfitters should use an auto-suppression list. An auto-suppression list is a tool that allows marketers to exclude subscribers from email sends based on their email address and sender profile. The email addresses can be added to the auto-suppression list using a SQL query or an import activity. Reference: https://help.salesforce.com/s/articleView?id=sf.mc_es_create_an_auto_suppression_list.htm&type=5

To send an email with 10 personalized fields from multiple data extensions to an audience of over one million subscribers, Northern Trail Outfitters should create and send to a sendable data extension containing those needed fields using a query activity. A query activity can join and filter data from multiple data extensions and populate a sendable data extension with the required fields for personalization. This will improve the email send performance and avoid timeouts or errors. Reference: https://help.salesforce.com/s/articleView?id=sf.mc_as_query_activity.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.mc_es_send_email_using_a_data_extension.htm&type=5

To diagnose the issue of failed Salesforce Triggered Sends, the consultant should ensure the System User is assigned the Standard User Profile. The System User is a user account that Marketing Cloud Connect uses to communicate with Sales Cloud. The System User needs to have the Standard User Profile or a custom profile with similar permissions to enable Salesforce Triggered Sends. Reference: https://help.salesforce.com/s/articleView?id=sf.mc_co_troubleshoot_marketing_cloud_connect_configuration_issues.htm&type=5