Pass the Pegasystems Certified Senior System Architect PEGACPSSA23V1 Questions and answers with ValidTests

To create a custom status named Open-Review to be applied to assignments in one application, create a Field Value record named Open-Review for .pyStatusWork with the Apply To class set to the class group (A). This approach allows you to customize the status values used in your application and ensure that they are available for use in assignments within the specified class group, which typically corresponds to an application.References: Pega Community documentation on Field Value records and status values.

In Application Settings, you can specify different values for production levels using text (e.g., URLs, file paths) or picklists (for selecting from predefined options). These settings allow for easy adjustment of values according to the environment the application is running in. References: Pega Platform Help - Application Settings.

To handle the unavailability of a system of record when using a SOAP connector, the most effective approach is to implement the retry logic in the connector's error handler flow. This flow can be configured to wait for a specified duration (in this case, an hour) before retrying the connection. If the system remains unavailable after the retry, the flow can then proceed to send a notification to the system administrator. This approach encapsulates the error handling logic within the connector's flow, making it reusable and maintainable.References: Pega Community documentation on connector error handling and SOAP connectors.

The application type can often be identified by viewing the Application layers widget for the ruleset stack, which gives an overview of how the application is structured, and by viewing the Application definition rule, which provides detailed information about the application's setup and its components. References: Pega Platform Help - Application Layers.

Generating report data based on several properties stored in the BLOB (Binary Large Object) can impact performance because it requires full database table scans. Using SQL query tools or activities to archive case data before purging tables can also negatively impact performance, as they may not be optimized for the Pega Platform's data structures. References: Pega Platform Help - Performance Best Practices.

When creating a pre-processing data transform, you should consider the timing of the commit for the flow action and the effect if the flow action is reloaded. These factors can impact how the data transform processes data and how it integrates with the flow action's lifecycle. References: Pega Platform Help - Data Transforms.

In attribute-based access control (ABAC), an attribute can be a property (such as an age or status), a Boolean value (indicating true or false conditions), or a single string (such as a name or identifier). These attributes are evaluated to determine access rights within the application. References: Pega Platform Help - ABAC.

A class group is used to associate child classes with a single database table. This mechanism is known as class table inheritance, where instances of different but related concrete classes that belong to the same class group are stored in the same database table. References: Pega official documentation on class groups and class inheritance.

The assignment urgency 6.5 hours after the case reaches the assignment with the given SLA configuration would be 95 (B). Here's the calculation: The initial urgency is 20. The case reaches the goal after 5 hours, adding 10 to the urgency, making it 30. Since the deadline is at 2 hours and has been exceeded by 4.5 hours, the urgency increases by 25, making it 55. Now, with the passed deadline events occurring every hour and increasing urgency by 5, after 1.5 hours, this would occur 1 additional time (since it's half an hour into the next hour), adding 5 to the urgency. Therefore, the total urgency after 6.5 hours is 20 (initial) + 10 (goal) + 25 (deadline) + 5 (passed deadline event) = 60. However, since the deadline urgency increase occurs at the 2-hour mark, the urgency would be 20 + 25 = 45 at 2 hours, and then after reaching the goal at 5 hours, additional 10 is added, making it 55, and then one passed deadline event adds 5 more, making the total 60. Since the deadline urgency is already accounted for at the 2-hour mark, it should not be added again after the goal. Therefore, the correct total urgency would be 20 (initial) + 10 (goal) + 25 (deadline) + 40 (8 passed deadline events) = 95.References: Pega Community documentation on SLAs and urgency calculation.

To support accessibility, it's recommended to use a calendar control that displays an entire month. This allows users who rely on screen readers or keyboard navigation to select a date without the need for precise mouse control or having to manually input the date, which can be error-prone. References: Pega User Interface Design Guide - Accessibility.