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

To configure the data page to satisfy all the requirements in the scenario:

Create a thread-level data page with parameters that uses a connector as its source (Answer B):

Explanation: A thread-level data page ensures that the data is specific to the current user session and not shared across multiple sessions. Using parameters allows for flexibility in filtering and retrieving the required transactions. The connector source ensures data is fetched from the external service as needed.

For modeling different types of vehicles in an insurance quote application:

Separate Data Types:

Create a distinct data type for each vehicle type (e.g., Car, Motorcycle, Truck). This allows for specific properties and business logic for each vehicle type.

Single Vehicle Page List:

Maintain a single page list property in the quote case type to hold vehicle details.

At runtime, dynamically identify the page class for each entry in the list based on the type of vehicle being processed. This approach allows for flexibility and maintainability.

References:

Pega Data Modeling Best Practices

Pega Case Management Guide

Criterion 1: Owns a smart mobile

Engagement Policy Level: Group level

Explanation: The criterion "Owns a smart mobile" applies to all data plans and can be considered a group-level policy. It filters the audience at a broader level to ensure they have a smart mobile device.

Criterion 2:

Under graduation student

Engagement Policy Level: Issue level

Explanation: The criterion "Under graduation student" applies to multiple data plans (1 GB and 3 GB) and is more specific to the issue of targeting educational segments. Thus, it is suitable at the issue level.

Criterion 3:

Post graduation student

Engagement Policy Level: Action level

Explanation: The criterion "Post graduation student" is specific to the 5 GB plan and is most appropriate at the action level. This level ensures the targeting is precise for this particular plan.

New customer

Engagement Policy Level: Group level

Explanation: The criterion "New customer" can be applied across multiple offers and thus is suitable for the group level to broadly target new customers.

Existing customer

Engagement Policy Level: Action level

Explanation: The criterion "Existing customer" is applied at the action level to ensure specific offers (3 GB and 5 GB plans) are appropriately targeted to customers who already have a relationship with the company.

Step by Step Comprehensive Detailed Explanation with References:

Group Level Engagement Policy:

Conditions that apply broadly across multiple offers or groups of offers fall under group-level policies. Examples include owning a smart mobile and being a new customer.

Issue Level Engagement Policy:

Conditions that are relevant to a specific issue, such as educational status for specific data plans, are categorized under issue-level policies. This ensures that offers targeting undergraduates are consistently managed.

Action Level Engagement Policy:

Conditions that are specific to individual actions or offers are best managed at the action level. This includes targeting post-graduation students for the 5 GB plan and existing customers for specific plans to ensure precise targeting.

References: Pega's best practices for engagement policies recommend using group-level policies for broad criteria, issue-level for segment-specific conditions, and action-level for highly specific targeting to ensure effective and relevant customer engagement.