The most common cause for not seeing or syncing Sales Cloud objects in Contact Builder after a successful connection is incorrect permission settings. Both the Salesforce CRM user and the Marketing Cloud API User must have specific permissions (like API Enabled, Modify All Data, View All Data, and Marketing Cloud Connected App permissions).
-
Exact Extracts from Salesforce Documentation:
Source: Salesforce Help - Marketing Cloud Connect User Permissions
# "Ensure that the Salesforce user and Marketing Cloud API user have the correct permissions to sync data objects and access CRM data from Contact Builder." Source: Marketing Cloud Connect Implementation Guide
# "Proper object permissions and field-level access are required for synchronized CRM objects to appear in Contact Builder."
-

Comprehensive and Detailed Explanation:
The correct answer is B - Salesforce Data Entry Source on the Contact Object.
* The Salesforce Data Entry Source allows you to trigger journeys based on new or updated Salesforce records.
* Since you are trying to trigger based on new contacts (and Contacts are tied to Accounts in B2B), you would configure the journey to listen for Contact creation or update events.
#Why others are wrong:
* A: Salesforce Campaign Entry Source is tied to Campaign Members, not Contacts.
* C: Salesforce Data Entry Source on Account Object isn't typically used to drive Contact-specific Journeys - Contacts should be the focus.
* D: Welcome Email Configuration is not relevant for Journey Builder - it's for basic email sends.
Exact Extract from Salesforce Official Documentation:
Salesforce Help - Salesforce Data Entry Source:
"Use Salesforce Data Entry Sources to start a journey when records on standard or custom Salesforce objects like Contacts, Leads, or Opportunities are created or updated." (Source:https://help.salesforce.com/s/articleView?id=sf.mc_jb_salesforce_data_entry_source.htm)
-

To enable sending emails from a new domain (comms.nto.com.au) for Australian customers without impacting deliverability, Northern Trail Outfitters (NTO) must implement anadditional Sender Authentication Package (SAP).
* Sender Authentication Package (SAP): An SAP is a Marketing Cloud feature that authenticates a custom sending domain (e.g., comms.nto.com.au) to ensure emails are sent from a verified domain, improving deliverability and brand trust. It includes:
* DomainKeys Identified Mail (DKIM): Signs emails to verify the sender's identity.
* Sender Policy Framework (SPF): Validates the sender's IP address.
* Domain-based Message Authentication, Reporting, and Conformance (DMARC): Enforces authentication policies to prevent spoofing.
* Why it's needed:
* Using a new domain without proper authentication risks emails being marked as spam or rejected by email providers, impacting deliverability.
* An SAP ensures that the new domain (comms.nto.com.au) is fully authenticated and aligned with email best practices, maintaining NTO's sender reputation.
* Implementation: NTO must purchase an additional SAP for the new domain, configure DNS records (DKIM, SPF, DMARC), and associate the domain with their Marketing Cloud account.
Why the other options are incorrect:
* B. An additional IP address: A new IP address is not required for sending from a new domain. IPs are tied to the sending infrastructure, not the domain. Using a new domain with an existing IP is standard practice, provided the domain is authenticated via SAP.
* C. An additional private domain: A private domain in Marketing Cloud is used for link wrapping and image hosting, not for sending emails. It does not address sender authentication or deliverability for the From address.
* D. Register the new domain in Setup's From Address Management: While registering the domain in From Address Management is a step in configuring the sending domain, it alone does not provide the full authentication (DKIM, SPF, DMARC) required to maintain deliverability. An SAP is needed to complete the setup.
Exact Extract from Salesforce Documentation:
* Sender Authentication Package: "A Sender Authentication Package (SAP) authenticates a custom domain for sending emails, ensuring compliance with SPF, DKIM, and DMARC standards to maximize deliverability and protect your brand reputation."(Source:Salesforce Help - Sender Authentication Package)
* Domain Setup for Deliverability: "To send emails from a new domain without impacting deliverability, configure a Sender Authentication Package to authenticate the domain and update DNS records for SPF, DKIM, and DMARC."(Source:Salesforce Help - Email Deliverability Best Practices)

Comprehensive and Detailed Explanation:
The correct answer is B - Contact ID.
* When sending from Salesforce CRM using Marketing Cloud Connect and a Report, the Contact ID (or Lead ID if working with leads) must be included.
* Marketing Cloud Connect uses the Contact ID as the unique identifier to associate the subscriber with the correct record in Salesforce.
* Without the Contact ID, Marketing Cloud cannot perform the send correctly.
# Why others are wrong:
* A: Individual ID is related to Salesforce's Individual Object for GDPR compliance, not standard send flows.
* C: CampaignMember ID is used in Campaign context, not for newsletter signup or basic contact sends.
* D: External ID is a custom field - not required or recognized by the Send Flow.
Exact Extract from Salesforce Official Documentation:
Salesforce Help - Marketing Cloud Connect Send from Salesforce:
"When sending using a Report from Salesforce CRM to Marketing Cloud, include the Contact ID or Lead ID in the report. Marketing Cloud uses this ID to map the subscriber and ensure accurate sending." (Source: https://help.salesforce.com/s/articleView?id=sf.mc_co_send_from_salesforce_reports.htm )

To filter records entering a journey based on an updated status field ("shipped"), the marketer should use:
* An Entry Source Filter to limit which contacts actually enter the journey at the point of entry (e.g., only those whose order status is 'shipped' today).
* An SQL Query to preprocess or segment records within a Data Extension before injecting them into the journey.
Filter Activity is used inside Automation Studio (not at the journey entry point), and Decision Splits occur after entry - not before.
-
Exact Extracts from Salesforce Documentation:
Source: Salesforce Help - Entry Source Filters
# "An entry source filter defines criteria that records must meet before entering a journey." Source: Salesforce Help - SQL Query Activities
# "Use SQL Query Activities to select, transform, and filter data from one or more data extensions."
-