Free Practice Questions for Pegasystems PEGACPLSA88V1 Exam

BIX Integration:

Use Pega's Business Intelligence Exchange (BIX) to export the Index-WorkPartyUri data. This method allows real-time data export without impacting case worker performance.

Configure BIX to export the required data to the report database at scheduled intervals.

To create custom workspaces for different user roles and display custom formatted properties:

Separate Portals and Harnesses: Define separate portals, harnesses, and sections for each access group (managers and customer service representatives). This approach allows you to tailor the user interface and functionality according to the specific needs of each role.

Specialty Components and XML: Use Specialty Components to create custom formats for properties. XML can be used to pass data in and out of these components, allowing for complex and specialized data handling.

References: Pega Platform documentation on portals, harnesses, and using Specialty Components with XML.

Security Token Identification:

Add steps in the IAC authentication activity to identify and validate the security token provided by the external module.

Token Verification:

Implement additional steps to return the security token to the external authentication module for verification, ensuring it is the authenticating source.

Circumstancing: This technique allows for creating variations of a rule based on specific conditions, such as different products, without duplicating the rule for every possible product scenario.

Rule Configuration:

Set the availability of the data transform rule to "Blocked".

Testing with Previous Versions:

This allows you to save and check in the record despite validation errors and lets previous versions of the rule execute during testing.

Limited Availability and Concurrency: This pattern handles situations where resources (like ferry seats) are limited, and concurrency needs to be managed to ensure fair allocation.

Divide and Conquer: This pattern involves breaking down a case into sub-cases or steps, such as managing bookings for both the outbound and return trips separately.

Segment:Segments are used to define high-level criteria for identifying the starting population. Conditions related to customer attributes like income and credit score are best suited for segment definitions because they help in broadly classifying customers based on these attributes.

Monthly Income: Customers with a monthly income less than 20000 can be grouped into a segment for targeted promotions.

Credit Score: Customers with a credit score higher than 200 can also be grouped into a segment to ensure that only creditworthy customers are considered for promotions.

Engagement Policy:Engagement policies are used to refine the targeting criteria further and define rules that must be met for engagement. Conditions related to customer consent and specific financial ratios are better suited for engagement policies.

Opt-in Status: Checking if the customer is opted in to receive promotional emails ensures compliance with communication preferences.

Debt to Income Ratio: A higher debt to income ratio might indicate higher financial risk, and this should be considered before engaging the customer with offers.

Opt-out Status: Ensuring customers are not opted out of receiving credit card promotions on mobile phones is crucial for effective communication and compliance with customer preferences.

References:Pega Academy modules on Segmentation and Engagement Policies provide detailed guidance on best practices for defining and using segments and engagement policies in customer decisioning.

Max Attempts: The maximum number of retry attempts set is 4.

Initial Delay: The initial delay before the first retry attempt is 2 minutes.

Delay Factor: The delay factor is set to 2, which means the delay doubles with each retry.

Calculating Delays:

First attempt fails, delay before second attempt = Initial delay = 2 minutes.

Second attempt fails, delay before third attempt = Initial delay * Delay factor = 2 minutes * 2 = 4 minutes.

Third attempt fails, delay before fourth attempt = 4 minutes * Delay factor = 4 minutes * 2 = 8 minutes.

Delay Between Attempts: The question specifically asks for the delay between the second and third attempt, which is calculated as 8 minutes.

References:

Pega documentation on queue processor configuration.

Pega Platform 8.x help files related to processing retries and delay factors.

To address difficulty in creating a customer service request through Facebook Messenger:

Change the text analyzer configured for the channel (Answer C):

Explanation: The text analyzer is responsible for interpreting user input. Improving its configuration can enhance its ability to understand and process customer requests more accurately.

Defining a case type within a case type-specific ruleset provides several advantages:

Branch Ruleset Association: By associating each branch ruleset with case-specific user stories, you can better manage development and testing. This allows for more targeted reviews and testing, ensuring that changes are isolated and easily traceable.

Component Application Conversion: If there is a possibility that the case type might be converted to a component application in the future, having a case-specific ruleset simplifies the process. It allows the case type to be more easily packaged and reused across different applications.

References: Pega Platform best practices for ruleset management and case type design.