Pegasystems Updated PEGACPLSA88V1 Exam Questions and Answers by dana

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.

To troubleshoot chronic performance issues in a cloud-based production application, you can use the following techniques:

Performance Alerts and Exceptions in PDC: Review the alerts and exceptions in Pega Predictive Diagnostic Cloud (PDC). PDC provides real-time monitoring and insights into performance issues.

Performance Alerts and Exceptions using PLA: Use the Pega Log Analyzer (PLA) to review alerts and exceptions. PLA helps in identifying and diagnosing performance bottlenecks by analyzing log files.

References:

Pega Predictive Diagnostic Cloud (PDC)

Pega Log Analyzer (PLA)

To address the requirement of handling tasks from both Pega and non-Pega applications seamlessly, the best approach is:

Pega Process Fabric Hub (B):

Pega Process Fabric Hub integrates multiple applications, whether they are Pega or non-Pega, providing a unified view of work. It allows users to manage tasks from different systems in a single interface, avoiding the need to switch between applications.

This approach supports a unified worklist, enhancing productivity and user experience by consolidating tasks into a single accessible place.

References:

Pega Process Fabric Hub Overview

To ensure that every attempt by a developer to check a rule into a certain ruleset version is reviewed before that rule is allowed to be checked in:

C. Override the FindReviewers decision tree to invoke a when rule that evaluates the criteria, if the when rule returns true, the decision tree returns SendBack.

By overriding the FindReviewers decision tree and incorporating a when rule, you can enforce criteria such as complete history tab fields and justified warnings. If the criteria are not met, the decision tree returns SendBack, preventing the rule from being checked in.

References:

Pega Documentation on Rule Check-In: Rule Check-In

Pega Documentation on Decision Trees: Decision Trees