PEGAPCBA87V1 Sample Questions Answers

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

You can use a list or an interactive chart to present insight data on the Explore Data landing page. A list displays the data in a tabular format, while an interactive chart displays the data in a graphical format, such as a pie chart or a bar chart. You can also filter, sort, group, and drill down the data in both types of visualizations. References: https://community.pega.com/knowledgebase/articles/reporting/86/viewing-insights-explore-data-landing-page

To display the Inspect Sailboat process only if .boatType = ‘Sail’, you need to configure the process to start if the .boatType property equals ‘Sail’. Otherwise, the process is skipped and the case life cycle continues to the next step. This way, only sailboats are inspected for sail-specific parts, while other boat types are inspected for common parts only. The other options are either incorrect or irrelevant for this requirement. References: https://docs-previous.pega.com/case-management/87/adding-processes-case-life-cycles

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

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