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

This option fits the scope for the minimum lovable product (MLP) based on Pega best practices. An MLP is the smallest version of an application that delivers value to customers and stakeholders while meeting their core needs and expectations. Pega best practices suggest that you should focus on building an MLP that solves one problem well, provides immediate feedback, and creates positive emotions for users. The option D satisfies these criteria by allowing customers to enter their order number and see the order status and delivery date details in one view. References: https://community.pega.com/knowledgebase/articles/application-development/86/defining-minimum-lovable-product

To configure the requirement that a customer can update an address at any point during case processing, you need to add a case-wide optional action to the workflow that performs the address change process. A case-wide optional action is an action that users can invoke at any time during the case life cycle. The address change process can be a series of steps that include submitting the new address, verifying it, and confirming it. The other options are either incorrect or irrelevant for this requirement. References: https://academy.pega.com/topic/optional-actions/v1

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)

To populate the backlog directly from the spreadsheet, you need to import stones. Stones are work items that represent features or functionalities that need to be built in an application. You can import stones from a spreadsheet file into Agile Workbench to create a backlog for your project. References: https://community.pega.com/knowledgebase/articles/agile-workbench/86/importing-stones-spreadsheet-file

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)

To sort the cases so the case with the most recent create date appears at the top of the list, you need to select the Highest to Lowest sort type for the Create Date column. This will arrange the cases in descending order of their creation date. The other options are either incorrect or irrelevant for this requirement. References: https://docs-previous.pega.com/reporting/87/sorting-and-grouping-columns-list-reports

This scenario is a use case for the Wait step because it involves pausing a case until another case reaches a certain status. The salary increase case can be configured to wait for the approval case to reach a Resolved-Approved status before continuing to process the increase. The other scenarios do not involve pausing a case based on a timer or a case dependency, but rather on user actions or inputs. References: https://academy.pega.com/topic/case-workflow-dependency/v1

To send email notifications automatically to the adjuster, the insured party, and the insurance agent when an auto accident claim is resolved, you need to add a Send Email step to the resolve process and include all required participants as recipients. You can use fields, participants, or user references to identify the recipients. The other options are either incorrect or irrelevant for this requirement. References: https://academy.pega.com/topic/email-correspondence/v1 https://docs-previous.pega.com/case-management/87/sending-emails

A case reference field allows users to select a case from a list of existing cases that match a specified condition. You can configure a case reference field to display the case ID, the case name, or any other property of the case. You can also use a case reference field to link cases together or to navigate to another case. References: https://community.pega.com/knowledgebase/articles/user-interface/86/creating-case-reference-fields

This use case requires an integration by using robotic process automation (RPA). RPA is a technology that automates tasks by mimicking human interactions with user interfaces of applications or systems. You can use RPA to integrate with legacy systems that lack an exposed API or a standard protocol for data exchange. For example, you can use RPA to update a customer profile in a legacy system by launching the system’s application, entering the customer data, and clicking the save button. References: https://community.pega.com/knowledgebase/articles/application-development/86/integrating-robotic-process-automation

These two options are examples of configurations that you can perform for a mobile app channel. A mobile app channel defines how a case type is displayed and processed on a mobile device. You can configure security behavior such as biometric identifiers, encryption, or offline authentication for a mobile app channel. You can also manage administrative functions such as access to log files, crash reports, or feedback forms for a mobile app channel. The other options are either incorrect or irrelevant for this question. References: https://docs-previous.pega.com/mobile/87/configuring-mobile-app-channels

Calculated fields are fields that derive their values from other fields or expressions. You can use calculated fields to implement use cases that require calculations based on user inputs or data sources, such as estimating costs, quoting prices, computing discounts, etc. For example, you can create a calculated field that multiplies the labor hours by the hourly rate to estimate the labor cost for painting a banquet hall, or a calculated field that adds up the premiums for different coverage options to quote the cost of an insurance policy. References: https://community.pega.com/knowledgebase/articles/user-interface/86/creating-calculated-fields

Data records are instances of data types that store information in your application. Data records need unique, user-generated IDs to identify and reference them. Data records also define permissible values for data fields that use them as data sources, such as drop-down lists, radio buttons, etc. References: https://community.pega.com/knowledgebase/articles/data-management-and-integration/86/creating-data-records

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

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

To identify duplicate maintenance requests from the same address, you need to configure the apartment address and the tenant name as basic conditions on the Search duplicate cases step. Basic conditions are fields that must match exactly for cases to be considered duplicates. The request type is not relevant for identifying duplicates, and weighted conditions are used for fields that may have similar but not exact values. References: https://docs-previous.pega.com/case-management/87/searching-duplicate-cases