CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. Pegasystems
  5. PEGACPBA88V1

Free PEGACPBA88V1 Exam Braindumps (page: 6)

Page 5 of 14
PDF with 50 Questions

The business process for an automobile insurance claim consists of the following phases:
· Submission: The customer contacts a customer service representative (CSR) to file the claim. · Review: An adjuster reviews the claim, assesses the damages to each vehicle, and provides an estimate of the cost of repairs.
· Repair: A third party performs the repairs on each vehicle, communicating with the adjuster and customer as necessary.
· Verification: After each vehicle repair, the adjuster closes the claim. According to Pega best practices, which phase can you implement as a child case?

  1. Verification
  2. Submission
  3. Review
  4. Repair

Answer(s): D

Explanation:

Submission: This phase involves the initial contact and filing of the claim, which typically doesn't need to be a separate case as it's an initial action.


Reference:

Pega Academy, Case Management Essentials, Case Lifecycle Design. Review: This phase involves an adjuster reviewing the claim and assessing damages, which can be handled within the primary case.
Pega Academy, Case Management Essentials, Case Lifecycle Design. Repair: The repair phase involves interaction with third-party vendors and ongoing communication, making it suitable to be implemented as a child case to track each repair separately.
Pega Academy, Case Management Essentials, Child Cases. Verification: This phase is a closing action performed after repairs, which doesn't typically require a separate case.

Pega Academy, Case Management Essentials, Case Lifecycle Design.



DRAG DROP (Drag and Drop is not supported)
Select each Process Step Description on the left and drag it to the appropriate Process Step on the right.

  1. See Explanation section for answer.

Answer(s): A

Explanation:

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.



Your client is planning their next Minimum Lovable Product (MLP) release.
Which three pillars of case design must the Pega Business Architect ensure are taken into account, to capture information for the release? (Choose Three)

  1. Personas and Channels
  2. Reports
  3. Case types
  4. Data and Interfaces
  5. Dashboards

Answer(s): A,C,D

Explanation:

When planning the next Minimum Lovable Product (MLP) release, a Pega Business Architect should focus on the three pillars of case design: Personas and Channels, Case Types, and Data and Interfaces.
Personas and Channels:
Personas: Identify the different user roles (personas) that will interact with the application. Understanding personas helps in designing user experiences that meet their needs. Channels: Determine the channels (e.g., web, mobile) through which users will interact with the system. This ensures that the application is accessible and user-friendly across different platforms.
Case Types:
Case Types: Define the different types of cases that the application will manage. Case types are fundamental to structuring the application and ensuring that it can handle various processes and workflows efficiently.
Data and Interfaces:
Data: Identify the data required to support the case types and processes. This includes understanding data sources, data structures, and how data will be captured and used. Interfaces: Determine the interfaces needed to integrate with external systems. Interfaces are crucial for ensuring that the application can interact with other systems and exchange information seamlessly.


Reference:

Pega Academy: Case Design
Pega Documentation: Minimum Lovable Product (MLP)



Identify the name of Pega's business architecture design that aligns human intelligence and process automation with business logic to deliver high-value software solitons.

  1. Center-out
  2. Customer-centric
  3. Business-first
  4. Pega Express

Answer(s): A

Explanation:

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.


Reference:

Pega Academy: Center-out Business Architecture
Pega Documentation: Center-out Design Principles






Post your Comments and Discuss Pegasystems PEGACPBA88V1 exam with other Community members:

PEGACPBA88V1 Discussions & Posts