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

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

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

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

To guide users through an application form without requiring user training, you can add an instruction to the assignment that explains what users need to do in that step of the case life cycle. The instruction can provide helpful tips, examples, or links to more information. The other options are either incorrect or irrelevant for this requirement. References: https://docs-previous.pega.com/case-management/87/adding-instructions-assignments

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 satisfy this requirement, you need to create a service level that specifies both A and B options. A service level is a rule that defines time intervals and actions for completing an assignment or resolving a case. A service level has two components: goal and deadline. The goal defines when an assignment or case should be completed ideally, while the deadline defines when an assignment or case must be completed at latest. You can also configure actions to perform at each component, such as sending notifications, escalating urgency, etc. References: https://community.pega.com/knowledgebase/articles/case-management/86/configuring-service-levels

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