Free Practice Questions for Pegasystems PEGAPCBA87V1 Exam

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

To show the total number of purchase requests for each of the regional cost centers, you need to summarize the case ID column by count and group the results by the regional cost center column. This will create a summary report that displays the count of case IDs for each cost center value. References: https://community.pega.com/knowledgebase/articles/reporting/86/summarizing-data-reports

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

 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)

This use case describes the function of the Estimator tool. The Estimator tool is a feature that helps you estimate the time and effort required to build an application or a release based on your scope definition and delivery approach. You can use the Estimator tool to plan your project schedule, budget, resources, and risks. References: https://community.pega.com/knowledgebase/articles/application-development/86/estimating-time-and-effort-application-development

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

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

To enable sales managers to approve sales quote proposals by email and from a mobile device, you need to add an Approve/Reject step to the case life cycle and enable email and mobile approval. This option allows sales managers to approve or reject the proposal by replying to an email message or by using a mobile app. The other options are either incorrect or irrelevant for this requirement. References: https://docs-previous.pega.com/case-management/87/approving-rejecting-cases-email https://docs-previous.pega.com/case-management/87/approving-rejecting-cases-mobile-devices

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