Pegasystems PEGACPSSA23V1 Certified Pega Senior System Architect 23 Exam Practice Test

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.

When creating a new major version of an application ruleset, you would use the Ruleset Maintenance wizard to skim the relevant ruleset versions. This process copies the highest version of existing rules to the new ruleset version, effectively creating the new major version. References: Pega official documentation on ruleset skimming.

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 satisfy the requirement that employees cannot see complaints made against themselves, an Access Control Policy (B) is the most suitable security solution. Access Control Policies in Pega allow for the definition of conditions under which access to certain data or cases is granted or denied. By configuring a policy that checks the relationship between the complaint and the employee (such as matching IDs), the system can dynamically restrict access to sensitive information, ensuring compliance with auditing policies.References: Pega Community documentation on Access Control Policies.

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

To support accessibility, it's recommended to use a calendar control that displays an entire month. This allows users who rely on screen readers or keyboard navigation to select a date without the need for precise mouse control or having to manually input the date, which can be error-prone. References: Pega User Interface Design Guide - Accessibility.

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.

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.

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.

Graphical user interface Description automatically generated

To match the security solutions to their appropriate use cases:

• "Access of Role to Object" is typically used to specify what actions a particular role can perform on instances of a class. It would be appropriate for a use case where "Dealers can modify evaluations" since this is an action that a specific role (dealers) would be allowed to perform.
• "Access Control Policy" allows defining rules that enforce property and case access restrictions based on the user role and other conditions. It would be appropriate for a use case where "Customers can only view their own credit report" since this would be a restriction based on user-specific data.
• "Access Deny" is used to explicitly deny access to a rule or data instance. It fits the use case where "Dealers cannot run reports" because it is a restriction that prevents a specific action (running reports) for a specific role (dealers).
• "Access when" is a rule that defines conditions for whether certain access is allowed. It would be used in the scenario where "Dealers cannot modify orders in the Fulfillment stage" since this is a conditional restriction based on the stage of the process.

Based on these explanations, here is the matched list:

• Access when -> Dealers cannot modify orders in the Fulfillment stage.
• Access Control Policy -> Customers can only view their own credit report.
• Access Deny -> Dealers cannot run reports.
• Access of Role to Object -> Dealers can modify evaluations.

• A: Configuring a class join on the report definition allows you to join the operator information to each case, enabling you to list the user ID of the manager associated with the operator who creates a time-off case.
• C: Using an association rule to join operator information to each case accomplishes the same objective by defining a reusable join that can be referenced in multiple reports. References: Pega official documentation on report definitions and associations.

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.

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

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.

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.

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.

Managing encrypted data in Pega Platform comes with certain limitations, one of which is that encrypted properties cannot be referenced using filter conditions in reports (A). This is because the encryption obscures the actual value of the property, making it impossible for the reporting engine to perform comparisons or filtering based on the encrypted data. This limitation is essential for maintaining data security, as it prevents unauthorized access to sensitive information through report queries.References: Pega Community documentation on encryption and reporting.

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 handle the unavailability of a system of record when using a SOAP connector, the most effective approach is to implement the retry logic in the connector's error handler flow. This flow can be configured to wait for a specified duration (in this case, an hour) before retrying the connection. If the system remains unavailable after the retry, the flow can then proceed to send a notification to the system administrator. This approach encapsulates the error handling logic within the connector's flow, making it reusable and maintainable.References: Pega Community documentation on connector error handling and SOAP connectors.

• A: Configuring a process with a decision shape that continues if the TestThreshold Configuration setting is less than the applicant's test score supports the requirement for automatic case advancement based on standardized test scores.
• B: Configuring a TestThreshold Configuration setting with the national average for the test score threshold allows for the necessary comparison to determine if a case should advance automatically. References: Pega official documentation on decision shapes and configuration settings.

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

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.

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.

Sixteen hours after the case reaches the assignment, the assignment urgency is calculated as follows: Initial urgency (20) + Urgency after goal (10) + Urgency after deadline (20) + Urgency after passing the deadline (2 hours passed, urgency increases by 20, and this event repeats for the limit of 5 times, so 20x5=100). Adding these together: 20 + 10 + 20 + 100 = 150. However, since none of the options matches this calculation, there might be an error in the given options or a misinterpretation of the question. Based on the provided options, 90 would be the closest, indicating a possible oversight in the question. References: Pega official documentation on Service Level Agreements (SLAs) and urgency calculations.

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

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

System exceptions and errors are typically logged in the Pega log. This log captures information about the functioning of the Pega platform and the applications running on it, including system errors and exceptions that users encounter. References: Pega System Administration documentation on log files.

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.

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.

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.

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

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

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.

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

The cache manifest in a mobile app facilitates the use of the app while offline by allowing the download of rules and static resources. This ensures that users can access the app's functionality and interface elements even when they do not have an internet connection. References: Pega Mobile Client Developer Guide.

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.