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

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

To sort the cases so the case with the most recent create date appears at the top of the list, you need to select the Highest to Lowest sort type for the Create Date column. This will arrange the cases in descending order of their creation date. The other options are either incorrect or irrelevant for this requirement. References: https://docs-previous.pega.com/reporting/87/sorting-and-grouping-columns-list-reports

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

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

This scenario is a use case for the Wait step because it involves pausing a case until another case reaches a certain status. The salary increase case can be configured to wait for the approval case to reach a Resolved-Approved status before continuing to process the increase. The other scenarios 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

 it suspends the parent case processing until the child cases are resolved, as per the requirement. The Wait step can be configured to pause the parent case until all child cases are resolved. This way, the parent case ensures that all child cases are completed before proceeding. References: https://academy.pega.com/library/87/pega-certified-business-architect-pcba-87v1 (Module 5: Case Hierarchy)

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)