PEGACPBA88V1 Practice Questions

For an application to process a new customer loyalty account with data stored in a data relationship

with an external data source, you should create a data reference field.

Data Reference Field: This field type allows the application to reference and use data from an

external source without embedding it directly within the case. This is suitable for maintaining up-to-

date information and integrating with external systems.

Reference:

Pega Academy: Data Management

Pega Documentation: Data Relationships and Integration

Field: Total hours for each type of time tracked (work, vacation, sick)

Method: Calculation

Field: Cumulative total of all hours for the week

Method: Calculation

Field: Updated vacation and sick time balances

Method: Data transform

Total hours for each type of time tracked (work, vacation, sick)

Method: Calculation

Explanation: The total hours for each type of time (work, vacation, sick) are derived by summing up

the respective hours entered by the employee for each day. This involves simple arithmetic

operations which are best handled by a calculation rule in Pega.

Reference: Pega Platform Business Architect Essentials, Chapter on Calculations and Decision Rules.

Cumulative total of all hours for the week

Method: Calculation

Explanation: The cumulative total of all hours for the week is computed by summing up the total

hours of work, vacation, and sick time. This is another straightforward arithmetic operation that

should be implemented using a calculation rule.

Reference: Pega Platform Business Architect Essentials, Chapter on Calculations and Decision Rules.

Updated vacation and sick time balances

Method: Data transform

Explanation: When the employee submits the timesheet, the application needs to update the

vacation and sick time balances by subtracting the entered hours from the available balances. This

involves data manipulation which is appropriately handled using a data transform. Data transforms in

Pega are used to copy and manipulate data.

Reference: Pega Platform Business Architect Essentials, Chapter on Data Transforms and Activities.

To match the reports to the correct report types:

Average duration and timeliness per assignment:

Report Type: Process Report

Total customer inquiry cases per state per product line:

Report Type: Business Report

Explanation:

Process Reports: Focus on process metrics like the duration and timeliness of assignments.

Business Reports: Focus on business metrics like customer inquiries segmented by state and product

line.

Reference:

Pega Academy: Reporting and Analytics

Pega Documentation: Types of Reports

Order of Events:

A user clicks the button.

The system applies a data transform.

The order ID value is set to the value of the confirmation number if the system confirms the

payment.

The system refreshes the section.

 A user clicks the button.

Explanation: The event sequence starts when the user interacts with the button by clicking it. This is

the trigger for the subsequent actions.

Reference: Pega Platform Business Architect Essentials, Chapter on User Interface.

 The system applies a data transform.

Explanation: After the button click, the specified data transform (SetDefaultValues) is executed. Data

transforms are used to manipulate data, such as setting default values or copying data from one

location to another.

Reference: Pega Platform Business Architect Essentials, Chapter on Data Transforms.

 The order ID value is set to the value of the confirmation number if the system confirms the

payment.

Explanation: Following the data transform, the system checks the condition (When Rule:

PaymentConfirmed). If this condition is true, the system sets the .Order.OrderID property to the

.ConfirmationNumber value.

Reference: Pega Platform Business Architect Essentials, Chapter on Conditional Processing.

 The system refreshes the section.

Explanation: Finally, the section is refreshed to reflect any changes made during the previous steps.

This ensures the user interface is updated with the latest data.

Reference: Pega Platform Business Architect Essentials, Chapter on User Interface and Dynamic UI

Updates.

Process Step Description: "A user enters information for a car reservation request."

Process Step: Collect Information

Process Step Description: "The system evaluates the request type to determine the next step."

Process Step: Decision

Process Step Description: "A manager determines whether to approve or reject a timesheet."

Process Step: Approval

Process Step Description: "The system notifies the user of the case status by email."

Process Step: Automation

A user enters information for a car reservation request.

Process Step: Collect Information

Explanation: This step involves gathering data from the user. In Pega, collecting information typically

involves prompting the user to enter necessary details to move the case forward.

Reference: Pega Platform Business Architect Essentials, Chapter on Data Collection.

The system evaluates the request type to determine the next step.

Process Step: Decision

Explanation: This step involves the system making a determination based on the provided

information. A decision step in Pega is used to evaluate conditions and determine the next path or

action in the case workflow.

Reference: Pega Platform Business Architect Essentials, Chapter on Decision Management.

A manager determines whether to approve or reject a timesheet.

Process Step: Approval

Explanation: This step is about reviewing and making an approval decision. In Pega, approval steps

are used when a human needs to review the case and make a decision to approve or reject it.

Reference: Pega Platform Business Architect Essentials, Chapter on Case Life Cycle Management.

The system notifies the user of the case status by email.

Process Step: Automation

Explanation: This step involves automated communication. Automation steps in Pega can be

configured to perform tasks like sending emails, updating records, or other system actions without

manual intervention.

Reference: Pega Platform Business Architect Essentials, Chapter on Notifications and

Correspondence.

Use Case: "A medical specialist completes their review of an insurance claim, and the system

attaches the report to the case."

Automation: Create PDF

Use Case: "Employees of a financial services firm receive confirmation when they register for the

required certification classes."

Automation: Send email

Use Case: "A Fraud department manager receives a mobile notification that an approval request is in

their worklist."

Automation: Push notification

Use Case: "When an approver rejects an expense report, an employee can modify and resend the

report for approval."

Automation: Change to a stage

 A medical specialist completes their review of an insurance claim, and the system attaches the

report to the case.

Automation: Create PDF

Explanation: In this use case, the system needs to generate a report that can be attached to the case.

The appropriate automation for generating documents like reports is creating a PDF. This ensures the

report is in a standardized, non-editable format that can be easily attached to the case.

Reference: Pega Platform Business Architect Essentials, Chapter on Case Design.

 Employees of a financial services firm receive confirmation when they register for the required

certification classes.

Automation: Send email

Explanation: This use case involves sending a confirmation to employees upon registration. The most

suitable method for sending such confirmations is through an email. Email notifications ensure that

the employee receives a record of their registration.

Reference: Pega Platform Business Architect Essentials, Chapter on Notifications and

Correspondence.

 A Fraud department manager receives a mobile notification that an approval request is in their

worklist.

Automation: Push notification

Explanation: The manager needs to be alerted promptly about an approval request. Push

notifications are ideal for this purpose as they provide real-time alerts directly to the mobile device.

Reference: Pega Platform Business Architect Essentials, Chapter on Mobile and Multi-Channel.

 When an approver rejects an expense report, an employee can modify and resend the report for

approval.

Automation: Change to a stage

Explanation: When an expense report is rejected, the case needs to move back to a stage where the

employee can modify and resubmit it. This involves changing the stage of the case to enable the

necessary actions.

Reference: Pega Platform Business Architect Essentials, Chapter on Case Management and Workflow.

Two statements about insights are true:

B . You can search for and select the fields that you want to include in an insight. This allows for

customized data visualizations based on selected fields.

C . You can transform data queries into sharable visualizations, making it easy to share insights with

others in the organization.

Reference:

Pega Academy: Insights and Data Visualization

Pega Documentation: Creating and Sharing Insights

To route cases to specific loan officers based on loan type using business logic, the following steps are

typically used in Pega:

Use Decision Rules: Define a decision table or decision tree that maps loan types to specific operators

(loan officers).

Configure Routing in the Flow: In the flow rule, configure the assignment shape to use the decision

rule to determine the routing based on the loan type.

Route to Operator: Use the "To Operator" routing option, and apply the decision logic to dynamically

determine the operator (loan officer).

In this case:

For mortgage loans, the decision rule routes the case to Adam Ross.

For automobile loans, the decision rule routes the case to Julia Samuels.

For equity line loans, the decision rule routes the case to Don Smith.

Reference:

Pega Academy: Assignments and Routing

Pega Decision Management: Using Business Logic for Routing

Use a visibility condition on the mobile phone number field to determine whether to show the field:

In Pega, visibility conditions are used to control the display of UI elements based on specific

conditions. In this case, you would configure the visibility condition on the mobile phone number

field to display it only when the checkbox for subscribing to the text messaging service is selected.

Reference: Pega Academy, User Interface Design, Visibility Conditions.

The statement that is true about responsive breakpoints is:

C . Custom responsive breakpoints are configured in App Studio. This allows you to define how the UI

behaves at different screen sizes.

Explanation:

Responsive Breakpoints: These are used to adapt the UI layout for different screen sizes, ensuring a

good user experience on all devices.

Reference:

Pega Academy: Responsive UI Design

Pega Documentation: Configuring Responsive Breakpoints in App Studio