PEGACPLSA88V1 Exam Dumps - Certified Pega Lead System Architect (CPLSA) Exam 8.8

To ensure basic functionality behaves as expected before inviting users to start acceptance testing after importing a Rule-Admin-Product (RAP) file:

Create a regression test suite. Run the test suite using the automation server (Answer D):

Explanation: A regression test suite helps verify that the new features do not break existing functionality. Running these tests using an automation server ensures that the process is repeatable, reliable, and efficient.

Use PR cipherGenerator:

Utilize the PR cipherGenerator tool to generate an encrypted password.

This can be done through Pega's utility tools or via command line.

Encrypt Password:

Replace the unencrypted password in the prconfig.xml file with the generated encrypted password.

Configuration:

Ensure that the encrypted password is correctly referenced in the connection information within prconfig.xml.

References:

Pega Academy: Configuration and Deployment.

Pega Documentation: Encrypting Passwords and PR cipherGenerator.

Check Weighted Conditions:

Ensure that the combined weights of the conditions meet or exceed the threshold set for identifying duplicates. This can be done in the Duplicate Search settings.

Verify Basic Conditions:

Confirm that each of the basic conditions (non-weighted) are met for the cases being compared. If these conditions are not satisfied, the duplicate search will not proceed to evaluate the weighted conditions.

Configuration Review:

Review the configuration of the duplicate search rule to ensure it is correctly set up and that the property values being compared are correct.

References:

Pega Academy: Case Management and Duplicate Detection.

Pega Documentation: Configuring Duplicate Case Search Rules.

Based on the volume constraints and the outbound customer segment order, let's analyze the configuration:

Volume Constraints:

Channel Constraint: SMS has a maximum limit of 2.

Action Constraint: Silver card has a maximum limit of 1.

Customer Interaction Order:

CUST-01: Action - Gold Card, Channel - Push (No constraint limits reached)

CUST-02: Action - Gold Card (Email), Silver Card (Push)

Gold Card via Email: No constraints.

Silver Card via Push: Hits the Silver card constraint (1/1).

CUST-03: Action - Platinum Card (Email), Diamond Card (SMS)

Platinum Card via Email: No constraints.

Diamond Card via SMS: SMS limit not yet reached (1/2).

CUST-04: Action - Diamond Card (Direct Mail)

Diamond Card via Direct Mail: No constraints.

CUST-05: Action - Silver Card (SMS), Diamond Card (Push)

Silver Card via SMS: SMS limit reached (2/2) and Silver card constraint already hit.

Diamond Card via Push: No action constraints remaining for Diamond Card in Push.

Since both SMS channel limit and Silver card constraint are reached by the time CUST-05 is processed, no offers are left to be applied to CUST-05.

References: Pega Documentation on Volume Constraints

ï‚· Next-Best-Action (NBA): This concept in Pega Customer Decision Hub involves recommending the best possible action for each customer interaction, which often includes decisions in customer service, marketing, sales, and risk management.

ï‚· Loan Decision: NBA is frequently applied in financial services to determine creditworthiness and loan approval, leveraging predictive analytics and customer data to make informed decisions.

ï‚· Reference: Pega Customer Decision Hub documentation outlines the application of NBA in making critical customer decisions, such as loan approvals, to enhance customer experience and operational efficiency (Pega Customer Decision Hub Documentation, Decision Strategies).