Free Pegasystems PEGACPLSA88V1 Practice Exam with Questions & Answers | Set: 5

Graphical user interface, application Description automatically generated

When defining an embedded list property with a specific data type:

Changing pxObjClass at Runtime (A):

The pxObjClass of any page within the .Loans list can be modified at runtime. This provides flexibility to change the class of individual pages if needed.

Inheritance and Calculation (C):

Extending the data model, such as a car loan application extending MyCo-Data-Loan-Auto, does not impact aggregate functions like sum performed on properties (e.g., .Loans().Amount).

Class Consistency within the List (E):

All pages within the .Loans list must adhere to the same class type, ensuring consistency and correct behavior of operations on the list.

References:

Pega Data Modeling Guidelines

Pega Clipboard and Page Management Documentation

 Dynamic Layout: This layout allows for flexible arrangements of items within the form. It supports wrapping content based on screen size, making it ideal for responsive design.

 Row Configuration: Within a dynamic layout, elements can be configured to flow like words in a sentence, wrapping to the next line as necessary. This is essential for displaying book covers in a row that adapts to different screen widths.

 Responsive Behavior: Dynamic layouts are designed to handle varying screen sizes seamlessly, ensuring that the UI remains user-friendly on all devices.

 Reference: Pega documentation emphasizes the use of dynamic layouts for creating flexible and responsive UI designs (Pega Platform 8.7 Documentation, User Interface - Layouts).

To configure a data page that caches customer transactions and minimizes operator wait time, you should:

Set the data page scope to node to ensure that the cached data is shared among all requestors on the same node, reducing the number of times the data needs to be fetched.

Configure the refresh strategy to reload if the data is older than 1 hour, aligning with the data update frequency and ensuring that the data is not stale.

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

 Elasticsearch Query Support:

Elasticsearch queries support operations such as "Starts with", "Contains", and "Greater than", which are useful for various search and filtering needs.

 References:

Pega's use of Elasticsearch for indexing and searching data provides support for these operations to enhance report definitions.

 Therefore, the correct answers are:

A. Starts with

B. Contains

E. Greater than

To restrict the ability to withdraw a case to specific users, the following rule types can be used in combination:

Access When (Answer B):

Explanation: An Access When rule can be created to conditionally grant or deny access to the withdraw action based on the user's role and whether they are the creator of the case or a work group manager.

Continuous integration (CI) is a DevOps practice where developers frequently merge their code changes into a central repository, followed by automated builds and tests. The primary goal is to detect and address integration issues early.

Leveraging release toggles (Answer B):

Explanation: Release toggles (or feature toggles) are a technique to enable or disable features within a software application without deploying new code. This allows teams to integrate new features incrementally and safely, supporting continuous integration and delivery.

 Defining Greetings: In Pega, create two separate greeting messages, one for satisfied customers and one for unsatisfied customers. Each greeting should be tailored to address the specific sentiment of the customer.

 Applying When Rule: A When rule is used to conditionally execute actions based on certain criteria. Create a When rule that evaluates the customer's satisfaction status. This can be based on data points such as customer feedback scores, recent interaction history, or sentiment analysis results from their messages.

 Configuring the Response: In the process configuration for handling Facebook Messenger interactions, apply the When rule to decide which greeting message to send. This ensures that when a customer initiates a conversation, the system checks their satisfaction status and responds with the appropriate greeting.

References:

Pega Academy: Configuring Chatbots and Virtual Assistants

Pega Documentation: Using When Rules

To extend the Pega Foundation for Healthcare (PFH) data model:

Direct Inheritance for Extension (B):

Use direct inheritance to extend the foundation data model provided by PFH. This ensures that the core data model remains intact while allowing for the addition of new fields and data classes specific to the company's needs.

Pattern Inheritance for Behavior (B):

Utilize pattern inheritance to extend application-specific behavior. This allows for customization and the addition of application-specific logic while maintaining a clear separation from the core data model.

References:

Pega Foundation for Healthcare Implementation Guide

Pega Inheritance Models Documentation