Northern Trail Outfitters (NTO) wants to connect their B2C Commerce data with Data Cloud and bring two years of transactional history into Data…

The B2C Commerce Starter Bundles are the recommended method for establishing the initial connection, data streams, and mappings for B2C Commerce data. However, these bundles are designed for ongoing data synchronization and typically ingest a limited historical window (e.g., the last 90 days of order data). To fulfill the requirement of bringing in two years of transactional history, a supplemental, one-time custom data extract from B2C Commerce is required. This historical data can then be ingested into Data Cloud, often via Amazon S3.

A. B2C Commerce Starter Bundles alone are insufficient as they do not typically ingest two years of historical transactional data by default.

B. This is too generic. It describes an entity but not the specific connector or process needed for a large historical backfill.

C. This is incorrect as it focuses only on the product entity, ignoring the required transactional (Sales Order) history.

1. Salesforce Help. (2024). Data Cloud Connectors: B2C Commerce Connector. "To load historical data, use a different ingestion method, such as the Amazon S3 connector." Section: Considerations for the B2C Commerce Connector.

2. Salesforce Partner Community. (2023). Data Cloud Implementation Guide. "For historical data loads exceeding the standard connector lookback window, a one-time batch ingestion via a custom process (e.g., S3 Ingestion) is the standard approach." Section 4.2: Historical Data Ingestion Patterns.