PEGACPSSA23V1 Certified Pega Senior System Architect 23 Questions and Answers

• 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.

The requirement is to handle an error when it occurs and perform two actions: display a message to the user and send an email to the administrator. This can be done by configuring an error handling process that encapsulates both actions. Typically, this would involve configuring a flow or an activity that runs when an error occurs, and it would handle both displaying the error message to the user and sending the email. References: Pega Platform Help - Error Handling.

• B: When adding a Split For Each shape to your case life cycle, you need to define when the parent process resumes processing. This can be after each iteration or after all iterations complete.
• C: You also need to specify the Page List or Page Group property that the split will iterate over. This determines the scope of the subprocesses that are to be created. References: Pega official documentation on case life cycle design.

When you generate an archive file using a Rule-Admin-Product instance, by default, it includes all checked-in rules which are the rules that have been saved and checked into the ruleset (thereby creating a historical record of the rule). It also includes instances of MyCo- class, which typically contain application-specific rules and data pertaining to the MyCo organization, assuming they're part of the specified application rulesets and versions included in the product rule. References: Pega Platform Help - Rule-Admin-Product.

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.

No

YES

YES

NO

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.

When considering post-processing actions on a flow action, it's crucial to understand their implications on the user experience and system behavior. The effect if the flow action is reloaded (A) is important because post-processing actions might not execute again, leading to inconsistent data or user experience. The sequence in which the system runs different actions (B) is critical to ensure that data transformations and business logic are applied in the correct order, maintaining data integrity and consistency. The timing of the commit for the flow action (C) influences transaction management, ensuring that all changes are saved correctly and that the system maintains data consistency, especially in multi-user environments.References: Pega Community documentation on flow actions and post-processing.

In the organizational hierarchy of Pega Platform, a work group can indeed have more than one manager, allowing for shared management responsibilities and coverage. References: Pega Platform Help - Organization and Work Groups.

To fulfill orders received during the peak season in December and process the orders in batches multiple times a day, you would create a queue processor that can process orders received by the company. Queue processors are designed to handle asynchronous, high-volume processing, which is suitable for the described use case. References: Pega official documentation on queue processors.

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 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.

You should consider using a field value when the list of allowed values is mostly static. Field values are best used for properties with values that do not change often and need to be reused throughout the application. References: Pega official documentation on field values.

The function of class mapping for reports is to retrieve data from an associated database table. Class mapping determines which table data is pulled from when running a report, ensuring that the report includes the appropriate data based on the class structure. References: Pega official documentation on class mapping and reporting.

Edit validate rules are associated with properties to validate the property value when a user inputs data. Edit validate rules contain a Java function that is called to check the property value for correctness. References: Pega Platform Help - Edit validate rules.

A native app is suitable for remote areas without internet access because it can be installed on the device and has the capability to function offline. This allows the courier company employees to scan and track parcels regardless of internet connectivity. References: Pega Mobile Client Developer Guide.

When deploying mashup code in a webpage, it is necessary to add the host URL in the Pega application to ensure that Pega Platform accepts incoming requests. This is part of configuring the trusted origins within the application's settings. References: Pega official documentation on Pega Web Mashup deployment and configuration.

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 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.

To send information to an external system of record using a connector, you would typically reference a connector from within a data transform. The data transform can manipulate the data as needed before it is sent out through the connector. References: Pega Platform Help - Connectors.

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.

When integrating multiple Pega Web Mashups into a single page, it is necessary to identify unique names for each mashup to ensure that they are embedded and function independently without conflict on the client's page. References: Pega Platform Help - Pega Web Mashup.

Unit tests are the first line of testing when ensuring that an integration passes data as expected. They are designed to test individual parts of the code — in this case, the integration point with an external data source — to confirm that it works properly in isolation. References: Pega Platform Help - Automated Unit Testing

A prerequisite for configuring a Pega Web Mashup is having a web server to test your host page. This is because the mashup will be embedded within a webpage, and testing on a web server ensures that the integration works as expected before going live. References: Pega official documentation on Pega Web Mashup prerequisites.

To prevent horizontal scrolling on mobile devices, setting the importance of columns allows for the most critical information to be shown first, potentially hiding less important columns on smaller screens. Using percentage widths for layouts ensures that the layout adapts to the screen width, which can also help prevent horizontal scrolling. References: Pega UI design best practices for mobile devices.

To allow both doctors and nurses to modify cases while complying with the identified security requirements, the best approach is to create a single access role for both doctors and nurses (C) and set the modify action to 5. This configuration grants both user groups the necessary permissions to modify cases throughout the case life cycle. By using a single access role with a high level of access for modifications, the application simplifies role management while ensuring that both doctors and nurses can perform their duties effectively, without compromising the security and integrity of patient cases.References: Pega Community documentation on Access Role to Object and case management best practices.

To include access groups in your Product rule, you can:

• A: Associate the access groups with a ruleset included in the application. This ensures that when the ruleset is included in the product rule, the associated access groups are also included.
• D: Add the access group directly to the Product record in the Individual instances to include section. This allows you to specifically select which access groups to include in the product rule. References: Pega official documentation on Product rules.

To implement the requirement of associating users in different units to the same work queue, you associate the users to a common work group and then associate a work queue to that work group. This allows users from different units, who are part of the same work group, to access the same work queue. References: Pega official documentation on work groups and work queues.

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.

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.

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.

Adding a footer to the Case Manager portal can be done by updating the skin that's applied to the portal. Skins in Pega define the look-and-feel of user interfaces, including headers, footers, and other elements. References: Pega Platform Help - Skins.

In Access Control Policies, attributes like Appointment date (A) and Number of dependents (B) can be used to define conditions for data access. These attributes can be part of case data or user profiles and serve as criteria for determining access levels. For example, an access control policy can restrict access to certain case information based on the appointment date or allow access to specific functionalities based on the number of dependents associated with a user profile.References: Pega Community documentation on Access Control Policies.

The two most common ways to expose your application to an external system are to leverage the Pega API (B) and to create a web service with the Service wizard (D). The Pega API provides a set of out-of-the-box RESTful endpoints for performing operations within the Pega Platform. The Service wizard simplifies the creation of SOAP or REST services, enabling external systems to interact with Pega applications.References: Pega Community documentation on Pega API and Service wizard.

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.

The compliance score of an application is generated based on several factors, including the number of rules with warnings, the number of rules with unjustified warnings, and the percentage of compliant rules in the application. This score helps to identify potential issues with rule compliance and areas that may need attention. References: Pega Platform Help - Compliance score.