Pegasystems Updated PEGACPLSA88V1 Exam Questions and Answers by kira

Next-Best-Action Reevaluation:When a customer rejects an offer, Pega Customer Decision Hub reevaluates the Next-Best-Action to determine the next most relevant action for the customer. This ensures that the customer's needs and preferences are continuously considered.

Process Steps:

Capture the rejection event.

Trigger the reevaluation process.

Determine the next best offer or action based on updated customer data and context.

References:Pega Documentation on Customer Decision Hub outlines the process of handling offer rejections and reevaluating Next-Best-Actions.

Configure Authentication Activity:

Go to Records Explorer > Security > Activities.

Create or configure the authentication activity to map the authenticated user to the operator ID in Pega.

LDAP Attributes Mapping:

Go to Designer Studio > Security > Authentication Service.

Configure the LDAP attributes to map to Pega operator properties, ensuring that attributes like cn, sn, mail, etc., are correctly mapped.

Validation:

Test the Single Sign-On (SSO) setup to ensure the authentication and attribute mappings work correctly.

Verify that users can log in using SSO and their LDAP attributes are correctly reflected in Pega.

References:

Pega Academy: Single Sign-On Configuration.

Pega Documentation: LDAP and SSO Configuration.

For U+ Bank's project to present credit card offers based on engagement policies, the conditions should be matched with the appropriate engagement policy criteria as follows:

The customer must not be flagged as a defaulted borrower

Engagement Policy: Eligibility

Explanation: This condition ensures that only customers who meet basic eligibility criteria, such as not having defaulted on previous loans, are considered for the offers.

Customer already owns a higher-value offer

Engagement Policy: Suitability

Explanation: This condition checks if the offer is suitable for the customer, ensuring that the customer does not already have a better offer, which would make the new offer irrelevant or less attractive.

Must be a resident of New York City

Engagement Policy: Applicability

Explanation: This condition pertains to the applicability of the offer, ensuring that the offer is relevant to the customer's location, which in this case is specific to residents of New York City.

The savings product offers are relevant only if the customer has not explicitly opted out of direct marketing

Engagement Policy: Eligibility

Explanation: This condition is part of the eligibility criteria, ensuring that only those customers who have not opted out of direct marketing are eligible to receive the offers.

Inappropriate for customers with a credit score < 300 as they are likely to default

Engagement Policy: Suitability

Explanation: This condition ensures the suitability of the offer, filtering out customers with a low credit score who are at a higher risk of defaulting, making them unsuitable for certain offers.

Step by Step Comprehensive Detailed Explanation with References:

Eligibility Conditions:

Conditions that determine the basic qualifications or permissions for receiving offers fall under eligibility. This includes criteria such as not being flagged as a defaulted borrower and not opting out of direct marketing.

Applicability Conditions:

Conditions that ensure the offer is applicable to the customer's specific situation or context fall under applicability. This includes location-based criteria like being a resident of New York City.

Suitability Conditions:

Conditions that determine if the offer is appropriate for the customer's current status or needs fall under suitability. This includes ensuring the customer does not already have a better offer and checking the credit score to prevent offering products to those at high risk of default.

References: According to Pega’s best practices for engagement policies, eligibility criteria are used to filter out ineligible customers, applicability ensures the offer is relevant to the customer’s situation, and suitability checks ensure the offer is appropriate for the customer’s current needs and status.

 Association Rules: Association rules in Pega are used to define relationships between different classes. By creating association rules for the set of classes used in reports, you streamline the process of joining these classes in various reports.

 Simplified Reporting: When managers create reports, they can easily include the necessary class joins by leveraging these predefined association rules, thus reducing complexity and the likelihood of errors.

References:

Pega Academy: Building Reports with Association Rules

Pega Documentation: Association Rules