To implement Salesforce Loyalty Management's partner capabilities, the Advanced license is a mandatory prerequisite. Before configuration, a consultant must confirm the business requirements for the partner's billing model, such as PostPaid, where partners are invoiced periodically for points they issue. The setup process automatically creates Partner Ledgers to track these financial transactions. Additionally, if the partner operates in a different currency than the loyalty program, the Partner Conversion Factor for Currencies must be checked and defined to ensure accurate financial reconciliation. These elements are foundational checks for a successful partner management setup.

A. The Growth license does not include the necessary Partner Management features; the Advanced license is required.

B. The Growth license is insufficient for Partner Management, which is an Advanced license feature.

D. This option is less precise. "Billing Type" is generic, and "Partner Transactions" are a result of the setup, not a prerequisite check like the specific billing model.

---

1. Salesforce Help, "Considerations for Partner Management": This document explicitly states the license requirement. It reads, "To use the Partner Management feature, you require the Loyalty Management - Advanced license." This directly supports the choice of the Advanced license and invalidates options A and B.

2. Salesforce Help, "Set Up Partners in Your Loyalty Program": This guide details the setup process, which includes selecting a Billing Type (Prepaid or Postpaid) and setting a currency conversion factor. It states, "If the partner's currency is different from your org's default currency, you can provide a conversion factor." This supports the inclusion of "PostPaid Billing Type" and "Partner Conversion Factor for Currencies" as key setup decisions.

3. Salesforce Help, "Partner Billing in Loyalty Management": This document describes the two billing models, Prepaid and Postpaid, confirming that selecting a specific billing type is a core part of the setup. It also explains that a ledger is used to track these transactions: "When you add a partner to your loyalty program, a ledger is created for the partner." This validates the importance of "Partner Ledgers".

To enable an external application, such as a member portal, to securely access Salesforce data via APIs, a Connected App must be configured within the Salesforce Platform. The Connected App acts as an intermediary, using standard protocols like OAuth 2.0 to authenticate the external system and authorize its access to specific Salesforce resources. This is a fundamental security and integration prerequisite for allowing external systems to call Salesforce APIs, including those for Loyalty Management, to fetch member information.

A. Create custom objects in Loyalty: Accessing standard member information does not require creating custom objects; Loyalty Management uses its own set of standard and managed objects.

C. Create customer integration code: Writing integration code is the implementation step for calling the API, but the prerequisite on the Salesforce side is to first establish the secure connection point via a Connected App.

D. Create Data Processing jobs: Data Processing Engine (DPE) jobs are used for batch processing and rule calculations, not for enabling real-time, transactional API access from external systems.

1. Salesforce Help, Loyalty Management Developer Guide, "Get Started with Loyalty Management APIs": "To get started with Loyalty Management APIs, create a connected app in your Salesforce org. The connected app gets a consumer key and a consumer secret, which are used in the OAuth 2.0 authentication flow to get an access token."

2. Salesforce Help, "Connected Apps": "A connected app integrates an application with Salesforce using APIs. Connected apps use standard SAML and OAuth protocols to authenticate, provide single sign-on, and provide tokens for use with Salesforce APIs."

3. Salesforce Developer Documentation, "OAuth 2.0 and OpenID Connect on the Salesforce Platform": This documentation details the authentication flows that rely on a Connected App's consumer key (client ID) and consumer secret (client secret) to grant access tokens for API requests. The creation of the Connected App is the first step in any of these flows.

The scenario requires the configuration of three distinct redemption rules based on member tier and transaction value.

1. Blue Tier Rule: The requirement is that for Blue-tier members (a logical inference from the options and the likely typo in the third bullet point), 1 non-qualifying point equals $1, regardless of the transaction amount. This translates to a formula where the points deducted = transaction amount. Option A correctly implements this.

2. Gold Tier Rule (High Value): For Gold-tier members with a transaction of $200 or more, 1 non-qualifying point equals $2. The formula is points deducted = transaction amount / 2. Option D correctly implements this.

3. Gold Tier Rule (Low Value): For Gold-tier members with a transaction less than $200, 1 non-qualifying point equals $1. The formula is points deducted = transaction amount. None of the provided options correctly represent this specific rule.

Therefore, only two of the provided options are demonstrably correct based on the requirements. The question's premise of selecting three options is flawed.

B. This rule is a subset of the rule in option A. Option A is more comprehensive and accurate as it applies to any transaction amount for Blue members, as required.

C. This option describes an accrual action (tier-qualifying multiplier), which relates to earning points, while the question is about redemption, which involves deducting points.

E. This option provides an incorrect outcome for Gold-tier members with transactions of $200 or more. It contradicts the specific requirement that 1 point equals $2 in this scenario.

1. Salesforce Help: Use Rules to Define a Promotion's Logic. This document explains that promotion eligibility is defined by creating rules with specific criteria and outcomes. A promotion can have multiple rules that are run in a defined order. This supports the approach of creating separate rules for each tier and transaction value condition.

2. Salesforce Help: Promotion Rule Criteria Attributes. This official documentation lists the attributes available for defining rule criteria. It confirms that rules can be based on MemberTierName (e.g., 'Gold', 'Blue') and transaction-related fields like TransactionAmount, which are the exact criteria needed to implement the specified logic.

3. Salesforce Help: Promotion Rule Action Attributes. This document details the possible outcomes of a rule. For a redemption promotion, the action would involve debiting points. The PointsToDebit attribute can be set using a formula, such as TransactionAmount or TransactionAmount / 2, as required by the scenario and correctly represented in options A and D.

The Loyalty Analytics - Base App permission set license is included with the Salesforce Loyalty Management license to provide foundational analytics capabilities. This specific license grants users access to the Loyalty Analytics app but imposes a data volume limitation. According to official Salesforce documentation, users with this license can analyze a maximum of 10 million rows of data. This limit is a key characteristic of the base license, distinguishing it from full CRM Analytics Plus licenses which offer higher or unlimited data row capacities.

A. Rows do not have an analysis limit, only licenses do: This is incorrect. The Loyalty Analytics - Base App license itself imposes a specific 10 million row analysis limit.

B. Administrators can analyze up to 25 million rows: This is incorrect. The 25 million row limit is associated with the CRM Analytics Plus license, not the Loyalty Analytics - Base App license.

C. Administrators can analyze up to 1 million rows: This is incorrect. The documented limit for the Loyalty Analytics - Base App is 10 million rows, not 1 million.

1. Salesforce Help Documentation, "CRM Analytics for Loyalty": This document explicitly states the limitation. Under the main description, it reads, "The Loyalty Analytics - Base App permission set license gives you access to Loyalty Analytics. With this license, you can analyze up to 10 million rows of data."

2. Salesforce Help Documentation, "Salesforce Loyalty Management Licenses": This page details the components included with the Loyalty Management license, confirming that the "Loyalty Analytics - Base App" permission set license is a part of the offering, which is subject to the aforementioned 10 million row limit.

To provide the Member Services team with a comprehensive view of a member's activity on the Contact record, two key components should be added. The Transaction Journals related list (C) offers a detailed, chronological log of every point transaction, including accruals, redemptions, and manual adjustments, which directly addresses the need to see specific activities. The Member Summary Embedded Dashboard (A) provides a visual, at-a-glance summary of the member's engagement, key metrics, and recent activities. Together, these components give service agents both a high-level overview and the granular detail required to effectively assist members.

B. Incorporate the Member Service Manager Home Dashboard on the Contact record

This dashboard is designed for a Home page to show aggregate, program-level performance metrics for managers, not data for a single member on a Contact record.

D. Incorporate the ‘View Member Profile’ component on the Contact record

This component displays a member's summary information, such as their current tier and points balance, but it does not show the detailed list of individual transactions or adjustments.

1. Transaction Journals:

Salesforce Help, Loyalty Management Developer Guide, "TransactionJournal". This section details that the TransactionJournal object "Represents a journal entry for a transaction that results in a change in a member's points balance." Adding this as a related list provides the required transaction history.

Salesforce Help, Set Up Your Org for Loyalty Management, "Add Related Lists to Page Layouts". This guide instructs administrators on how to add related lists like Transaction Journals to objects such as Contact or Account for visibility.

2. Member Summary Embedded Dashboard:

Salesforce Help, Loyalty Analytics, "Loyalty Management Dashboards". This document describes the "Member Summary Embedded" dashboard, stating it is "Embedded on the Contact or Account page, the dashboard shows key metrics about a member's engagement with the loyalty program." This confirms its purpose for viewing member-specific data on the Contact record.

3. View Member Profile Component:

Salesforce Help, Loyalty Management Developer Guide, "Lightning Web Components for Loyalty Management". The documentation for the loyaltyMemberProfile component specifies that it is used to "View a member's profile information, such as the member's tier, points balance, and the currency balance," confirming it is for summary data, not transaction lists.

Salesforce Loyalty Management allows administrators to configure three distinct types of vouchers to reward program members. These types define the nature of the benefit provided. The available types are:

1. Discount Percentage: Offers a percentage-based discount on a transaction (e.g., 20% off an order).

2. Fixed Value: Provides a specific monetary amount off a transaction (e.g., $10 off). This is also referred to as a Fixed Amount discount.

3. Product or Service: Grants the member a specific product or service at no cost (e.g., a free coffee or complimentary shipping).

A. Promo Code: A promo code is a mechanism used to distribute and redeem a voucher, not a fundamental type of voucher benefit itself.

D. Gift Card: While a fixed-value voucher can function similarly to a gift card, "Gift Card" is not a distinct, configurable voucher type within the Loyalty Management setup.

1. Salesforce Help, Vouchers in Loyalty Management: This document outlines the voucher framework and its capabilities. It states, "Vouchers can provide members with a percentage or fixed amount discount on products. Vouchers can also provide members with a product or service, for example, a free dessert or a free car wash." This directly supports options B, C, and E.

2. Salesforce Help, Create a Voucher Definition: In the setup steps for creating a voucher, the "Discount Type" field is a required picklist. The available values in this picklist are "Percentage," "Fixed Amount," and "Product or Service," which correspond directly to the correct answers.

The Data Processing Engine (DPE) is the correct component for this task. It is specifically designed to query large volumes of data from multiple standard and custom Salesforce objects, perform complex transformations and aggregations, and write the results back to other objects. In Loyalty Management, DPE is the standard tool used for computationally intensive processes like calculating qualifying points for tier upgrades, aggregating member behavior for promotions, and processing transaction journals. Its ability to handle high data volumes efficiently makes it the ideal choice for the described scenario.

A. Batch Management: This is a general administration feature for monitoring jobs. While DPE jobs run in batches, "Batch Management" itself is not the tool that performs the data aggregation.

B. Decision Table: Decision Tables are used to define and execute business rules based on a set of inputs (e.g., determining promotion eligibility), not for aggregating high volumes of data.

C. Quick Actions: Quick Actions are user interface components designed for users to perform simple, record-specific tasks, not for complex, back-end processing of large datasets.

1. Salesforce Help, Data Processing Engine: "Use Data Processing Engine to transform data that's available in your Salesforce org and write back the transformation results as new or updated records. Data Processing Engine gives you a user-friendly, declarative interface to query, filter, join, and aggregate data from various objects." (See "Get Started with Data Processing Engine" section).

2. Salesforce Help, Loyalty Management Tier Processing: "Loyalty Management uses a Data Processing Engine definition to run the tier assessment process... The Data Processing Engine job aggregates the member’s total qualifying points..." (See "How Does Tier Processing Work?" section).

3. Salesforce Help, Decision Tables: "Decision tables automate decisions by using a set of rules. A decision table contains a set of conditions and a corresponding set of results." (See "Decision Tables" section). This highlights its function as a rule engine, not a data aggregator.

The tier group uses a Fixed Model with a one-year period and a Qualifying Points (QP) reset date of December 31. The key setting is "Extend Expiration for this tier group is Qualifying Points Reset Date."

For a fixed-model tier group, when a member is upgraded, their new tier is valid for the remainder of the current tier assessment period plus the entire next tier assessment period.

The member was upgraded on March 16, 2023.

- The current assessment period is January 1, 2023, to December 31, 2023.

- The next assessment period is January 1, 2024, to December 31, 2024.

Therefore, the member's new Gold tier will expire at the end of the next full assessment period, which is December 31, 2024.

A. December 31, 2023: This is the end of the current assessment period. The member's tier is valid for the next full period as well, not just the current one.

B. March 16, 2024: This date is one year from the upgrade date, which is the logic for an Anniversary Model tier group, not the Fixed Model specified in the scenario.

D. March 31, 2024: This date does not align with the program's annual reset date of December 31 and is not consistent with any standard tier expiration logic.

1. Salesforce Help, Loyalty Management, "How Tier Expiration Works": This document explicitly states, "For a fixed-model tier group, when a member is upgraded to a higher tier, the member’s new tier is valid for the remainder of the current tier assessment period and the entire next tier assessment period." This directly supports the calculation that leads to the December 31, 2024 expiration date.

2. Salesforce Help, Loyalty Management, "Tier Management": This guide details the setup of Tier Groups. It describes the "Tier Model" field, where administrators choose between "Fixed" and "Anniversary". The scenario's use of a "Fixed Model" with a specific reset date (December 31) is central to the correct answer, distinguishing it from anniversary-based calculations.

3. Salesforce Help, Loyalty Management, "Create a Tier Group": In the section detailing the fields for a tier group, it explains the "Tier Period" and "Qualifying Points Reset Frequency". The combination of a one-year period and a fixed reset date (Dec 31) establishes the fixed assessment periods (Jan 1 - Dec 31) used in the expiration calculation.

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).

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.