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

When configuring Pega Web Mashup, it's essential to create one DIV element in the hosting web page for each Pega gadget (A), ensuring that each gadget is properly isolated and rendered within its designated area on the web page. Additionally, adding a list of trusted domains in your application settings (B) is crucial for security, as it specifies which domains are authorized to host the mashup, preventing unauthorized use or embedding of the Pega functionalities in untrusted environments.References: Pega Community documentation on Pega Web Mashup configuration and security best practices.

C:\Users\Waqas Shahid\Desktop\Mudassir\Untitled.jpg

The correct match for each error type to its description is:

Transient Errors -> These errors usually correct themselves over time.

Permanent Errors -> These errors are typically due to a configuration error or an error in the remote application logic.

Withdrawing the circumstanced rules in the AccountOpen class is the correct action to stop using a circumstanced rule. This allows the non-circumstanced (or base) rule to be used instead without affecting other circumstanced versions of the rule for different case types. References: Pega Platform Help - Withdrawing a rule.

The initial urgency is set at 20. At 5 hours, the urgency increases by 10 (total 30). At 8 hours, the urgency increases by 20 (total 50). After the deadline, the urgency increases by 20 every 2 hours, up to a limit of 5 events. By 16 hours, all 5 events have occurred, adding 100 to the urgency, leading to a total urgency of 150 (initial 20 + goal 10 + deadline 20 + passed deadline 100). References: Pega Platform Help - Service Level Agreements.

A: When using a Pega Web Mashup, leveraging the standard authentication service IACAuthentication and updating the authentication activities to match the external system's requirements is a common practice.

D: Configuring application permissions by specifying a list of trusted domains in the application rule is important for security purposes and to control which external domains are allowed to embed the mashup. References: Pega official documentation on Pega Web Mashup configuration.

Inbound request received

Map inbound data

Request processing

Map outbound data

System returns a response

This sequence represents the typical flow of processing an inbound service request, from the initial receipt of the request to the final response after the necessary processing and mapping have been completed.

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.

To ensure that the correct pattern is entered for a part number field, configure an edit validate rule and reference it from the property rule for the field. The edit validate rule can be set up to check that the first two characters are letters and the last four are digits. References: Pega official documentation on property rules and edit validate rules.

To resolve performance issues caused by resource-intensive queue processors, it's essential to ensure that these processors are associated with appropriate node types (A) and that application nodes are configured with node types (D). Associating queue processors with specific node types allows for the distribution of workload across the application infrastructure, optimizing resource utilization and improving performance. Configuring application nodes with node types ensures that tasks are executed on the most suitable nodes, further enhancing system efficiency and scalability.References: Pega Community documentation on queue processors and node types.

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.