Northern Trail Outfitters asks its consultant to extract the runner profiles and activity logs from its Track My Run mobile app and load them into…

The best practice is to use the most efficient ingestion method for each phase of the data loading process. Bulk ingestion is designed for loading large, historical datasets, making it the ideal choice for the initial 90-day data load. It processes records asynchronously in batches, which is optimal for high volumes. For ongoing, near real-time updates from a mobile app, streaming ingestion is the correct method. It is designed for low-latency ingestion of events as they occur, ensuring that new and updated runner profiles and activities are available in Data Cloud promptly.

1. Salesforce Help

Data Cloud

"Data Ingestion": "Use the Bulk API to upload large-scale data that doesn’t need to be available in Data Cloud right away. Use the Streaming API to upload data from websites and mobile devices in near real time." This directly supports using Bulk for historical and Streaming for ongoing mobile app data.

2. Salesforce Developers

Data Cloud Developer Guide

"Data Ingestion APIs": In the section "When to Use the Bulk API vs. the Streaming API

" the documentation states: "Use the Bulk API for batch imports

such as daily or weekly imports of large datasets... Use the Streaming API for real-time or near-real-time use cases

such as when you want to capture user activity on your website or mobile app." This clearly outlines the distinct use cases that align with the correct answer.

3. Salesforce Trailhead

"Data Cloud for Marketing

" Unit: "Get Started with Data Cloud": This module explains that different ingestion methods are suited for different scenarios. It describes batch (Bulk API) for historical data and streaming for real-time event data

reinforcing the pattern of using bulk for the initial load and streaming for continuous updates.