To configure the Promotional discount field, you need to create a calculated currency field that uses a decision table. A calculated field sets its value based on one or more input fields by using functions or custom calculations. A decision table is a type of calculation that defines multiple conditions and outcomes in a tabular format. In this case, you can use a decision table to define the different order total ranges and their corresponding discount amounts. The other options are either incorrect or irrelevant for this requirement. Reference: https://academy.pega.com/topic/calculated-values/v1 https://docs-previous.pega.com/decision-management/87/decision-tables

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). Reference: https://community.pega.com/knowledgebase/articles/reporting/86/filtering-data-reports

A case reference field allows users to select a case from a list of existing cases that match a specified condition. You can configure a case reference field to display the case ID, the case name, or any other property of the case. You can also use a case reference field to link cases together or to navigate to another case. Reference: https://community.pega.com/knowledgebase/articles/user-interface/86/creating-case-reference-fields

To inform a user by email when an assignment is added to the user's worklist, you need to configure the case type to send assignment notifications to assigned users. This option enables email notifications for all assignments in the case type. The other options are either incorrect or irrelevant for this requirement. Reference: https://docs-previous.pega.com/case-management/87/sending-email-notifications

A user story is a concise description of a feature or functionality that a user wants to achieve in an application. A good user story has three characteristics: it can be tested, it reflects the business value the client receives, and it is easy to understand. It can be tested means that the user story has clear and measurable acceptance criteria that verify whether it meets the user's expectations. It reflects the business value the client receives means that the user story explains why the feature or functionality is important or beneficial for the user or the business outcome. It is easy to understand means that the user story uses simple and consistent language that avoids technical jargon or ambiguity. Reference: https://academy.pega.com/library/81/pega-certified-business-architect-pcba-81