Pegasystems Pega Certified Business Architect (PCBA) 87V1 PEGAPCBA87V1 Exam Dumps: Updated Questions & Answers (September 2025)

To display the Select hotel amenities section only if a user selects the Add amenities check box, you need to apply a visibility condition (when rule) to the section. The when rule can check whether the Add amenities check box is selected or not, and show or hide the section accordingly. The other options are either incorrect or irrelevant for this requirement. References: https://docs-previous.pega.com/user-interface/87/controlling-visibility-ui-elements

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. References: https://community.pega.com/knowledgebase/articles/application-development/86/application-layers

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

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

These two use cases can be implemented by using one or more calculated fields because they involve setting the value of a calculated field based on one or more input fields. For example, the cost of painting a banquet hall can be calculated by multiplying the labor rate, the number of hours, and the area of the hall. The cost of an insurance policy can be calculated by adding the base premium and the selected coverage options. Calculated fields can use functions or custom calculations to express the relationship between fields. References: https://academy.pega.com/topic/calculated-values/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

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

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

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

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