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

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 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. References: https://docs-previous.pega.com/case-management/87/sending-email-notifications

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

it fetches exchange rates that are updated on a daily basis from a web service and makes them available in your application using a data page. A request scope for a data page means that the data page is loaded once per user session and is refreshed when the user logs out and logs back in. This way, the data page can provide the most up-to-date exchange rates for each user session. References: https://academy.pega.com/library/87/pega-certified-business-architect-pcba-87v1 (Module 10: Data Pages)

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

This option requires you to configure distinct mobile app channels for users and CSRs because it involves different capabilities for different user roles. A mobile app channel defines how a case type is displayed and processed on a mobile device. You can configure different mobile app channels for different user roles and case types. The other options do not require distinct mobile app channels because they involve common features or settings that can be applied to all users or devices. References: https://docs-previous.pega.com/mobile/87/configuring-mobile-app-channels

This requirement can be satisfied by using a Wait step with a Timer wait type that pauses a case until a set date/time interval expires or until a reference date/time is reached. In this case, the Wait step can be configured to pause the Accident Claim case for 48 hours after the accident date/time property value. The other requirements 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