PEGAPCBA87V1 Pega Certified Business Architect (PCBA) 87V1 Questions and Answers

The three roles that you invite to the DCO sessions are product owner, subject matter experts, and system architect. The product owner is the primary stakeholder who represents the business vision and priorities for the application. The subject matter experts are the users or customers who provide input and feedback on the application requirements and functionality. The system architect is the technical lead who designs and builds the application using Pega Platform. References: https://academy.pega.com/library/81/pega-certified-business-architect-pcba-81

The logic statement A returns the correct subset of transaction disputes because it filters the cases by the vendor name (F1 or F2), the transaction amount (F3 or F4), and the dispute reason (F5). The parentheses indicate the order of operations and the AND and OR operators combine the conditions. The logic statement A can be read as follows: Return the cases where (the vendor is MaxValu and the amount is greater than or equal to 25) OR (the vendor is MegaMart and the amount is greater than or equal to 50) AND (the dispute reason is stolen card). References: https://community.pega.com/knowledgebase/articles/reporting/86/filtering-data-reports

To display the Employee vacation requests report in the Manager portal dashboards, you need to add a report widget to the dashboard and publish it. This will make the report visible to all managers who have access to the Manager portal. The other options are either incorrect or irrelevant for this requirement. References: https://docs-previous.pega.com/reporting/87/adding-report-widgets-dashboards

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

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

To indicate the progress of a case towards resolution, you need to update the case status on the appropriate steps. The case status reflects the current state of a case and helps users track its progress. You can use standard statuses such as New, Pending-Approval, or Resolved-Completed, or define custom statuses for your application. The other options are either incorrect or irrelevant for this requirement. References: https://docs-previous.pega.com/case-management/87/updating-case-status

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

 This answer is correct because it is the earliest opportunity to configure a user view for a step in a case life cycle in App Studio. A user view is a form that displays fields and controls for users to enter or view data related to a case or an assignment. In App Studio, you can configure a user view for a step after you add that step to the case life cycle by clicking on the View icon next to the step name. References: https://academy.pega.com/library/87/pega-certified-business-architect-pcba-87v1 (Module 9: User Interface)

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

To configure the case type to verify that the value of Date account opened is in the past, you need to use a validation condition. A validation condition is a rule that checks whether the value of a field meets a specified criterion. You can use a validation condition for the Date account opened field that compares it with the current date and displays an error message if it is not in the past. References: https://community.pega.com/knowledgebase/articles/user-interface/86/configuring-validation-conditions

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

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

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

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 meet these requirements, you need to create four personas: Employee, HR, IT, and Facilities. A persona is a role that represents a group of users who perform similar tasks in your application. You can use personas to define user stories, assign tasks, configure access groups, and design user interfaces for your application. References: https://academy.pega.com/library/81/pega-certified-business-architect-pcba-81

To satisfy this user story, you need to add a case wide action to the case workflow. A case wide action is an action that users can perform at any point in the case life cycle, regardless of their current stage or assignment status. You can add a case wide action to allow users to cancel an open service request at any time and resolve the case accordingly. References: https://community.pega.com/knowledgebase/articles/case-management/86/configuring-case-wide-actions