PEGAPCBA87V1 Sample Questions Answers

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

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

Insights are interactive visualizations that help you explore and analyze data in your application. You can create insights from data queries by selecting the fields that you want to include and choosing a visualization type, such as a chart or a table. You can also share insights with other users or embed them in dashboards or portals. References: https://community.pega.com/knowledgebase/articles/reporting/86/creating-insights

This requirement can be satisfied by using a Wait step with a Timer wait type that pauses a case until a set date/time interval expires or until a reference date/time is reached. In this case, the Wait step can be configured to pause the Accident Claim case for 48 hours after the accident date/time property value. The other requirements 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 satisfy this security requirement, you need to create a new Analyst role with the required access. A role defines a set of permissions that grant access to specific features and functions in an application. You can create a new role by copying an existing role and modifying its permissions as needed. You can also assign multiple roles to a user or a group of users to grant them combined access. References: https://community.pega.com/knowledgebase/articles/security/86/managing-roles

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

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

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

Autocomplete and dropdown controls can be used to minimize clutter on the order form because they do not display all the options until the user clicks or types in the control. This helps reduce the space occupied by the UI elements and makes the form more compact and clear. Checkbox and radio buttons controls display all the options on the form, which can create clutter if there are many options to choose from. References: https://academy.pega.com/topic/user-interface-controls/v1

These two case types can support the scenario of filing home insurance claims with items of loss and potential fraud investigation. Items of loss can be implemented as a child case type that represents each item that is claimed by the customer. Fraud investigation can be implemented as a parallel process that runs in the background while the main claim process is ongoing. The other options are either incorrect or irrelevant for this scenario. References: https://academy.pega.com/topic/child-cases/v1 https://academy.pega.com/topic/parallel-processes/v1

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 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)

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

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

 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)