PEGACPSSA23V1 Pegasystems Certified Pega Senior System Architect 23 Exam Free Practice Exam Questions (2025 Updated)

Creating a new ruleset version for each team ensures that each team's work is isolated within a specific version, preventing overlap and conflict. Setting up a branch ruleset for each team further isolates development work, allowing parallel development streams that can later be merged back into the main application ruleset. These two options, when used together, provide the most flexibility for teams working on separate enhancements with uncertain release dates. References: Pega Platform Help - Branch Rulesets.

To satisfy the requirement that employees cannot see complaints made against themselves, an Access Control Policy (B) is the most suitable security solution. Access Control Policies in Pega allow for the definition of conditions under which access to certain data or cases is granted or denied. By configuring a policy that checks the relationship between the complaint and the employee (such as matching IDs), the system can dynamically restrict access to sensitive information, ensuring compliance with auditing policies.References: Pega Community documentation on Access Control Policies.

Integrating a third-party application with Pega Platform can be efficiently achieved through REST calls using the Pega API. This allows for seamless communication between the third-party application's existing front end and Pega's backend processes. The REST API endpoints in Pega Platform enable external applications to interact with Pega applications for operations like case management, assignments, and data retrieval, without requiring significant changes to the existing user interface or user experience. This approach minimizes the need for extensive retraining of users on a new system, leveraging the familiar UI of the existing application.References: Pega Community documentation on Pega APIs and integration best practices.

Branched rulesets are used when multiple teams need to work on the same application version simultaneously. Each team can work in their own branch, allowing for concurrent development without affecting the main application until the branches are merged. References: Pega Platform Help - Branched Rulesets.

A keyed data page is best used when a user selects a replacement part from a long list that seldom changes (B). Keyed data pages are designed to efficiently manage large amounts of data that do not change frequently by loading data specific to a key (like a part ID). This improves performance by caching the data and reducing the need to frequently query the source system for the same data.References: Pega Community documentation on data pages and caching strategies

Application settings are used to point to external resources that can change without requiring changes to the application code. For example, a weather service application might use application settings to specify the URL of a web service for weather data. References: Pega Platform Help - Application Settings.

The compliance score of an application in Pega Platform includes items such as rules with unjustified warnings in the application (A), rules with warnings in the application (D), and the percentage of compliant rules in the application (E). These metrics provide insights into the application's adherence to best practices and guardrails, highlighting areas that may require attention to improve application quality, maintainability, and performance.References: Pega Community documentation on Application Quality Dashboard and compliance scoring.

To satisfy the requirement that users assigned the role "Manager" can edit objects related to any studio work, the Access of Role to Object (ARO) record should be configured at the "UPlusMusic-Production-Work-Studio-" level (C). This level is the common parent class for all studio-related work, such as Recording and Editing. By setting the ARO at this level, it ensures that managers have the necessary permissions to edit any object that falls under the studio work hierarchy, without having to set permissions at each individual subclass level.References: Pega Community documentation on class hierarchy and Access of Role to Object configuration.

A: Configuring a data transform to apply the Open-Review status on the appropriate assignments can be used to change the status of a case when it is assigned to a user for review.

D: Apply the Open-Review status to the appropriate assignments directly within the flow where the assignment is configured. References: Pega official documentation on case statuses and data transforms.

To satisfy the report requirements, you can configure a class join on the Fulfillment report definition to join the operator information to each case. Alternatively, you can use an association rule to achieve the same effect. Both these options allow for the relevant operator information to be displayed alongside the shipping information in the report. References: Pega Reporting Guide - Joining Data.

When a report is created in a class group (MyCo-HR-SelfService-Work), it will return instances of its child classes (MyCo-HR-SelfService-Work-TimeOff and MyCo-HR-SelfService-Work-Expense) unless those child classes are stored in different database tables due to class table inheritance or other data storage configurations. References: Pega official documentation on reporting and class groups.

A Declare OnChange rule is designed to perform an action when a specified property changes. The action that a Declare OnChange rule can perform includes executing a data transform, which allows for the automated update of properties when a change is detected in the specified property. References: Pega official documentation on Declare OnChange rules.

A: In Pega Platform, the PegaRULES database is used to store rules, while the PegaDATA database contains work instances and other data instances.

B: The Database Table rule in Pega allows you to configure the connection settings to a specific external database table, facilitating the interaction with external data sources. References: Pega official documentation on Pega Platform databases and Database Table rules.

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.

Graphical user interface, application Description automatically generated

At 4.5 hours after the case reaches the assignment, the SLA would have passed the goal and deadline, and entered the passed deadline period. The initial urgency is 15, the goal adds 10 (total 25), and the deadline adds 15 (total 40). After the passed deadline, the urgency increases by 10 every hour up to a limit of 10 events. By 4.5 hours, there would have been two passed deadline events, adding 20 to the urgency, leading to a total urgency of 60. References: Pega Platform Help - Service Level Agreements.

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.