PEGACPBA88V1 Certified Pega Business Architect 8.8 Questions and Answers

The name of Pega's business architecture design that aligns human intelligence and process automation with business logic to deliver high-value software solutions is Center-out.

Center-out Design:

This approach focuses on designing the core business logic and processes first (the "center") and then extending outwards to include the user interface (UI) and channels.

By centering on the core logic, Pega ensures that the most critical aspects of the business process are well-defined and robust. This approach supports scalability and adaptability as the system grows and evolves.

References:

Pega Academy: Center-out Business Architecture

Pega Documentation: Center-out Design Principles

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.

Import stories: When populating the backlog directly from a spreadsheet, the correct approach is to import the stories. Pega allows for importing user stories from spreadsheets to efficiently populate the backlog.

 A sales representative wants to quote the cost of an insurance policy based on selected coverage options: Calculated fields can dynamically determine the cost based on selected options.

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.

 MLP sizing leads to more precise resource planning: Proper sizing of the MLP ensures that resource planning is accurate, allowing the team to allocate the necessary resources effectively to meet the delivery timelines.

Property reference: .Address(1).PostalCodeField type: Single record data relationship

Property reference: .ShippingAddress.CityField type: Text

Property reference: .BillingAddress.TelephoneField type: Multiple record data relationship

Property reference: .Address(1).PostalCode

Field type: Single record data relationship

Explanation: The .Address(1).PostalCode property indicates a specific postal code within a single address. The (1) suggests it’s part of an indexed or paged list, but each PostalCode is a single entity within that address record.

The basic condition for identifying duplicate cases, such as IT tickets for the same issue, is to check if the issue type is the same. By configuring the Search duplicate cases step to identify cases where the issue type is the same, you can effectively identify and manage duplicate IT tickets related to common problems like "the office Wi-Fi is down."

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.

MLP sizing leads to more precise resource planning: Accurate sizing of the MLP helps in precise allocation and planning of resources, ensuring that the team can deliver the required functionality within the defined time frame.

As a project nears the end of the Prepare phase, the project plan should include:

B. Epics and user stories:

These are essential for defining the work to be done in future sprints. They provide detailed descriptions of the functionality and requirements that need to be developed and tested.

C. RAID log (Risks, Actions, Issues, and Decisions):

This log is critical for tracking potential risks, ongoing actions, issues that need resolution, and decisions made during the project. It helps in managing and mitigating risks and ensures that the project stays on track.

References:

Pega Academy: Project Planning and Management

Pega Documentation: Prepare Phase Activities and Deliverables

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.

Responsive Breakpoints: These are used to adapt the UI layout for different screen sizes, ensuring a good user experience on all devices.

References:

Pega Academy: Responsive UI Design

Pega Documentation: Configuring Responsive Breakpoints in App Studio