PEGACPSSA23V1 Sample Questions Answers

When adding a Split for Each shape to your case life cycle, you must specify the Page List or Page Group property that forms the basis of the split and define when the parent process resumes processing after the iterations of the subprocess are complete. References: Pega Platform Help - Case Design.

The primary purpose of a production ruleset is to allow rules to be updated in a production environment. Production rulesets are designed to hold rules that business users can modify directly in a production environment without requiring a deployment from development through testing environments. This enables quick changes to be made to decision tables, correspondence, and other rule types that business users are permitted to change. References: Pega official documentation on ruleset types.

The recommended practice is to set the Access time-out value for the child case to be greater than the parent case time-out value. This ensures that the child case does not become inaccessible due to a time-out while the parent case is still active, which could happen if it had the same or a shorter time-out value. References: Pega official documentation on locking strategies and time-out values.

• A: The Application Guardrails landing page does count the number of rules with severe or moderate warnings, as these can have a significant impact on the application's performance and maintainability.
• B: Guardrail scores exclude Pega Platform core rules since these are established by Pega and are assumed to be optimized.
• C: The landing page also counts the number of rules with no warnings or caution-level warnings, which contribute positively to the overall compliance score. References: Pega official documentation on the Application Guardrails landing page and guardrail scores.

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 ensure that only a manager can run a specific flow action, the best approach is to add a privilege to the flow action form (B) and then assign this privilege to a role that is exclusive to managers. This role is then associated with the access group designated for managers. Privileges provide a granular level of security that can be used to control access to specific actions within a Pega application, such as executing a flow action. By leveraging privileges, you can ensure that only users with the manager role, who possess the necessary privilege, can execute the flow action, thereby enforcing the desired level of access control.References: Pega Community documentation on privileges, roles, and access groups.

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.

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.

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.

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 enable the attending doctor to update the Patient visit case while the Lab analysis and Diagnostic imaging child cases are active, the following configurations are necessary:

• A: Configuring the Patient visit case type to allow multiple users ensures that more than one user can work on the case simultaneously, which would allow the doctor to update the case with notes even while the child cases are in progress.
• B: Configuring the Lab analysis and Diagnostic imaging case types to allow other users to open the parent case type ensures that opening the child cases does not lock the parent case, allowing the doctor to make updates concurrently. References: Pega official documentation on case type configuration and locking strategies.

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

Rule resolution in Pega follows the "Rule Resolution" algorithm, which will look for the rule that best matches the class hierarchy and the ruleset list. In this scenario, the rule that matches the Apply to: class of TGB-HR-SelfService-Work-TimeOff and is in the highest listed ruleset that is available (SelfService) will be selected. References: Pega SSA course materials on rule resolution.

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.

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

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.

Pega Mobile Client supports leveraging various mobile device features to enhance app functionality and user experience. Barcode scanning (A) is commonly used in logistics and retail applications for quick identification and tracking of items. Biometric identification (C), such as fingerprint or facial recognition, adds an extra layer of security for user authentication. Push notifications (D) are crucial for real-time communication, alerting users to updates or required actions within the app, even when the app is not actively in use.References: Pega Community documentation on Pega Mobile Client capabilities.

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 satisfy the requirement that users assigned the role "Manager" can edit objects related to any studio work, the Access of Role to Object (ARO) record should be configured at the "UPlusMusic-Production-Work-Studio-" level (C). This level is the common parent class for all studio-related work, such as Recording and Editing. By setting the ARO at this level, it ensures that managers have the necessary permissions to edit any object that falls under the studio work hierarchy, without having to set permissions at each individual subclass level.References: Pega Community documentation on class hierarchy and Access of Role to Object configuration.

To allow delegation of a decision table, you should save it in a Production ruleset. Production rulesets are designed to hold rules that business users can modify directly in a production environment, which includes delegated rules. References: Pega official documentation on ruleset types and rule delegation.

To support offline use of applications on mobile devices, you should source UI elements such as drop-down lists using data pages, which can be configured to be available offline. This allows the application to use locally cached data to populate the UI elements even when the device is not connected to a network. References: Pega Mobile Developer Guide on offline capabilities.

For each scenario, the appropriate mobile application solution is as follows:

• "SDK application" is suitable for Globobank's scenario because they want to build a mobile app of its Pega Platform application to embed in its mobile app. The SDK would allow them to integrate Pega's capabilities within their existing mobile application environment.
• "Signed application" is needed for Metrobank, which wants to distribute their mobile app on Android and iOS app stores. For an application to be accepted on these platforms, it must be properly signed with a developer certificate.
• "Unsigned application" fits the scenario for Localbank, as they want to build a mobile app for a Pega Platform application but cannot distribute developer certificates to app developers. An unsigned application does not require these certificates, allowing development to proceed without them.

Based on these explanations, here are the matched solutions:

• SDK application -> Globobank wants to build a mobile app of its Pega Platform application to embed in its mobile app.
• Signed application -> Metrobank wants to build a mobile app for distribution on Android and iOS app stores.
• Unsigned application -> Localbank wants to build a mobile app for a Pega Platform application, but developer certificates cannot be distributed to app developers.

• A: Calling the function pega.web.api.doAction() allows for specific actions to be performed in the Pega application from the web mashup, such as refreshing a section or submitting an assignment.
• D: Using the attribute data-pega-event-onpagedata allows for passing data from the web mashup to the Pega application when specific events occur on the page. References: Pega official documentation on Pega Web Mashup methods and attributes.

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.

Graphical user interface, application Description automatically generated

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

In Pega's Enterprise Class Structure (ECS), standard functionalities that are shared across multiple applications within an organization, such as sending a confirmation email, should be placed at the Organization layer. This allows for reusability and standardization across various implementations within the organization. References: Pega best practices for class design and ECS.

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.

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

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.

When creating a pre-processing data transform, you should consider the timing of the commit for the flow action and the effect if the flow action is reloaded. These factors can impact how the data transform processes data and how it integrates with the flow action's lifecycle. References: Pega Platform Help - Data Transforms.

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.

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.

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.

Application settings are used to point to external resources that can change without requiring changes to the application code. For example, a weather service application might use application settings to specify the URL of a web service for weather data. References: Pega Platform Help - Application Settings.

The Performance Analyzer (PAL) is the correct tool to gather and analyze performance data for the form submission that takes a significant amount of time. PAL tracks the interaction with the Pega Platform and provides metrics related to the performance of activities, rules, and system functions over time, which is essential for identifying the cause of the delay during form submission. References: Pega official documentation on PAL.

Attribute-based access control (ABAC) supports various granular and dynamic access control requirements, such as allowing managers to reschedule but not delete appointments (A) and enabling bakers with a rating of 4 or better to add recipes to the database (D). ABAC uses attributes (such as user roles, data characteristics, and environmental conditions) to define access control policies, providing a flexible and context-aware mechanism to enforce security policies tailored to specific business requirements.References: Pega Community documentation on ABAC and its use cases.

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.

Pega best practices recommend keeping activities short to enhance maintainability and readability. Custom Java steps should be limited to reduce complexity and potential errors. Activities should also be limited in general, with preference given to other rule types that are more declarative and less procedural, like data transforms, to improve application performance and maintainability. References: Pega SSA course materials on activity best practices.