Migrate the legacy data leveraging an ETL tool to transform data types and load data into Salesforce.

Explanation:

While options B and C use similar tools, A is the most comprehensive and robust approach for complex data migrations. A staging database acts as an intermediary where data from the legacy system is first loaded, allowing for a thorough data cleansing and transformation process. This step is crucial for addressing data type mismatches, duplicates, and inconsistencies before the data is transformed and loaded into Salesforce using an ETL (Extract, Transform, Load) tool. This method ensures data integrity and quality, which are paramount in data migration projects.

Option A: This is a best practice. The staging database provides a dedicated space to validate and transform data, and the ETL tool provides the robust capabilities for the final transformation and loading into Salesforce. This two-step process separates concerns and makes troubleshooting easier.

Option B: Using a staging database is a good start, but using stored procedures for data transformation can be less flexible and harder to maintain than an ETL tool, especially for complex transformations.

Option C: Migrating directly from the legacy system to Salesforce using an ETL tool is a valid approach for simple migrations, but it can be problematic if the source data is complex, requires extensive cleansing, or if the source system is sensitive to direct API calls. It bypasses the crucial data analysis and cleansing phase that a staging database provides.

Option D: Exporting to CSV and using Data Loader is a manual and error-prone process. Data Loader is a simple tool and not designed for complex data transformations, especially for addressing data type mismatches on a large scale.

Create a custom big object in Salesforce which will be used to capture the Reward Program data for consumption by Einstein.

Explanation:

This question tests the understanding of handling high-volume data and integrating it with Einstein Analytics (now Tableau CRM).

✅ Why A is Correct: The scenario states the program will generate 100 million rows of data monthly (1.2 billion rows per year). This volume is far beyond the practical storage limits of standard or custom objects in Salesforce, which are subject to data storage limits and performance degradation at this scale. A Big Object is specifically designed for this use case: it stores billions of records, has a consistent, low-performance profile for large-scale queries, and can be accessed directly by Einstein Analytics for analysis. Storing the data in a Salesforce Big Object keeps it on the platform, making it natively accessible for Einstein Analytics.

❌ Why B is Incorrect: While Einstein Analytics can connect to external systems, this approach bypasses the Salesforce platform. This makes the data unavailable for other Salesforce features (like reporting, flows, or other automations that might be needed for the loyalty program itself) and adds complexity to the integration and security model. The requirement is to "store, collect, and use" the data, implying a need for a centralized, scalable repository on the Salesforce platform.

❌ Why C is Incorrect: There is no such thing as a "big object in Einstein Analytics." Einstein Analytics is an analytics service that consumes data from various sources (like Salesforce objects, Big Objects, or external systems); it is not a primary data storage system itself. The data must be stored elsewhere first.

❌ Why D is Incorrect: A standard custom object is not suitable for this volume of data. Loading 100 million records per month would quickly consume all data storage limits and lead to severe performance issues during data insertion, updates, and queries. Custom objects are not architected for this scale.

Reference: Salesforce Help & Training documentation on "Big Objects" and "Einstein Analytics Data Integration." The key concept is matching the data volume characteristic (massive, append-only) with the correct Salesforce architectural component (Big Objects).

Develop an ETL process that utilizers the merge API to merge the duplicate records

Explanation:

Merging a massive number of existing duplicates requires an automated, scalable approach. The Merge API, invoked via an ETL process, is the designed and supported method for this exact use case, ensuring data integrity is maintained during the operation.

✅ Correct Option A:
For a large-scale de-duplication project (500k duplicates), an automated process using the Data Loader and the Merge API is the only scalable and supported solution. An ETL tool (like Data Loader or an external tool) can orchestrate the logic to identify duplicates and then use the API to merge them correctly, preserving related data and audit history.

❌ Incorrect Option B:
Using a data warehouse as the system of truth does not solve the active duplication problem within Salesforce. It is a reporting strategy, not a data remediation one. The goal is to clean the operational Salesforce org, not to report on dirty data from another system.

❌ Incorrect Option C:
Extracting 2 million records to Excel is not feasible due to tool and row limits. Manually merging hundreds of thousands of records in Excel is impossible and error-prone. This is not a scalable or recommended approach for any data volume within Salesforce.

❌ Incorrect Option D:
Duplicate rules are a preventative measure. They stop new duplicates from being created but do nothing to identify or merge the existing 500,000 duplicates that are already in the system. They are part of the long-term solution but not the remediation tool.

🔗 Reference:
Salesforce Developer - Merge()

They do not include soft-deleted records

They avoid resource intensive joins

Their tables are kept in sync with their source tables when the source tables are modified

Explanation:

Skinny tables are a specialized type of custom table created by Salesforce support. They are used to improve the performance of frequently used reports and list views for very large objects. They work by combining key fields from a large object and its related parent objects into a single table, which speeds up queries.

Correct Options ✅:

A. They do not include soft-deleted records.
Skinny tables only contain active, non-archived data. This reduces the overall size of the table, making queries faster. Soft-deleted records are stored separately and are not included in the main table used for reporting.

B. They avoid resource intensive joins.
This is the primary reason for using skinny tables. By combining fields from a parent and child object into one table, they eliminate the need for a costly database join operation, which significantly speeds up report and query performance.

C. Their tables are kept in sync with their source tables when the source tables are modified.
Salesforce ensures that the skinny table is updated whenever a record in the source object is modified. This guarantees that reports and views using the skinny table are always showing the most current data.

Incorrect Options ❌:

D. They can contain fields from other objects.
This statement is not entirely correct. Skinny tables can only contain fields from a parent object and its child object, not from unrelated objects. They are not a general-purpose data consolidation tool.

E. They support up to a max of 100 of columns.
The column limit for skinny tables is 100, so this statement is factually correct. However, it is a technical detail, not a reason for them being "fast." The speed comes from the other three points.

Explanation:

UC needs a permanent retention strategy for Lead data beyond Salesforce's standard Recycle Bin (which holds deleted records for 15 days before permanent deletion). Once cleared from the Recycle Bin, data is irretrievable via standard Salesforce mechanisms without support intervention (which is limited and not scalable). Let’s analyze each option:

Option A: Use a Lead standard report and filter on the IsDeleted standard field.
The IsDeleted field can be used in SOQL reports to view soft-deleted records (those in the Recycle Bin), but it does not access data after permanent deletion from the Recycle Bin. Once permanently deleted, the records are no longer queryable, making this insufficient for long-term maintenance.

Option B: Use a Converted Lead report to display data on Leads that have been deleted.
Converted Lead reports focus on Leads that have been converted to Accounts/Opportunities/Contacts, not deleted ones. They do not provide visibility into deleted (let alone permanently deleted) Leads and are unrelated to the requirement.

Option C: Query Salesforce with the queryAll API method or using the ALL ROWS SOQL keywords.
queryAll() in the API or ALL ROWS in SOQL retrieves soft-deleted records (in the Recycle Bin) by including IsDeleted = true. However, this does not work for records permanently deleted from the Recycle Bin, as they are no longer stored in Salesforce's database. This approach fails for data cleared from the Recycle Bin.

Option D: Send data to a Data Warehouse and mark Leads as deleted in that system.
This is the best solution. Implement an integration (e.g., via ETL tools, Change Data Capture, or Outbound Messages) to replicate Lead data to an external Data Warehouse (e.g., Snowflake, AWS Redshift) in real-time or near-real-time. When a Lead is deleted in Salesforce, update the warehouse record with a "deleted" flag or soft-delete marker. This ensures permanent retention and accessibility even after Recycle Bin clearance, allowing UC to maintain historical data for compliance, reporting, or auditing without relying on Salesforce's limited recovery options.

Why Option D is Optimal:
Salesforce does not natively support indefinite retention post-Recycle Bin clearance, so external archiving to a Data Warehouse provides a scalable, auditable solution. It aligns with data governance best practices for large-scale orgs, enabling queries on historical Lead data indefinitely while marking deletions appropriately.

References:
Salesforce Documentation: Recycle Bin and Data Recovery
Salesforce Developer Guide: SOQL ALL ROWS Limitations (confirms no access post-permanent deletion)
Salesforce Architect Guide: Data Archiving and Retention