Get Pegasystems PEGAPCBA87V1 Exam Dumps

Answer : A, B

These answers are correct because they prevent the accident claim case from resolving before all vehicle claims are resolved, as per the requirement. By adding each vehicle claim as a child case of the accident claim, you can create a case hierarchy that allows you to manage related cases together. By adding a wait step to the accident claim case, you can pause the parent case until all child cases reach a specific status, such as Resolved. Reference: https://academy.pega.com/library/87/pega-certified-business-architect-pcba-87v1 (Module 5: Case Hierarchy)

Answer : B, D, E

The three options that are application layers in the Situational Layer Cake architecture are implementation, division, and organization. The implementation layer contains the case types and data types that are specific to a single implementation of an application. The division layer contains the rules and data that are shared by multiple implementations within a division or a business unit. The organization layer contains the rules and data that are common across the entire organization or enterprise. Reference: https://community.pega.com/knowledgebase/articles/application-development/86/application-layers

Answer : A, C, E

The three roles that you invite to the DCO sessions are product owner, subject matter experts, and system architect. The product owner is the primary stakeholder who represents the business vision and priorities for the application. The subject matter experts are the users or customers who provide input and feedback on the application requirements and functionality. The system architect is the technical lead who designs and builds the application using Pega Platform. Reference: https://academy.pega.com/library/81/pega-certified-business-architect-pcba-81

Answer : A, B, E

The three pillars that are used to capture information for the release are personas and channels, data and interfaces, and micro journeys. Personas and channels define who uses the application and how they access it. Data and interfaces define what information is stored and displayed in the application. Micro journeys define how users achieve their goals and outcomes in the application. Reference: https://academy.pega.com/library/81/pega-certified-business-architect-pcba-81

Answer : A, B, C

A user story is a concise description of a feature or functionality that a user wants to achieve in an application. A good user story has three characteristics: it can be tested, it reflects the business value the client receives, and it is easy to understand. It can be tested means that the user story has clear and measurable acceptance criteria that verify whether it meets the user's expectations. It reflects the business value the client receives means that the user story explains why the feature or functionality is important or beneficial for the user or the business outcome. It is easy to understand means that the user story uses simple and consistent language that avoids technical jargon or ambiguity. Reference: https://academy.pega.com/library/81/pega-certified-business-architect-pcba-81