Pegasystems PEGACPSSA23V1 - Certified Pega Senior System Architect 23 Exam

To ensure that the Manager role cannot open a purchase request during the Audit stage, applying an Access When record (B) is the most suitable approach. An Access When record allows for the definition of conditional logic that determines whether a specific action, such as opening a case, is permitted based on the user's role and the current context of the case, such as its stage. By configuring this rule to evaluate to false for users with the Manager role during the Audit stage, you can effectively restrict their access to purchase requests in this stage, aligning with the requirement.References: Pega Community documentation on Access When rules and stage-based access control.

Services in Pega Platform can be configured to listen for incoming requests using background listeners. These listeners are continuously running processes that wait for requests on specific ports or addresses. When a request is received, the service processes it accordingly. This capability is crucial for enabling asynchronous communication and integration with external systems, where Pega services can act upon requests without requiring manual initiation of these interactions.References: Pega Community documentation on service types and listeners.

A: Each rule in Pega can indeed have multiple guardrail warnings. These warnings indicate the degree to which the rule deviates from Pega's best practices.

C: Pega Platform performs a guardrail examination when a rule is saved. This is to ensure that developers are immediately aware of any potential issues that may arise from the rule they are creating or modifying. References: Pega official documentation on compliance score and guardrails.

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.

To ensure that patients can read but not edit cases in the hospital's ER case management system, two steps need to be taken. First, configure an Access Role to Object rule with the open case action set to 1 (B), which grants read-only access. This ensures that patients can view their cases without the ability to make any modifications. Secondly, create an access group unique to patients (D). This access group would include the Access Role to Object rule configured in the previous step. By associating patients with this access group, it ensures that they are granted the appropriate level of access to their cases, fulfilling the security requirements specified by the stakeholders.References: Pega Community documentation on Access of Role to Object and access groups.

Connectors establish a link to a service on another system (B). They are designed to communicate with external systems, such as sending a request to a web service or a REST service, and handle the response within a Pega application. This capability is part of Pega's integration features and enables the application to interact with multiple systems across different platforms.References: Pega Community documentation on connectors and integration.

To ensure that the advisor and the student can simultaneously edit the draft proposal, configure the locking on the case type to allow multiple users (B). This setting enables a shared access model, where multiple users can work on the case at the same time. Additionally, Pega's conflict resolution mechanisms can be utilized to check for changes before committing them to the database, ensuring that any concurrent edits are properly managed and the integrity of the proposal is maintained.References: Pega Community documentation on case locking and concurrent editing.

Controlling access to an attachment category can be achieved through various configurations. Using a When condition like "IsCurrentStageTesting" (A) allows for dynamic access control based on the case's current stage, enabling attachments to be accessible only under certain conditions. Assigning privileges, such as "DeleteOwn" (C), to users enables fine-grained control over actions users can perform on attachments, such as deleting their own attachments, thus enhancing security and compliance with business rules.References: Pega Community documentation on attachment categories and access control.

An edit validate rule is used to ensure that data is entered in a specific format. For membership numbers that need to match a particular pattern (M-######-0#), an edit validate rule would be the appropriate mechanism to enforce this format upon entry. References: Pega Platform Help - Edit Validate.

The rule types that you can mark as relevant records are those that are frequently referenced and are of high importance in the application. Reports (B) and Sections (D) can be marked as relevant records to easily access and modify these important rules. References: Pega official documentation on relevant records.