PEGAPCBA87V1 Pega Certified Business Architect (PCBA) 87V1 Questions and Answers

it allows the parent case to continue before the child cases resolve, as per the requirement. The Wait step can be configured to resume the parent case when a specific status is reached in the child cases, such as payment pending review. This way, the parent case does not have to wait for the child cases to be fully resolved. References: https://academy.pega.com/library/87/pega-certified-business-architect-pcba-87v1 (Module 5: Case Hierarchy)

The logic statement A returns the correct subset of transaction disputes because it filters the cases by the vendor name (F1 or F2), the transaction amount (F3 or F4), and the dispute reason (F5). The parentheses indicate the order of operations and the AND and OR operators combine the conditions. The logic statement A can be read as follows: Return the cases where (the vendor is MaxValu and the amount is greater than or equal to 25) OR (the vendor is MegaMart and the amount is greater than or equal to 50) AND (the dispute reason is stolen card). References: https://community.pega.com/knowledgebase/articles/reporting/86/filtering-data-reports

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

Before you add fields to a view, you need to decide how users enter values into the field and whether the fields require a data source. These decisions determine the type and configuration of the fields that you add to the view. For example, you can use different types of controls to allow users to enter values in different ways, such as text inputs, drop-down lists, radio buttons, etc. You can also use different types of data sources to populate the fields with values from your application data or external systems, such as data pages, report definitions, connectors, etc. References: https://community.pega.com/knowledgebase/articles/user-interface/86/adding-fields-view

 This answer is correct because it is the earliest opportunity to configure a user view for a step in a case life cycle in App Studio. A user view is a form that displays fields and controls for users to enter or view data related to a case or an assignment. In App Studio, you can configure a user view for a step after you add that step to the case life cycle by clicking on the View icon next to the step name. References: https://academy.pega.com/library/87/pega-certified-business-architect-pcba-87v1 (Module 9: User Interface)

To display the Inspect Sailboat process only if .boatType = ‘Sail’, you need to configure the process to start if the .boatType property equals ‘Sail’. Otherwise, the process is skipped and the case life cycle continues to the next step. This way, only sailboats are inspected for sail-specific parts, while other boat types are inspected for common parts only. The other options are either incorrect or irrelevant for this requirement. References: https://docs-previous.pega.com/case-management/87/adding-processes-case-life-cycles

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

 it suspends the parent case processing until the child cases are resolved, as per the requirement. The Wait step can be configured to pause the parent case until all child cases are resolved. This way, the parent case ensures that all child cases are completed before proceeding. References: https://academy.pega.com/library/87/pega-certified-business-architect-pcba-87v1 (Module 5: Case Hierarchy)

The Repair phase can be implemented as a child case because it represents work that is performed by a third party and can be processed in parallel with other phases. A child case also allows for different reporting options and time frames for the repair work. The other phases are part of the main business process and should be implemented as steps or stages in the top-level case. References: https://academy.pega.com/topic/child-cases/v1

To satisfy this requirement, you need to configure a calculation for the total cost field. A calculation is a type of validation that derives the value of a field from an expression or a formula. You can configure a calculation for the total cost field that multiplies the room rate by the number of nights and updates the value whenever the room selection changes. References: https://community.pega.com/knowledgebase/articles/user-interface/86/configuring-calculations

Case reference and data reference are specialized versions of the query field type. A query field allows users to select a value from a list of values that are retrieved from a data source, such as a data page or a report definition. A case reference field is a query field that uses a report definition as a data source and displays cases that match a specified condition. A data reference field is a query field that uses a data page as a data source and displays values from a data type or an external system. References: https://community.pega.com/knowledgebase/articles/user-interface/86/creating-query-fields

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)

These two are benefits of DCO because they involve capturing, organizing, and storing information by using Pega’s integrated solution, the Pega Platform. DCO enables business and IT to collaborate using a shared visual model that can automatically generate documentation and working models. DCO also provides real-time awareness of project development by using Pega tools and best practices to track progress and outcomes. References: https://www.pega.com/insights/articles/what-pega-dco

 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)

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

These two situations require a data type. A data type is a reusable component that defines the structure and behavior of a set of data in your application. You can use data types to access and write data from and to external systems of record, such as databases or web services. You can also use data types to populate fields with values from your application data, such as drop-down lists or radio buttons. References: https://community.pega.com/knowledgebase/articles/data-management-and-integration/86/creating-data-types

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)

To indicate the progress of a case towards resolution, you need to update the case status on the appropriate steps. The case status reflects the current state of a case and helps users track its progress. You can use standard statuses such as New, Pending-Approval, or Resolved-Completed, or define custom statuses for your application. The other options are either incorrect or irrelevant for this requirement. References: https://docs-previous.pega.com/case-management/87/updating-case-status