Northern Trail Outfitters an online clothing store has recently enabled the Loyalty Program. Which objects count toward data storage capacity?

All standard and custom object records in Salesforce consume data storage. However, in the context of a Salesforce Loyalty Management implementation, certain objects are foundational and contribute most significantly to data volume. This option correctly identifies the key high-volume objects:

Person Account: Represents the individual loyalty program member.

Orders: A primary source of member activity that leads to point accrual.

Loyalty Program Members: Represents the member's enrollment in a specific loyalty program.

Transaction Journals: The highest-volume object, as a new record is created for every single point transaction (e.g., accrual, redemption, adjustment, expiration).

This combination represents the core data flow and the largest contributors to data storage in a typical retail loyalty program.

B. Person Account, Loyalty Ledgers, Cases, Loyalty Program Currency: This option is less accurate because Cases are not a core Loyalty Management object, and Loyalty Program Currency is low-volume setup data, not transactional data.

C. Person Account, Email Messages, Transaction Journals, Loyalty Member Currency: This option is incorrect as Email Messages, while consuming storage, are ancillary to the core loyalty transaction processing and data model.

D. Person Account, Loyalty Member Tier, Orders, Loyalty Program Members: This option is plausible but omits Transaction Journals, which is typically the single largest contributor to data storage growth in a Loyalty Management implementation over time.

1. Salesforce Help, Monitor Data and Storage Resources: This document confirms that records for standard objects like Accounts and custom objects consume data storage. It states, "Data storage is used by creating records, such as Account, Contact, and Lead records." This principle applies to all objects listed in the options.

Reference: Salesforce Help, Article ID 000384919, "Monitor Data and Storage Resources".

2. Salesforce Help, Loyalty Management Data Model: The official data model illustrates the central role of Loyalty Program Member, Transaction Journal, and their relationship with source objects like Order. Transaction Journal is shown as the detailed log of all point changes.

Reference: Salesforce Help, "Loyalty Management Data Model", ERD Diagram.

3. Salesforce Help, Transaction Journal: The documentation explicitly describes this object's function: "Stores a log of all loyalty point transactions of a member in a loyalty program... A transaction journal is created for every credit and debit of points." This highlights its high-volume nature.

Reference: Salesforce Help, "Loyalty Management Objects", Section: Transaction Journal.

4. Salesforce Help, Set Up Your Org for Loyalty Management: The setup guide specifies enabling Person Accounts and Orders as prerequisites, underscoring their foundational role in the implementation for B2C scenarios like Northern Trail Outfitters.

Reference: Salesforce Help, "Set Up Your Org for Loyalty Management", Section: Enable Person Accounts, Enable Orders.