Salesforce-Loyalty-Management Practice Test

Explanation: To associate the new products with their respective partners within the loyalty partner product section, the Administrator should take two steps. For the Chocolate cookies linked with the snack category, the Administrator should add the partner in the Lookup on the Chocolate cookie product. This directly associates the product with the specific partner responsible for the snack category.
Similarly, for the Green soda from the beverage importer, the Administrator should choose the ‘Product’ option and map the Green soda to the partner. This step ensures that the beverage product is correctly associated with the beverage importer, maintaining accurate and organized tracking of partner products within the Loyalty Program. These configurations facilitate seamless management and representation of partner products within the program, enhancing the clarity and efficiency of partner product associations.

Explanation: Customer support agents can manually adjust points for Loyalty Program Members on the following pages:
Loyalty Program Member page (A): This is the primary interface for viewing and managing individual loyalty program members, including adjusting their points as needed. Loyalty Program Member Related List (B): This related list, found on related records such as accounts or contacts, provides access to loyalty program member information, including point adjustments.
Transaction Journal (C): The Transaction Journal records all point transactions forloyalty program members, allowing customer support agents to make manual adjustments to points as necessary. Options D (Account page) and E (Contact page) may provide indirect access to loyalty program member information but are not the primary interfaces for adjusting loyalty program points. Salesforce documentation on Loyalty Management would detail the interfaces and processes for managing loyalty program members' points, including the roles and permissions required for customer support agents to make adjustments.

Explanation: To enable users to access a new analytics app, it's crucial to assign them the appropriate roles and permission sets. Assigning user access to the analytics for Loyalty role ensures that users are granted the necessary permissions to view and interact with the Loyalty analytics content. This role is designed to encompass the permissions required for accessing and analyzing Loyalty-specific data.
Additionally, assigning user access to permission sets for analytics for Loyalty is an effective way to provide access. Permission sets offer a flexible and granular approach to managing user permissions, allowing Administrators to specify the exact capabilities each user should have within the analytics app. This method ensures that users have access to the appropriate analytics tools and data relevant to their roles and responsibilities within the Loyalty program.

Explanation: In Salesforce Loyalty Management, member engagement attributes are used to track and reward customer behaviors that are not directly tied to transactions. In the scenarios provided:
Member is eligible for ‘Bonus days” if the member constantly spends more than $500 each month for a year (A): This scenario is ideal for using member engagement attributes to track consistent high spending over a year. The attributes can be used to monitor monthly spending and, once the criteria are met, trigger the bonus days reward.
Member attends three trainings between March 1st and April 30th to get 200 bonus points (B): This is another perfect use case for member engagement attributes. The attributes can be set to track participation in specific events (like training sessions) and award points when the member meets the attendance requirement.
Member buys apparel online and gets 400 bonus points if the member belongs to Gold Tier only (C): This scenario is more about transactional behavior combined with tier status, which might not necessarily require the use of engagement attributes. Instead, this could be managed through regular transactional rules and tier benefits.
Member enrolls in “welcome aboard” promotion for free surprise gift every quarter (D): While engagement attributes could potentially track enrollment in promotions, this scenario seems more straightforward and could be managed through the promotion and voucher functionalities in Salesforce Loyalty Management without the need for engagement attributes.
Engagement attributes are particularly useful for tracking non-purchase behaviors and engagements, providing a flexible tool to reward members for a wide range of activities, enhancing their loyalty and engagement with the program. The Salesforce Loyalty Management documentation provides extensive guidance on configuring and using member engagement attributes effectively.

Explanation: For integrating a custom object "Member TierUpdate_c" with a journey in Salesforce Marketing Cloud for real-time tier change notifications, the correct data source option is:
Option D "Salesforce Data" as the Entry Source, with the custom object "Member TierUpdate_c" as the data source. This option allows for real-time triggering of journeys in Marketing Cloud based on updates to Salesforce records, in this case, the "Member TierUpdate_c" object which tracks tier upgrades.
Options A and B do not correctly target the custom object designed to track tier changes.
Option C, using a "Data-Extension," would not provide the real-time integration needed for immediate email notifications upon tier changes.