Explanation

Expanded Partner Management in Salesforce Loyalty Management allows a company to track point liability and financial transactions with external partners, a crucial feature for a complex partner ecosystem. The consultant must ensure the organization has the necessary license tier, the correct billing method for financial reconciliation, the system for recording partner-specific transactions, and the conversion mechanism for handling currency or point value differences with international partners. These features are fundamental for accurate accounting and settlement with partners.

✅ Correct Option: C. Advanced license, PostPaid Billing Type, Partner Ledgers, Partner Conversion Factor for Currencies
The Advanced license is typically required for the most complex features in Loyalty Management, including the full suite of Expanded Partner Management capabilities that go beyond basic partner enrollment.
PostPaid Billing Type is the mechanism used to define that the partner will be billed after members have accumulated points from their transactions, which is a common scenario for managing point liability and financial reconciliation.
Partner Ledgers are the dedicated records necessary to track the financial relationship, liability, and point balances specifically for each partner. The Partner Conversion Factor for Currencies is essential for accurately converting the value of points or currency when dealing with global partners who transact in different denominations.

❌ Incorrect Option: A. Growth license, PostPaid Billing Type, Partner Ledgers, Partner Conversion Factor for Currencies
The Growth license typically offers a baseline set of features and may not include the full complexity and scale of Expanded Partner Management, particularly the sophisticated financial tracking capabilities like Partner Ledgers and Conversion Factors. The Advanced license is generally needed for this level of functionality.

❌ Incorrect Option: B. Growth license, Prepaid Billing Type, Partner Transactions, Partner Conversion Factor O for Currencies
This option is incorrect primarily because of the Growth license (see A). Additionally, while Prepaid Billing Type is an option, PostPaid is the standard and most relevant model for tracking partner liability in scenarios requiring Partner Ledgers. Partner Transactions is not a standard configuration check; the system uses the Partner Ledgers to record the financial data.

❌ Incorrect Option: D. Advanced license, Partner Ledgers, Partner Transactions, Billing Type
While the Advanced license and Partner Ledgers are correct, this option is incomplete and less specific. Billing Type is too vague (it needs to specify PostPaid for the common partner liability model), and Partner Transactions is not the key feature to check; the ability to use the Partner Conversion Factor for Currencies is a critical component for expanded, often international, partner management setup.

🔗 Reference
For details on the features included in different Loyalty Management licenses, refer to the official Salesforce documentation:
Feature Availability with Loyalty Management Licenses

Explanation:

Setting up a Loyalty Promotion with Salesforce CDP and Marketing Cloud involves more than just creating promotions—it requires ensuring that member data segments are correctly prepared, activated, and shared with Marketing Cloud so that personalized campaigns can be executed. These steps are critical because promotions are driven by member behavior, tier, and engagement. Without sending the segments, activating them, or enabling connector settings, Marketing Cloud won’t receive the necessary data, and targeted campaigns may fail to reach the right audience.

Correct Options:

🟢 A. Send Loyalty Promotion Segments to Marketing Cloud
Sends curated member segments from Loyalty Management to Marketing Cloud. Ensures that promotions target the correct audience based on tier, activity, or engagement metrics. This step enables personalized communication and maximizes campaign effectiveness.

🟢 C. Activating and Publishing the Segment
Activation ensures the segment is live and ready to sync to Marketing Cloud. Publishing confirms the segment configuration is finalized, making it usable in campaigns. Without activation and publishing, the segment data cannot be shared or used effectively.

🟢 D. Enable Connector Settings on all the Loyalty Objects
Connector settings are required to establish the connection between Loyalty Management and Marketing Cloud. They allow member data, promotions, and segments to flow seamlessly for campaign execution. Ensures that changes in Loyalty Management are automatically reflected in Marketing Cloud.

Incorrect Options:

🔴 B. Automatically Add a New Individual Relationship
This relates to member relationships and not directly to promotion execution. It does not impact the creation, activation, or syncing of promotion segments.

🔴 E. Enable Service Connector for Promotion Escalations
Promotion escalations are optional advanced features for alerting and workflow automation. Not required for the basic setup of sending segments and running promotions.

Key Point:
To successfully run Loyalty Promotions via Salesforce CDP and Marketing Cloud, the three critical steps are: sending the segments to Marketing Cloud, activating and publishing them, and enabling connector settings on Loyalty objects. These steps ensure data flows correctly and campaigns target the right audience. Optional features like escalation connectors are not necessary for standard setups.

Reference:
Salesforce Loyalty Management: Promotions with Marketing Cloud

Explanation:

✅ Correct Option: B
On the Case Page Layout, the "View Member Profile" component should be added. This is the official Salesforce-recommended way to show Loyalty Program Member details on Case records in Service Cloud. It allows customer service agents to quickly see membership information such as points, tier, and program status. Additionally, administrators can configure related lists from the Loyalty Program Member object to give agents full visibility into loyalty activity.

❌ Option A
The "Related Record" component with "First Lookup" does not provide the full functionality for Loyalty Management. While related record components can display basic lookup information, they cannot show the detailed loyalty program data such as points, tier, or transactions. Using this option would limit agents from accessing the comprehensive loyalty details they need for customer interactions.

❌ Option C
The Loyalty Program Member related lists cannot be directly embedded into the Case page layout. Related lists are tied to objects, and in this case, the Case object does not directly expose the loyalty information as related lists. Salesforce instead provides specialized components such as "View Member Profile" for this purpose, making this option invalid for the requirement.

❌ Option D
The "View Related Membership" action is not the correct component to use on Case records. It is designed for different contexts, such as showing related memberships on Accounts or Contacts, but does not directly apply to Case layouts. If used, it would not deliver the comprehensive loyalty program visibility required by service agents on a Case record.

📘 Summary:
To enable Service Cloud agents to view Loyalty Program Member details on a Case, the "View Member Profile" component must be added to the Case page layout. This approach provides the right level of visibility into loyalty data, such as tier and points, without relying on less effective related record or membership components. Other options lack the required integration capabilities.

🔗 Reference: Salesforce Help – Set Up Loyalty Management for Service Agents

Explanation

Post-rollout, Loyalty Management automations rely on flows and batch jobs for processing, with Monitor Workflow Services tracking their status. Data Processing Engine (DPE) actions handle high-volume transformations like point calculations or tier updates, but they demand specific backend permissions. When only DPE-involved automations fail while others succeed, it signals a licensing gap for the automated execution user, halting data ops without affecting simpler loyalty flows.

Correct Option:

✅ A. The Default Workflow User is missing the Data Pipelines Base User permission set license
In Salesforce, the Default Workflow User executes automated processes like flows and batch jobs, including DPE actions for loyalty data transformations. This license is essential for DPE access, enabling secure data processing in the background. Without it, DPE jobs fail with permission errors in Monitor Workflow Services, but non-DPE automations run fine since they don't require Data Cloud pipeline capabilities tied to this PSL.

Incorrect Options:

❌ B. The Default Workflow User is missing the CLAAnalytics Base User permission set license
CLAAnalytics Base User (for CRM Analytics in Customer 360) supports reporting and dashboards on loyalty data but doesn't grant execution rights for DPE transformations or automations. Assigning this wouldn't resolve workflow failures, as DPE relies on Data Cloud's processing engine, not analytics tools—leaving batch jobs stuck while analytics queries remain unaffected.

❌ C. The Default Workflow User is missing the Loyalty Management permission set license
Loyalty Management PSL provides core object access for manual edits and basic automations, like creating transaction journals. However, DPE actions for advanced computations (e.g., point expirations) need separate Data Pipelines licensing. This explains why non-DPE loyalty flows work: they use standard permissions, but DPE fails due to missing pipeline execution rights.

❌ D. The Default Workflow User is missing the CLAAnalytics Base Admin permission set license
This admin variant of CLAAnalytics handles advanced analytics setup and segmentation, not automation execution or DPE jobs. It offers no help for workflow services failures, as DPE requires Data Pipelines for data ingestion and transformation—analytics admins can't bridge that gap, keeping loyalty batch processes in a failed state.

Reference:
https://help.salesforce.com/s/articleView?id=sf.concept_data_processing_engine_permission.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.loyalty_data_processing_engine.htm&type=5

Explanation

To automatically award a new member upon sign-up, the Program Administrator must create a record-triggered flow on the Loyalty Program Member object. This flow needs to execute two core actions: Credit Points (for the 100 points) and Issue Voucher (for the 10% discount). These actions are essential components of the Loyalty Management package, streamlining the process without needing to manually generate Journal or Ledger records.

Correct Option: B. Create a record triggered flow using Journal Type. Journal SubType, Transaction Journal. Credit Points action and Issue Voucher action
Creating a record-triggered flow on the Loyalty Program Member object (triggered upon record creation) is the standard and most efficient approach for sign-up promotions. The flow's logic should call the standard Credit Points action to grant the 100 points and the Issue Voucher action to provide the 10% discount benefit. While it uses Journal Type, SubType, and Transaction Journal fields in the backend for processing, the key flow elements are the standard actions, making this the correct operational answer.

Incorrect Option: A. Create a record triggered flow using Journal Type, Journal SubType, Transaction Journal, and Process O Member Benefit Action
The Process Member Benefit Action is typically used to process a benefit that has already been awarded (e.g., tier upgrade benefits or perks). It is not the correct action to award a new member points and a discount voucher upon the initial sign-up event. The correct actions for awarding points and vouchers are Credit Points and Issue Voucher.

Incorrect Option: C. Create an autolaunched flow using Transaction Journal, Loyalty Ledger, and Get Loyalty Promotions for Transactions
An autolaunched flow is typically called from a process builder or another flow and would not be the direct mechanism to monitor new member creation. Furthermore, the Get Loyalty Promotions for Transactions action is used in transaction processing to find and apply relevant promotions, not to credit points or issue vouchers for a sign-up event.

Incorrect Option: D. Create an autolaunched flow using Journal Type. Journal SubType, Transaction Journal, Credit Points ° action, and Issue Voucher action
Using an autolaunched flow would require an extra step (e.g., a Process Builder) to trigger it when a new member is created, which is less efficient than a direct record-triggered flow. While the actions (Credit Points and Issue Voucher) are correct, the flow type (autolaunched) is incorrect for directly capturing the new member sign-up event in the simplest manner.

🔗 Reference
For documentation on using flows for automating Loyalty Management actions, please refer to the official Salesforce documentation on the Credit Points and Issue Voucher flow actions:
Loyalty Management