Pegasystems PEGAPCBA87V1 Pega Certified Business Architect (PCBA) 87V1 Exam Practice Test

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

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

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

This option requires you to configure distinct mobile app channels for users and CSRs because it involves different capabilities for different user roles. A mobile app channel defines how a case type is displayed and processed on a mobile device. You can configure different mobile app channels for different user roles and case types. The other options do not require distinct mobile app channels because they involve common features or settings that can be applied to all users or devices. References: https://docs-previous.pega.com/mobile/87/configuring-mobile-app-channels

A journey is a high-level description of an end-to-end process that delivers value to a customer or stakeholder. A microjourney is a specific path or scenario within a journey that achieves a particular outcome or goal for a persona or role. In this case, customer obtains troubleshooting assistance is a journey, and new customer obtains troubleshooting assistance by using a call center and experienced customer obtains troubleshooting assistance by using the online forum are microjourneys. References: https://community.pega.com/knowledgebase/articles/application-development/86/defining-journeys-and-microjourneys

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

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

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