PEGAPCBA87V1 Exam Dumps - Pegasystems CPBA Questions and Answers

This answer is correct because it sets the maximum time allowed for resolving a medical claim case, as per the requirement. The deadline in the service level defines the time limit for completing a case or an assignment. If the deadline is reached, an escalation action can be triggered to notify or reassign the case or assignment. References: https://academy.pega.com/library/87/pega-certified-business-architect-pcba-87v1 (Module 6: Service Levels)

 it provides users with guidance for completing a form and avoids the need for application training. An instruction is a short text that appears above a form and explains what the user needs to do to complete the task. An instruction can help users understand the purpose and context of a form and reduce errors or confusion. References: https://academy.pega.com/library/87/pega-certified-business-architect-pcba-87v1 (Module 9: User Interface)

A Pega Business Architect is expected to help to refine ahead of a sprint by applying design thinking and the Pega Express methodology to define the right scope and yield faster business results. A Pega Business Architect also facilitates discussions and drives decision making with stakeholders and subject matter experts using Pega tools and best practices. References: https://community.pega.com/roles/business-architect

To satisfy this user story, you need to add a case wide action to the case workflow. A case wide action is an action that users can perform at any point in the case life cycle, regardless of their current stage or assignment status. You can add a case wide action to allow users to cancel an open service request at any time and resolve the case accordingly. References: https://community.pega.com/knowledgebase/articles/case-management/86/configuring-case-wide-actions

it fetches exchange rates that are updated on a daily basis from a web service and makes them available in your application using a data page. A request scope for a data page means that the data page is loaded once per user session and is refreshed when the user logs out and logs back in. This way, the data page can provide the most up-to-date exchange rates for each user session. References: https://academy.pega.com/library/87/pega-certified-business-architect-pcba-87v1 (Module 10: Data Pages)

Using the Pega Express delivery approach, governance is established during the prepare phase of the project. The prepare phase involves setting up the project team, roles, responsibilities, tools, processes, and standards that will guide the project delivery. Governance ensures that the project is aligned with the business objectives, follows best practices, meets quality criteria, and delivers value to the stakeholders. References: https://community.pega.com/knowledgebase/articles/pega-express-methodology/86/prepare-phase

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. References: https://academy.pega.com/library/81/pega-certified-business-architect-pcba-81

To satisfy this requirement, you need to create a service level that specifies both A and B options. A service level is a rule that defines time intervals and actions for completing an assignment or resolving a case. A service level has two components: goal and deadline. The goal defines when an assignment or case should be completed ideally, while the deadline defines when an assignment or case must be completed at latest. You can also configure actions to perform at each component, such as sending notifications, escalating urgency, etc. References: https://community.pega.com/knowledgebase/articles/case-management/86/configuring-service-levels

These answers are correct because they achieve the behavior of creating a case ID only when the customer chooses to make changes to their membership. Temporary cases are cases that are not stored in the database until a Persist case step is reached in the case life cycle. This way, the case can be abandoned without creating any records or consuming any resources. References: https://academy.pega.com/library/87/pega-certified-business-architect-pcba-87v1 (Module 4: Case Design)

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. References: https://academy.pega.com/library/81/pega-certified-business-architect-pcba-81