Explanation: To analyze the performance of the Loyalty Program, a System Administrator needs the 'Loyalty Analytics User' permission. This permission set grants access to the analytics and reporting features within Salesforce Loyalty Management, allowing the administrator to customize, view, and analyze data related to the loyalty program's performance, member engagement, and other key metrics.

Explanation:

✅ Correct Option:
A. Loyalty Program Member page. This is the primary record page for a member in the loyalty program. It contains a dedicated "Points" component with an "Adjust Points" button. This allows agents to directly add or remove points from the member's balance, providing a clear audit trail linked to the specific member.

✅ Correct Option:
B. Loyalty Program Member Related List. The Loyalty Program Member object is a related list on both the Account and Contact pages. Agents can click into a member's name from this related list, which navigates them to the full Loyalty Program Member page (Option A), where they can then perform the points adjustment.

✅ Correct Option:
C. Transaction Journal. The Transaction Journal tab provides a global view of all point transactions. From this page, agents can click "New" to create a manual transaction entry. They can select a member and specify an adjustment type (e.g., "Manual Adjustment") to add or subtract points, making it a central hub for all point movements.

❌ Incorrect Option:
D. Account page. While the Account page hosts the Loyalty Program Member related list (Option B), there is no direct "Adjust Points" button on the Account page itself. The adjustment action must be performed either on the individual member record accessed via the related list or through the Transaction Journal.

❌ Incorrect Option:
E. Contact page. Similar to the Account page, the Contact page contains the Loyalty Program Member related list but does not have a native function to adjust points directly on the page. The action is performed on the subsequent Loyalty Program Member record or via the Transaction Journal.

📌 Summary:
Agents can manually adjust points from three key locations: the primary member record page (A), by accessing that record from its placement on Account/Contact pages (B), or through the central ledger system that logs all point transactions (C). The standard Account and Contact pages themselves do not contain the direct functionality to adjust points.

🔗 Reference:
Salesforce Help: Adjust Points

Explanation: To edit Loyalty Management objects, the "Loyalty Management" permission set license is required. This license grants users the necessary permissions to access and modify Loyalty Management-specific data and configurations.
Option B "Loyalty Management" is the correct answer as it directly relates to the permissions needed to work with Loyalty Program configurations and objects within Salesforce.
Options A, C, and D pertain to analytics and data pipeline functionalities and do not grant permissions to edit Loyalty Management objects.
Reference: Salesforce Help Documentation, specifically the section on Loyalty Management, outlines the required permission set licenses for different functionalities within Loyalty Management.

Explanation

To offer a 10% discount to loyalty members, the consultant must first define the reward itself, which is a voucher representing the discount. Next, a Promotion is required to define the rules (for loyalty members, during the summer sale) that determine when that specific discount voucher is issued to the qualifying member. This uses two key components within the Loyalty Management architecture.

✅ Correct Option: B & D

B. Create within the Loyalty Experiences tab a new promotion for the Summer Sales campaign where the Loyalty Promotion Type is Standard and the Fulfillment Action is Issue Voucher.
A Promotion record is the mechanism that defines the rules for giving out rewards.
Loyalty Promotion Type: Standard is used for basic, non-tier-related promotions.
The Fulfillment Action: Issue Voucher tells the system that when a member qualifies for this promotion, they should receive the associated discount voucher. This links the rules to the reward.

D. Create within the Loyalty Experience tab a new voucher tab a new voucher definition where the Type Is Discount Percentage and the Expiration Type is fixed Date.
The Voucher Definition defines the specific reward being given.
Type is Discount Percentage is required to represent the 10% discount NTO wants to offer.
The Expiration Type is Fixed Date ensures the voucher can only be used during the annual summer sale period, making the discount exclusive to that event.

❌ Incorrect Options

A. Create within the Loyalty Experiences tab a new voucher definition for the summer sales campaign where the Type is Product or Service and the expiration Type is fixed Date.
Using Type: Product or Service is incorrect. This type is used when the reward is a physical item or service (like a free hat or free shipping). Since NTO is offering a 10% discount, the correct voucher type must be Discount Percentage (Option D).

C. Create within the Loyalty Experiences tab a new Benefit Type for the Summer sale campaign where the Benefit Type Name is standard and the Category type is Issue Voucher.
Benefit Type is used to categorize and track the high-level kinds of rewards offered (e.g., 'Discount', 'Free Shipping'). It is a general setup component and is not the operational record used to define the specific rules or the reward value itself. The promotion (Option B) and the voucher definition (Option D) are the correct operational records.

🔗 Reference
Salesforce Help: Create a Voucher Definition (Details on setting the voucher type to 'Discount Percentage'.)
Salesforce Help: Create a Loyalty Promotion (Details on setting the Promotion Type and the Fulfillment Action to 'Issue Voucher'.)

Explanation:

To connect Salesforce Loyalty Management with Marketing Cloud, a Consultant must ensure that the Marketing Cloud user account has the correct permissions and technical capabilities. The integration relies on secure API communication and proper access to the Marketing Cloud Business Unit (BU) used for loyalty campaigns, journeys, and messaging. Without these settings, the connection handshake and authentication will fail, preventing the systems from syncing data.

Correct Options:

✅ B. Grant access to the correct business unit
The user must have access to the specific Marketing Cloud Business Unit that will store and process loyalty-related data.
This ensures that the integration can interact with the correct data extensions, journeys, and assets.
Misaligned business unit access often results in connection failures or missing data visibility.

✅ D. API access
API access is required for server-to-server authentication between Salesforce Loyalty Management and Marketing Cloud.
Without API permissions, the system cannot generate, send, or receive data.
This is essential for syncing members, points, vouchers, and triggered sends between platforms.

Incorrect Options:

❌ A. User account must exist within the Loyalty Management org
Marketing Cloud and Loyalty Management operate on different platforms, so the Marketing Cloud user does not need an account inside the Salesforce org. The connection is established via API integration, not shared user identities. This requirement does not impact the integration setup.

❌ C. Assign the permission set to the user account
Permission sets apply to Salesforce CRM/Loyalty users, not Marketing Cloud users. Marketing Cloud uses roles and permissions, not Salesforce permission sets. Assigning a Salesforce permission set has no effect on the Marketing Cloud user’s ability to connect via API.

Summary:
To enable integration between Salesforce Loyalty Management and Marketing Cloud, the Consultant must configure Business Unit access and API access for the Marketing Cloud user. Other options do not influence the connection process.

Reference:
Salesforce Help — Connect Marketing Cloud to Salesforce