PEGACPSSA23V1 Questions and Answers

When two teams work on different enhancements within the same ruleset and wish to keep their work separate, the best practice is to create a new ruleset version for one of the teams and to use branch rulesets for each team. This allows for parallel development without interference, and the teams can merge their work back into the main ruleset when they're ready. References: Pega best practices for parallel development.

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.

The Static Assembler is a Pega tool used to address rules assembly issues specifically when the server is managing a large number of rules caches. By pre-assembling rules into a static content, the Static Assembler helps in improving performance in situations where cache management becomes complex due to the volume of rules. It creates a set of static files that represents the assembled rules, which can reduce the overhead on the server during rule assembly and cache management. References: Pega official documentation on performance tools and best practices.

No

YES

YES

NO

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.

To support the requirement that all investigation cases are higher priority than other case types, create a service-level agreement (SLA) rule and increase the initial urgency (B). By setting a higher initial urgency on the SLA rule for Investigation cases, you ensure that these cases are prioritized over others from the moment they are created. This configuration directly influences the assignment urgency and worklist prioritization, aligning with the business requirement.References: Pega Community documentation on service-level agreements and case prioritization.

When properties are encrypted in Pega Platform, they cannot be used in filter conditions for reports because the data is in a non-readable format. To apply filters, the data must be decrypted, which is not typically done within the reporting tool. References: Pega Platform Help - Data Encryption.

The assignment urgency 6.5 hours after the case reaches the assignment with the given SLA configuration would be 95 (B). Here's the calculation: The initial urgency is 20. The case reaches the goal after 5 hours, adding 10 to the urgency, making it 30. Since the deadline is at 2 hours and has been exceeded by 4.5 hours, the urgency increases by 25, making it 55. Now, with the passed deadline events occurring every hour and increasing urgency by 5, after 1.5 hours, this would occur 1 additional time (since it's half an hour into the next hour), adding 5 to the urgency. Therefore, the total urgency after 6.5 hours is 20 (initial) + 10 (goal) + 25 (deadline) + 5 (passed deadline event) = 60. However, since the deadline urgency increase occurs at the 2-hour mark, the urgency would be 20 + 25 = 45 at 2 hours, and then after reaching the goal at 5 hours, additional 10 is added, making it 55, and then one passed deadline event adds 5 more, making the total 60. Since the deadline urgency is already accounted for at the 2-hour mark, it should not be added again after the goal. Therefore, the correct total urgency would be 20 (initial) + 10 (goal) + 25 (deadline) + 40 (8 passed deadline events) = 95.References: Pega Community documentation on SLAs and urgency calculation.

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.

For offline support, it's necessary to have the access groups configured to allow offline access to users so that the correct rules and data can be synchronized to the user's device. In addition, the case types must be configured to function properly in an offline environment, ensuring that users can create, update, and submit cases without a network connection. References: Pega Mobile Client Developer Guide.

A Declare OnChange rule is appropriate in a scenario where an immediate automatic response is required to a property change. For instance, when a manager approves a case (D), the case is routed back to the appropriate case worker. The OnChange rule can detect the approval and automatically perform the routing. References: Pega official documentation on Declare OnChange rules.

In Pega's ruleset hierarchy, a ruleset can reference rules in its own ruleset as well as in any prerequisites (and their prerequisites, recursively). Since MyCo lists MyCoInt and Customer as its prerequisites and MyCoInt, in turn, lists Pega-ProcessCommander (which is not relevant here), MyCo can reference rules in both Homelns and HomelnsInt. However, since only Homelns is explicitly mentioned in the options, the correct answer is that MyCo can reference rules in Homelns. References: Pega SSA course materials on ruleset hierarchy and ruleset validation.

Graphical user interface, application Description automatically generated

The difference between using the Call and Branch methods in an activity step to invoke other activities is that Call will return to the originating activity once the called activity completes, while Branch will not return to the originating activity and will skip the remainder of it after the called activity completes. References: Pega official documentation on activity methods.

Field-level auditing is enabled directly on the property rule form, where you can specify that changes to the property should be audited. This ensures that any changes to the field are tracked and recorded. References: Pega Platform Help - Auditing.

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.

A keyed data page is best used for data that does not change frequently and can be retrieved by a unique key. A long list of vehicle parts that rarely changes fits this criterion because the data can be cached and doesn't require frequent updates, optimizing performance. References: Pega Platform Help - Data Pages.

The application type can often be identified by viewing the Application layers widget for the ruleset stack, which gives an overview of how the application is structured, and by viewing the Application definition rule, which provides detailed information about the application's setup and its components. References: Pega Platform Help - Application Layers.

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

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.

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.

To enable property-level encryption for sensitive data such as SSN and Account Number, you create an Access Control Policy of type PropertyEncrypt. This policy specifies which properties should be encrypted and how the encryption should be applied. References: Pega Platform Help - Access Control Policies.

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.

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.

• A: Running the process to completion before capturing PAL readings is important because it ensures that all the necessary rule assemblies have taken place. If you measure performance without doing this, the rule assembly might skew the results by adding additional overhead.
• B: Capturing PAL readings after significant changes to a process helps in identifying any performance impacts due to those changes. This allows you to compare the performance data before and after changes to assess their impact. References: Pega official documentation on Performance Analyzer (PAL).

Application Settings allow you to store references to an external system connected to an application. These settings can be used to manage environment-specific parameters such as URLs, file paths, and other data that may vary between development, testing, and production environments. References: Pega official documentation on application settings.

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.

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.

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.

In a Pega Web Mashup, valid ways to exchange data include using an action object configured as a script to perform additional actions on a web mashup gadget (A), utilizing the Javascript function doAction() to set or read data values through the hosting web page (B), and using the data-pega-event-onpagedata attribute to configure default values for the gadget (E). These methods facilitate dynamic interaction between the mashup and the hosting web page, allowing for seamless data exchange and integration of Pega functionalities into external web applications.References: Pega Community documentation on Pega Web Mashup and integration techniques.

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.

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

For a courier company requiring a mobile app to work in remote areas without internet access, a signed app is the best solution. Signed apps are authorized by a certificate authority, ensuring their authenticity and integrity. These apps can be designed to operate in offline mode, storing data locally when there's no internet connection and syncing it back to the server once connectivity is restored. This capability is crucial for field operations in remote areas, ensuring uninterrupted app functionality and data collection.References: Pega Community documentation on mobile app development and offline capabilities.

The Tracer tool is designed to debug the execution of rules by providing detailed runtime information about each step within a rule. This allows you to identify performance issues at the step level within an activity. References: Pega Platform Help - Tracer Tool.

To include access groups in your Product rule, you can add the access groups to the application record, which incorporates all the necessary rules for the application. Additionally, you can add the access group directly to the Product rule in the 'Individual instances to include' section, which allows you to specify individual rules and data instances that the Product rule should include. References: Pega Platform Help - Creating a Product rule.

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 where service level intervals vary according to multiple criteria (passenger status, class of service, and fare type), you would create a multivariate circumstanced rule, a circumstance definition, and a circumstance template. This allows you to create SLAs that vary based on the combination of these criteria. References: Pega official documentation on circumstancing rules.

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.