A fundamental architectural principle in Salesforce Loyalty Management is that a single Loyalty Member Portal, which is an Experience Cloud site, can only be associated with one Loyalty Program. Therefore, to support a new Loyalty Program, a new portal must be created. To meet the requirement of retaining the same design and functionality, the most efficient approach is to build this new portal using the existing, pre-built Experience Cloud components, themes, and layouts from the original portal. This ensures a consistent member experience across both programs without redundant development effort.

A. A single Experience Cloud site (Loyalty Member Portal) cannot be assigned to more than one Loyalty Program at the same time.

C. Creating new components is unnecessary and inefficient, as the requirement is to replicate the existing design and functionality, which can be achieved with existing components.

1. Salesforce Help - Create a Loyalty Program: In the setup steps for a Loyalty Program, the "Experience Cloud Site" field is a lookup that allows associating only one site with the program. This demonstrates the one-to-one relationship. (See Step 6 under "Create a Loyalty Program").

2. Salesforce Help - Set Up Your Loyalty Program's Experience Cloud Site: This document outlines the process of creating a new site using the Loyalty Management template. It states, "After you create the site, you can associate the site with your loyalty program," confirming that a new program requires a dedicated site to be created and associated.

3. Salesforce Help - Loyalty Management Components in Experience Builder: This guide details the standard, reusable components available for building a Loyalty Member Portal, such as Loyalty Member Profile and Loyalty Tier Progress. This supports the concept of using existing components to build out the functionality of a new portal.

Batch Management in Salesforce Loyalty Management is specifically designed to handle the asynchronous processing of large volumes of records. In the context of receiving nightly transaction data from a POS system, its primary benefit is the ability to efficiently process these high-volume transactions against loyalty rules (B). A crucial component of this feature is the operational oversight it provides; administrators can use the Batch Jobs page to track the status, progress, and health of each job, ensuring data is processed correctly and troubleshooting any failures (A).

C. Load large volumes of external data coming from external systems: Batch Management processes records that are already loaded into Salesforce objects (e.g., Transaction Journal), it does not perform the initial data loading or extraction from external systems.

D. Process zip files full of Loyalty Transactions coming from point-of-sales systems: The native Batch Management feature processes Salesforce records, not file formats like zip files. An external process would be required to handle file extraction before data can be processed.

1. Salesforce Help, Process Transaction Journals in Batches: "Use batch jobs to process a large number of transaction journals at a time... You can track the progress of batch jobs on the Batch Jobs page in Loyalty Management. The Batch Jobs page shows the status of each job part and the number of records that are processed, have failed, or are yet to be processed." (This supports options A and B).

2. Salesforce Help, Batch Management: "Batch Management helps you process large volumes of data by using batch jobs. You can monitor the health of your batch jobs and ensure that they run successfully." (This directly confirms options A and B as key benefits).

3. Salesforce Help, Considerations for Batch Management: This page details the record processing limits (e.g., "Batch jobs can process up to 250,000 records in 24 hours"), underscoring its purpose for handling large volumes (supporting option B). It does not mention file processing capabilities (disproving option D).

Salesforce Loyalty Management processes transactions from the Transaction Journal object to award points. This can be automated using two primary models: real-time and batch processing.

A Schedule-Triggered Flow is used for the batch processing model, where the flow runs at a predefined schedule (e.g., daily) to process a large volume of unprocessed transaction journals.

The term "Evaluation Flow" refers to the real-time processing model. In this model, a flow is triggered to evaluate a single transaction as soon as it is created (functionally equivalent to a Record-Triggered Flow). This flow evaluates the transaction against the loyalty program rules to accrue points immediately.

B. Autolaunched Flow (No Trigger): This flow type contains the processing logic but lacks an inherent trigger. It must be invoked by another process (like a Record-Triggered Flow or Apex), making it a component of the solution rather than the complete automation pattern itself.

D. Screen Flow: This flow type requires user interaction through a user interface. Automating points accrual from a ticket purchase is a backend process that should not require manual user input.

1. Salesforce Help, Document: Process Transaction Journals with Flows.

Reference: This document explicitly outlines the two primary automation methods. It states, "You can create a flow that is triggered when a transaction journal is created or run a flow on a schedule to process a batch of transaction journals." This directly supports the real-time ("Evaluation Flow") and batch (Schedule-Triggered Flow) models.

2. Salesforce Help, Document: Flow Core Action for Loyalty Management: Process Loyalty Ledger.

Reference: This document describes the invocable action used within the flows. It explains that the Process Loyalty Ledger action "Processes a member's eligible, unprocessed transaction journals and updates the member's points balance." This action is the core engine used by both Schedule-Triggered and real-time evaluation flows.

3. Salesforce Help, Document: Flow Types.

Reference: This documentation defines the different types of flows. It describes a Schedule-Triggered Flow as one that "launches at a specified time and frequency," confirming its use for batch processing. It defines a Screen Flow as requiring a user interface, confirming it is unsuitable for this backend process. It defines an Autolaunched Flow as needing to be invoked by another process, clarifying why it's a component rather than a complete triggering automation in this context.

Salesforce Loyalty Management provides a specific, pre-built Lightning Web Component named 'View Member Profile' designed for this exact purpose. An administrator can add this component to the Case Lightning Record Page. The component automatically uses the Contact associated with the Case to find and display the corresponding Loyalty Program Member's complete profile, including their tier, points balance, and related information like transaction history. This is the most direct and feature-rich method to meet the service team's requirement.

A: The standard 'Related Record' component is a generic solution. The 'View Member Profile' component is purpose-built for Loyalty Management and provides a more comprehensive and context-aware view of member data.

C: Loyalty Program Member is not a direct child of the Case object, so its related lists cannot be directly embedded on the Case Page Layout. A component is required to traverse the relationship via the Contact.

D: A 'View Related Membership' action would require an agent to click and navigate away from the Case record to see the information, whereas the request is to view the information on the Case record itself.

1. Salesforce Help Documentation, "View a Member's Profile": This document explicitly states, "The View Member Profile component shows a loyalty program member’s details, such as the member’s tier, points balance, and enrolled promotions. You can add this component to the Account, Contact, and Case record pages." This directly supports the use of the 'View Member Profile' component on the Case record page.

2. Salesforce Help Documentation, "Loyalty Management Components for Experience Cloud Sites and Salesforce Pages": This page lists and describes the available components for Loyalty Management. It details the 'View Member Profile' component as the primary tool for displaying a member's summary and related lists on standard Salesforce pages, confirming it as the correct tool for the job.

3. Salesforce Help Documentation, "Configure the Service Console for Loyalty Management": This guide provides step-by-step instructions for Service Cloud integration. In the section "Add Loyalty Components to the Case Record Page," it instructs administrators to: "Drag the View Member Profile component to the page canvas." This confirms the exact procedure described in the correct answer.

To build a network of brand advocates, Universal Containers must move beyond simple transactional rewards and create personalized, engaging experiences that foster a deeper connection with the brand. Loyalty Management facilitates this by:

1. Integrating with Salesforce CDP to segment members and deliver targeted promotions, making members feel understood and valued (A).

2. Using tiers to differentiate members based on their engagement, offering exclusive benefits that encourage continued interaction and a sense of status (C).

3. Rewarding non-transactional, advocacy-based behaviors, such as social media posts, with unique experiences, which directly encourages and reinforces brand endorsement (D).

These strategies combine to create positive experiences that transform satisfied customers into active brand advocates.

B: A simple points-per-dollar program is purely transactional and does not specifically incentivize the advocacy behaviors UC wants to cultivate.

E: Separating loyalty and analytics systems creates data silos, hindering the 360-degree customer view necessary for the personalization required to build brand advocates.

1. Salesforce Help, Salesforce CDP and Loyalty Management: "You can use Salesforce CDP to create segments of loyalty program members based on their profile, tier, points balance, and engagement activities. You can activate the segments for marketing campaigns and journeys." This supports using segmentation for targeted promotions (Answer A).

2. Salesforce Help, Tiers in Loyalty Management: "Tiers help you classify members based on their engagement with your brand. You can create tiers and provide members with exclusive benefits for each tier... Tiers help you retain high-value customers and keep them engaged with your brand." This directly supports using tiers for engagement (Answer C).

3. Salesforce Help, Benefits in Loyalty Management: "You can create benefits of different types, such as a product or service discount, shipping fee waiver, or access to exclusive events." This supports offering experiential rewards like concert tickets (Answer D).

4. Salesforce Help, Loyalty Program Processes: The documentation details how to create processes that reward various member behaviors, including non-transactional activities. The "Use a Flow to Credit Points for a Non-Transactional Activity" section explicitly covers rewarding actions beyond purchases, such as social media engagement (Answer D).

Implementing a targeted strategy within Salesforce Loyalty Management is designed to enhance program efficiency by moving from a generic to a specific approach. This strategy fundamentally relies on data-based segmentation (D), where members are grouped based on criteria like purchase history, engagement, or demographics. Once these segments are defined, the program can deliver personalized digital marketing (A), including tailored promotions, offers, and communications. This personalization increases relevance for members, which in turn boosts engagement and improves the overall return on investment for the loyalty program.

B. Transaction journey data is automatically archived: Data archiving is a platform-level data management process and not a direct benefit or outcome of implementing a targeted loyalty strategy.

C. Customers are rewarded based on their tiers: Tier-based rewards are a core structural component of a loyalty program, likely established at launch. A targeted strategy uses tiers for segmentation but does not create the concept of tier-based rewards itself.

1. Salesforce Help, Segments in Loyalty Management: "Segments help you group your loyalty program members based on a specified criteria. You can then target these segments with specific promotions and benefits." This directly supports the concept of a data-based segmentation strategy (D) as a core part of a targeted approach.

2. Salesforce Help, Promotions in Loyalty Management: "Create promotions to engage with your loyalty program members and to increase brand loyalty... You can make promotions available to all members or only to members of specific tiers or segments." This highlights how segmentation enables targeted, and therefore more personalized, marketing efforts (A).

3. Salesforce Help, Personalize Loyalty Program Member Experience: "To create a personalized experience for your loyalty program members, you can use Flow Builder, Marketing Cloud, and Experience Cloud... Use Marketing Cloud to send personalized emails to your members about their loyalty program activity." This document explicitly connects the use of member data and segmentation with delivering personalized experiences.

To communicate a new promotion to eligible members, a two-step process is required: segmentation and engagement.

1. Salesforce Customer Data Platform (CDP), now part of Data Cloud, is used for segmentation. It unifies member data from Loyalty Management with other sources to create a complete customer profile. This allows the creation of precise segments of "eligible members" based on criteria like tier status, point balance, or past engagement, which can then be activated for campaigns.

2. Salesforce Marketing Cloud is the engagement platform. Once the segment of eligible members is identified (either directly or via CDP), Marketing Cloud is used to design and execute the communication campaign across various channels, such as email, SMS, or mobile push notifications, to inform members about the new promotion.

A. Salesforce Cloud Intelligence: This is a general term for analytics tools like CRM Analytics. While it provides insights and dashboards on program performance, it is not the primary application for executing communication campaigns.

B. Salesforce Field Service Lightning: This application is designed for managing a mobile workforce, scheduling service appointments, and optimizing field operations. It is not intended for marketing communications to loyalty program members.

1. Salesforce Help, Topic: Customer Data Platform and Loyalty Management: "Use Customer Data Platform with Loyalty Management to get a unified view of your loyalty program members. You can then segment members and act on the insights. For example, you can create a segment of your high-value loyalty program members and then run a campaign for them."

2. Salesforce Help, Topic: Marketing Cloud and Loyalty Management: "Use Marketing Cloud with Loyalty Management to create personalized and engaging journeys for your loyalty program members. You can use Journey Builder to send welcome emails to new members or to notify members about their tier upgrade."

3. Salesforce Help, Topic: Activate Segments on Marketing Cloud - Business Manager: "After you create your segments in Customer Data Platform, you can publish them to activation targets... You can activate segments on Marketing Cloud to send emails to your loyalty program members."

The requirement is to trigger a Marketing Cloud Journey immediately when a record is created in a custom Salesforce object ("Voucher Issued"). The "Salesforce Data Event" entry source is the standard, declarative feature designed for this exact purpose. Option C correctly configures this entry source to listen for the creation of a VoucherIssuedc record. This method allows for near real-time injection into the journey and enables the use of related Salesforce data for personalization (like First Name and Membership Number) with minimal configuration and no custom code, thus meeting the "least amount of development effort" requirement.

A: This option uses a "Salesforce Campaign" as the entry source. The trigger is a new voucher record, not a member being added to a campaign.

B: This option uses the correct entry source type ("Salesforce Data Event") but is configured for the wrong object ("Lead") instead of the required "Voucher Issued" custom object.

D: This option uses an "API Event" entry source. While it could work, it requires custom development (e.g., an Apex trigger) to make an API call to Marketing Cloud, which contradicts the "least amount of development effort" constraint.

1. Salesforce Help Documentation, Salesforce Data Entry Source: This document explicitly describes the functionality shown in Option C. It states, "The Salesforce Data entry source lets you choose a Salesforce object, then filter the records that enter a journey... A journey can be triggered when a record is created or updated." This directly supports using a Salesforce object creation event as the journey trigger. (Salesforce Help, Marketing Cloud, Journey Builder, Entry Sources section).

2. Salesforce Help Documentation, Use Salesforce Data in Journey Builder: This guide details the configuration process. It outlines the steps: "Select the Salesforce Data entry source... Choose a Salesforce object... Select who to inject... Set entry criteria... Select entry data." The screenshot in Option C is a direct representation of these configuration steps for the specified custom object. (Salesforce Help, Marketing Cloud, Journey Builder, Audiences section).

3. Salesforce Help Documentation, Entry Sources: This page provides an overview of all available entry sources. It differentiates the "Salesforce Data" source, which is integrated via Marketing Cloud Connect for declarative setup, from the "API Event" source, which is used for transactional sends triggered by an API call. This distinction highlights why the Salesforce Data Event is the lower-effort solution for this use case. (Salesforce Help, Marketing Cloud, Journey Builder, Entry Sources section).

To grant users access to a CRM Analytics application like "Analytics for Loyalty," two distinct permissions must be assigned at the user level. First, the user requires a permission set license, specifically "CRM Analytics Plus User," which enables the core functionality of the analytics platform for that user. Second, the user must be assigned a permission set, such as "Analytics for Loyalty User" or "Analytics for Loyalty Manager." This permission set grants the specific permissions needed to access the components of the Analytics for Loyalty app, including its datasets, lenses, and dashboards. Both are required for the user to see and use the app.

A. Assign user access to the analytics for Loyalty role.

Roles in Salesforce primarily define a user's position in the hierarchy, which controls record-level access visibility, not access to applications like CRM Analytics.

D. Assign the user the analytics profile for analytics for Loyalty.

While profiles can grant permissions, the standard and best practice for managing access to CRM Analytics is through permission sets and permission set licenses for more granular and scalable control.

1. Salesforce Help, Set Up the Analytics for Loyalty App: "To give users access to the Analytics for Loyalty app, assign them the CRM Analytics Plus permission set license. Then assign them the Analytics for Loyalty Manager or Analytics for Loyalty User permission set." This directly confirms the necessity of both the permission set license (Option B) and the specific permission sets (Option C).

2. Salesforce Help, Assign Permission Sets for CRM Analytics: "To enable CRM Analytics functionality for users in your org, first assign each user a permission set license. Then, to grant users the permissions they need, assign them one of the standard permission sets: CRM Analytics Plus Admin or CRM Analytics Plus User." This document establishes the foundational requirement of assigning a permission set license before assigning a permission set for access.

The tier-upgrade process in Salesforce Loyalty Management is a two-stage operation. First, a batch process identifies members who qualify for a tier change based on defined rules. Second, an orchestration process executes the tier update for the identified members.

Option C correctly models this two-stage design by proposing two separate flows. The first flow serves as the batch process to evaluate the tier-upgrade rule and populate the specified custom object with qualified members. The second flow is a record-triggered flow on that custom object, which handles the orchestration, such as calling the updateTier action and sending notifications. This separation of concerns is a standard design pattern for scalable automation.

A. A flow to perform both tier-upgrade rule and tier-upgrade orchestration process

A single flow is not suitable for a batch process on a large number of members as it would likely exceed Salesforce governor limits.

B. A flow to schedule and process the custom object's pending records and another flow to perform tier-upgrade orchestration process

This is an inefficient design. A single record-triggered flow is sufficient to process records created in the custom object; a separate scheduling flow for processing is redundant.

D. A data-processing-engine (DPE) to identify the qualified members

While DPE is the recommended tool for the identification stage, this option is incomplete as it only addresses one of the two required components for the entire process.

1. Salesforce Loyalty Management Developer Guide, "Automate Tier Updates": This guide details the creation of a flow to manage the tier update process. It states, "Create a flow that's triggered when a record is created in the custom object that stores members' tier assessment details... Use the Update Member Tier invocable action in the flow to upgrade or downgrade the member's tier." This confirms that a flow is the correct component for the orchestration part of the process.

2. Salesforce Help, "Tier Processing": This document outlines the end-to-end process. It recommends creating a Data Processing Engine definition to identify members and then a "flow to process the records in the custom object and update the members' tier." This supports the two-component architecture (identification and orchestration) that option C describes, even though it suggests DPE as the preferred tool for the first component. Option C provides a complete, two-component solution using flows for both parts, which is a valid architectural choice.