Free Salesforce-Loyalty-Management Practice Test Questions (2026)

Explanation

The Chief Marketing Officer's requirements involve two core loyalty concepts: a redeemable points system and a gamified tier structure. To award redeemable points, a points currency must be established. To gamify spending with exclusive benefits, a tier system based on cumulative value is necessary. Finally, promotions are a versatile tool used to create special offers, bonus point opportunities, and targeted campaigns that drive the desired spending behavior and engagement.

✅ Correct Options

B. Set up one qualifying currency
A qualifying currency is essential for tracking the points that determine a member's tier status. While the primary requirement is for redeemable points, a tier system must be built on a foundation of qualifying points earned from spending. This directly enables the "gamification" of customer spending.

C. Set up a tier system based on a cumulative spending value
This directly fulfills the requirement to "gamify customers that spend the most to receive exclusive benefits." A tier system automatically rewards members who reach specific cumulative spending thresholds with elevated status and exclusive perks, encouraging increased purchases.

E. Set up promotions
Promotions are a flexible tool used to create special offers, bonus point events, and targeted campaigns. They are crucial for actively driving the customer spending that fuels both the redeemable points system and the tier progression, making them a key element for a dynamic program.

❌ Incorrect Options

A. Set up one qualifying currency and a non-qualifying currency
This is incorrect and more complex than necessary. While a non-qualifying currency is used for redeemable points, the requirement is for points redeemable for products, which is typically handled by a separate, standard Loyalty Points currency, not a non-qualifying currency. The tier system requires only the qualifying currency.

D. Set up vouchers for specific products
Vouchers are a specific type of benefit, but they are not a core structural element of the program as described. The requirement is for a general points redemption system for "products in the store," which is achieved through the standard redemption process, not necessarily by pre-configuring specific product vouchers.

Summary
To meet the objectives, configure a qualifying currency for the tier system, the tier system itself for gamification, and promotions to drive engagement and spending.

📚 Reference
Salesforce Help - "Loyalty Program Types and Models" and "Set Up Loyalty Currencies"

Explanation:

✅ Correct Option: B
Using the out-of-the-box "Reset Qualifying Points" Data Processing Engine (DPE) is the most efficient method. Salesforce provides this pre-built engine specifically for resetting points at scale. Administrators can automate the execution by triggering it with a Schedule-Triggered Flow, ensuring resets happen efficiently without requiring manual work or heavy customization. This is Salesforce’s best practice for managing qualifying points in high-volume loyalty programs.

❌ Option A
Although reset periods are defined at the Tier Group level, they are not automatically processed by Salesforce every night. The definition simply indicates when a reset should occur. Without an actual process engine like DPE, the resets will not run at scale. Relying solely on this would not deliver the automation or efficiency needed for enterprise-level loyalty programs.

❌ Option C
Creating a custom Schedule-Triggered Flow that manually scans reset periods and resets points is unnecessary. While it could work, Salesforce already provides the "Reset Qualifying Points" DPE template for this exact purpose. Building a flow from scratch would add complexity, create maintenance overhead, and risk performance issues compared to using the standard solution provided by Salesforce.

❌ Option D
Developing an Apex time-trigger to handle reset operations is not efficient or scalable. Custom code increases the maintenance burden and could fail to handle large data volumes compared to the DPE, which is optimized for high-performance processing. Salesforce explicitly recommends using the DPE framework over custom Apex for loyalty program management tasks like resets.

📘 Summary:
The most effective and scalable way to reset qualifying points is by using Salesforce’s out-of-the-box "Reset Qualifying Points" Data Processing Engine. Combined with scheduling, it ensures resets run smoothly without custom development. Other options either misunderstand how reset periods work, duplicate functionality unnecessarily, or introduce inefficient custom code.

🔗 Reference: Salesforce Help – Manage Tier Calculation with Data Processing Engine

Explanation

Crafting a CDP segment for timely expiration alerts means pinpointing members whose standardized end-of-month dates match the current calendar month, then queuing a one-off send on the 1st. This setup leverages Loyalty Program Member data for precise filtering, with a static refresh to lock in the snapshot and date bounds to confine it to April through June. It's a smart, automated way to nurture renewals, blending CDP's power with Loyalty Management for proactive member care that feels personal and prevents churn.

Correct Option:

✅ B. In the Segmentation Rule, Use "LoyaltyProgramMember" as the Direct object, > Operator: "This Month" for the "Membership Expiry Date" attribute.
Picture this: On May 1st, the rule scans active members where expiry falls squarely in May—grabbing all with dates like May 31st. "This Month" dynamically aligns to the evaluation date, ensuring only true soon-to-expire folks make the cut. Paired with the direct object link, it pulls straight from Loyalty records for accuracy, making your notifications hit the bullseye every time without manual tweaks.

✅ D. In "Segment Property," set "Publish Schedule" to "24 hours" and the appropriate "Start Date" and "End Date"
Set the clock for a daily refresh at 24 hours to keep data fresh as of the 1st, then box in the action with a start on April 1st and end June 30th. This combo guarantees the segment builds once per needed day within the window, capturing updates like last-minute status changes. It's the guardrail for seasonal campaigns, ensuring emails fly only when they should, all while staying hands-off post-setup.

Incorrect Option:

❌ A. In "Segment Property", set "Publish Schedule" to "Don't Refresh".
Opting for no refresh freezes the segment at creation time, which might miss folks added or updated after—like a member renewing mid-month before the 1st. For expiration alerts needing current accuracy, this static lockout risks incomplete lists and missed opportunities. Better for unchanging groups, but here it skips the pulse-check that keeps notifications relevant and complete.

❌ C. In the Segmentation Rule, Use "LoyaltyProgramMember" as the Direct object, > Operator: "Next Number of days" = 30 for the "Membership Expiry Date" attribute.
A 30-day forward look shines for general reminders, but it blurs lines for end-of-month standardization—snagging expiries in 1-30 days might include next month's early birds or skip varying month lengths (28 vs. 31). It lacks the calendar precision of "This Month," leading to over- or under-inclusive sends that dilute your targeted renewal push.

Reference:
Create a Segment in Data 360
Build Segments in Data Cloud
Explore Customer Segments

Explanation:

✅ Correct Option:
C. Install the Salesforce Loyalty Member Mobile App. This is a pre-built, managed package mobile app provided by Salesforce specifically for Loyalty Management. It allows members to directly access their points balance, tier status, rewards, and transactions on their iOS or Android devices, perfectly fulfilling the requirement for heavy mobile users without custom development.

❌ Incorrect Option:
A. Enable Experience Cloud and customize the Loyalty Member Portal. While a valid method for web access, this creates a portal experience designed for a browser, not a native mobile application. It does not best serve "heavy mobile users" who prefer a dedicated app and may not provide the optimal mobile user experience (UX) out-of-the-box.

❌ Incorrect Option:
B. Create and implement a feature-rich Loyalty Member Mobile App. This suggests custom development, which is not an "existing capability" of Loyalty Management. The platform already provides a pre-built mobile app, making a custom-built solution an unnecessary and expensive effort that does not leverage available out-of-the-box functionality.

❌ Incorrect Option:
D. Configure either Service Cloud or Sales Cloud. Service and Sales Cloud are not designed to provide a direct member-facing mobile experience for loyalty programs. Their mobile apps are intended for internal users (agents and sales reps). This approach would not meet the requirement for customer access to their own program information.

📌 Summary:
The requirement is for a native mobile experience for end customers. Salesforce provides this exact capability via a pre-installable managed package app, the "Salesforce Loyalty Member Mobile App." This is the fastest, most efficient, and purpose-built solution to give members mobile access to their loyalty data.

Explanation

To award points automatically upon program enrollment, the system requires two key components. First, a mechanism to record the enrollment event is needed. Second, a business rule must evaluate that event and trigger the points award. This setup separates the member's action from the logic that grants the loyalty currency.

Correct Option:

✅ A. Create a Transaction Journal with an Activity type of ‘’Enrollment’’ that needs to be created when the customer signs up to join the Loyalty Program.
This journal acts as the system of record for the enrollment activity. It is the foundational transaction that proves the member performed the action that makes them eligible for the points.

✅ B. Create a Process rule that awards 500 points when the Activity Type =’Enrollment’.
This is the business logic that processes the journal entry. The rule listens for journals with the "Enrollment" type and automatically executes a "Credit Points" action to deposit the 500 points into the member's account.

Incorrect Option:

❌ C. Create a Loyalty Partner and associate one of the Partner’s products that must be purchased to award the 500 points.
This configuration is used for partner-based offers where a purchase is required. Since the points are for enrollment alone, with no purchase necessary, this setup is incorrect and overcomplicates the requirement.

❌ D. Create a Benefit that adds 500 points when the new member reaches the Top Platinum Level tier.
Benefits are tied to tier achievement, not initial enrollment. This would award points only after a member has progressed through the program and reached a high tier, not when they first join.

Key Point:
The solution requires creating the enrollment activity record (Journal) and the business logic to reward it (Process Rule). Partner products and tier benefits are not involved.

Reference:
Salesforce Help: "Loyalty Processes" and "Transaction Journals" in the Loyalty Management Implementation Guide.

Explanation:

For this scenario, the retailer needs to track when a member's last activity occurred to expire their points. The Qualifying Points currency is the correct choice because it is designed to impact a member's tier status, which is often tied to activity-based rules. The 'Activity Model' for points expiration is the precise method to achieve this. This model links point expiration to a member's last activity, such as a purchase or redemption, making it ideal for the requirement of expiring points after 18 months of inactivity. This approach encourages members to remain engaged.

Incorrect Option:

🔴 A. Set up a Non-Qualifying Points currency and apply the expiration model 'Fixed Model':
Non-Qualifying Points do not affect a member's tier status, and the requirement is to use a method that encourages members to return to purchase and redeem their points, which can be linked to tiers. The 'Fixed Model' expires points on a specific date, not based on member activity. This would not meet the requirement of expiring points after 18 months of inactivity.

🔴 C. Set up a Non-Qualifying Points currency, apply the expiration model 'Activity Model':
This option incorrectly uses Non-Qualifying Points. While the 'Activity Model' is the correct expiration method, using Non-Qualifying Points is not a best practice for a program that is trying to motivate members to maintain their tier status through activity. The program's core goal is to drive engagement, and Qualifying Points are better suited for this purpose.

🔴 D. Set up a Qualifying Points currency and apply the expiration model 'Fixed Model':
This option correctly uses Qualifying Points, but the expiration model is incorrect. The 'Fixed Model' would expire points on a specific, predetermined date, not based on the member's last activity. The retailer's requirement is to base the expiration on a rolling 18-month period of inactivity, which the 'Fixed Model' cannot support.

Summary:
The sports retailer wants to create urgency by expiring points if a member is inactive for 18 months. To achieve this, a Loyalty Consultant must configure the program to use a currency that tracks member engagement and a flexible expiration model. The best solution is to use Qualifying Points, as they are ideal for linking to tier status and member activity, and the Activity Model, which is specifically designed to expire points based on a member's last active date, perfectly meeting the 18-month inactivity requirement.

Reference:
Salesforce Help Documentation: Set Up a Points Expiration Model in Loyalty Management.

Explanation

In Salesforce Loyalty Management, the distinction between point types is crucial: Non-Qualifying Points (NQP) are the currency members earn for the sole purpose of redemption (getting rewards). Qualifying Points (QP) are used to measure member engagement and determine their Loyalty Tier (e.g., Bronze, Silver, Gold). Since the hotel's goal is to reward members with points that can be converted to cover a night's stay (a redemption reward), the correct currency type to use is the one designed specifically for redemption: Non-Qualifying Points.

✅ Correct Option: D

D. Non-Qualifying Points
Non-Qualifying Points (NQP) are the standard currency used for member redemption activities.
The entire premise of the program—earning points to be redeemed for a free night's stay—aligns perfectly with the function of NQP.
NQP balances can be used directly for rewards or converted into vouchers/discounts, fulfilling the goal of incentivizing more bookings by offering tangible rewards.
Unlike Qualifying Points, NQP can have different expiration rules (fixed or activity-based) that encourage frequent engagement and redemption.

❌ Incorrect Options

A. Qualifying Points
Qualifying Points (QP) are used to measure a member's engagement level to determine their tier status (e.g., moving from Silver to Gold). They typically cannot be redeemed for rewards. Using QP alone would allow members to earn a higher tier but give them no actual spendable points for the free night's stay, failing to meet the core redemption goal.

B. Tier Qualifying Points
Tier Qualifying Points (TQP) is another name or type of Qualifying Point used exclusively to track progress toward a specific loyalty tier. Like standard QP, they are not intended to be used for redemption against the cost of a hotel night. Using this currency type would miss the primary objective of rewarding the member with a spendable value.

C. Non-Qualifying and Qualifying Points
While a full loyalty program often uses both types (QP for tier progression and NQP for redemption), the prompt specifically asks which currency should be used for the goal of redeeming points for a free night's stay. The specific goal described is purely a redemption activity, which only requires the use of Non-Qualifying Points. Including QP is unnecessary and complicates the currency setup for this particular redemption objective.

🔗 Reference
Salesforce Help: Loyalty Program Currencies (Search for the definitions of Qualifying Points and Non-Qualifying Points, noting that Non-Qualifying Points are the currency used for member redemption.)

Explanation:

Correct Option: B. Name, Program, Program Partnership Category, Type, Billing Type
When setting up a program partner in Salesforce Loyalty Management, a specific set of required fields must be populated to ensure the partner is correctly integrated and managed within the system. The required fields include:

➡️ Name: The name of the partner company.
➡️ Program: The specific Loyalty Program the partner is associated with.
➡️ Program Partnership Category: Classifies the type of partnership (e.g., Earn Partner, Redemption Partner).
➡️ Type: The business type of the partner (e.g., Brand, Vendor).
➡️ Billing Type: Determines how the partner will be billed (e.g., Flat Rate, Per Transaction).

These fields are essential for defining the partner's role, relationship, and financial setup within the Loyalty program.

Incorrect Option:

A. Name, Partnership Start Data, Industry, Status, Billing Type:
This option includes fields that are not universally required for partner setup. Partnership Start Date is often optional, and Industry and Status are important but not required fields for the basic creation of the partner record. The missing Program and Program Partnership Category fields are critical for linking the partner to the loyalty program.

C. Name, Partnership Start Data, Billing Type, Status, Type:
This option is missing the Program and Program Partnership Category fields, which are fundamental for defining the partner's relationship with the loyalty program. Without these fields, the system cannot correctly associate the partner with a specific loyalty program and understand its role within it.

D. Name, Partnership Start Data, Industry, Status, Type:
This option is missing several key required fields, including Program, Program Partnership Category, and Billing Type. Without these, the partner record is incomplete and cannot be properly configured for the loyalty program. The fields included are insufficient to set up a functional partner relationship within Salesforce Loyalty Management.

Summary:
To successfully onboard a new program partner in Salesforce Loyalty Management, a consultant must fill in the required fields on the partner record. These fields are essential for defining the partner's identity, its relationship to the loyalty program, its specific role, and its financial arrangement. The specific fields required for this setup are Name, Program, Program Partnership Category, Type, and Billing Type, which are fundamental to establishing a functional and trackable partnership.

Reference:
Salesforce Help Documentation: Create a Program Partner.

Explanation:

In this scenario, the customer is eligible for a compensation voucher because the t-shirt is out of stock. Salesforce Loyalty Management enables agents to issue vouchers directly to the customer, ensuring they can redeem it immediately. The voucher must reflect the correct discount value and validity period for proper compensation.

Correct Option:

✅ C. Use Issue voucher from the Loyalty Program Member page
Allows the agent to directly issue a voucher to a specific customer.
Ensures the voucher is linked to the Loyalty Program Member record.
Can configure a 50% discount with a one-year validity, making it immediately usable.
This is the standard Salesforce method for agent-issued, real-time vouchers.

Incorrect Options:

❌ A. Use the “issue Voucher” flow template
Flow templates are designed for automated or repeatable voucher issuance.
They are not ideal for one-off, real-time customer compensation, as the agent cannot control the immediate issuance.
Using a flow template would require additional steps to assign the voucher, delaying customer satisfaction.

❌ B. Activate the voucher assignment batch
Voucher assignment batches are intended for bulk processing of vouchers, typically scheduled for multiple members at once.
This method is not real-time; the customer would not immediately receive the 50% discount.
Relying on a batch could lead to frustration, as the compensation would be delayed until the batch runs.

❌ D. Assign a voucher definition from the customer’s Loyalty Program Member
Assigning a voucher definition only defines the type and parameters of the voucher (e.g., discount percentage, expiration).
It does not actually issue the voucher to the customer.
Without issuing, the customer cannot redeem the discount, so this step alone is insufficient.

Summary:
To ensure immediate compensation, agents must issue the voucher directly from the Loyalty Program Member page. Batch, template, or definition-only methods won’t provide instant access or usability for the customer.

Reference:
Salesforce Loyalty Management – Vouchers Overview

Explanation:

✅ Correct Option: B
Using the “Category” mapping option allows the administrator to associate all products in a category (e.g., snacks) with a specific partner in one step. Since Chocolate cookies already belong to the snacks category, mapping the category to the partner automatically links this product and saves manual effort. This approach is efficient when multiple products in the same category need to be linked to the same partner.

✅ Correct Option: D
Using the “Product” mapping option ensures a direct association between a specific product and a partner. In this case, Green soda must be explicitly mapped to the beverages importer because it doesn’t belong to a broader shared category in this scenario. Mapping by product ensures precise linking without impacting other items. It is the simplest and most accurate way to connect this product to its partner.

❌ Option A
Manually adding the partner to the lookup on the snack product is less efficient than using category-based mapping. While it would work, it requires product-by-product updates instead of automating the relationship through category mapping. For organizations managing many products, this manual approach becomes time-consuming and inconsistent compared to using the category option.

❌ Option C
Adding the partner in the lookup directly on the Chocolate cookies product achieves the goal but is not the least-effort method. Because the product already belongs to the snacks category, mapping by category (Option B) will automatically cover this association and scale better if more snack products are introduced in the future. Therefore, Option C is redundant when a category option exists.

📘 Summary
The most efficient way to associate products with partners in Loyalty Management is by using Category mapping for products already grouped under a category and Product mapping for individual items without shared categories. In this scenario, UC should map Chocolate cookies by category to the snacks partner and Green soda by product to the beverages importer. Direct lookups (A and C) would work but require more manual effort and don’t scale as effectively.

🔗 Reference: Salesforce Help – Loyalty Management Partner Products