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

Rule resolution will choose the rule that is most specific to the circumstances of the case. Since the country is set to Japan, the rule resolution algorithm will choose the rule version that is circumstanced for Japan. Among the options, 01-01-02 is the circumstanced rule that matches the country condition of Japan and would be selected over the base rule and any other versions. References: Pega Platform Help - Rule Resolution.

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.

On 1 June 2020, rule resolution would choose the instance of the rule that is circumstanced for Algeria, provided that the rule's availability is not blocked or withdrawn and the ruleset version is accessible by the operator's access group. The specific rule circumstanced for Algeria would take precedence over the base rule or other circumstanced rules that do not match the circumstance condition. References: Pega SSA course materials on circumstancing rules.

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.

The Purge/Archive wizard in Pega Platform is appropriately used to remove old cases to reduce the size of a database table (B). Over time, completed or resolved cases can accumulate in the system, leading to large table sizes that can negatively impact application performance. By archiving these cases, you can move them out of the primary database tables into an archive, and by purging, you can delete cases that are no longer needed. This process helps maintain optimal database performance and manage storage costs effectively.References: Pega Community documentation on the Purge/Archive wizard and database maintenance best practices.

To add a new minor version of an application ruleset for a phased rollout, you would lock the current version of the ruleset to prevent further changes (this is referred to as "rolling" the ruleset), and then create a new minor version. The application record should be updated to reference this new minor version of the ruleset. This ensures that the new features can be tested and gradually released to the user base without the need to create a completely new application version. References: Pega Senior System Architect documentation on versioning and release practices.

Since the MSDS rarely changes, a keyed data page that allows multiple pages for each key is the most efficient. This configuration enables the data page to hold the MSDS for each product, identified by a unique key (e.g., the product ID), in memory for quick retrieval without the need to reload the data frequently. References: Pega Platform Help - Data Pages.

Graphical user interface Description automatically generated

To match the security solutions to their appropriate use cases:

"Access of Role to Object" is typically used to specify what actions a particular role can perform on instances of a class. It would be appropriate for a use case where "Dealers can modify evaluations" since this is an action that a specific role (dealers) would be allowed to perform.

"Access Control Policy" allows defining rules that enforce property and case access restrictions based on the user role and other conditions. It would be appropriate for a use case where "Customers can only view their own credit report" since this would be a restriction based on user-specific data.

"Access Deny" is used to explicitly deny access to a rule or data instance. It fits the use case where "Dealers cannot run reports" because it is a restriction that prevents a specific action (running reports) for a specific role (dealers).

"Access when" is a rule that defines conditions for whether certain access is allowed. It would be used in the scenario where "Dealers cannot modify orders in the Fulfillment stage" since this is a conditional restriction based on the stage of the process.

Based on these explanations, here is the matched list:

Access when -> Dealers cannot modify orders in the Fulfillment stage.

Access Control Policy -> Customers can only view their own credit report.

Access Deny -> Dealers cannot run reports.

Access of Role to Object -> Dealers can modify evaluations.

To ensure that the values are only initiated once for each flow action, add logic to the pre-processing data transform to test if the values were already initiated (A). This logic can prevent the reinitialization of values that have already been set, allowing the pre-processing to only set default values when they are not present, avoiding any unwanted overwrites or duplications of effort.References: Pega Community documentation on data transforms and flow action pre-processing.

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.