PEGACPSSA23V1 Certified Pega Senior System Architect 23 Exam Questions and Answers

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.

The Purge/Archive wizard in Pega Platform is appropriately used to remove old cases to reduce the size of a database table (B). Over time, completed or resolved cases can accumulate in the system, leading to large table sizes that can negatively impact application performance. By archiving these cases, you can move them out of the primary database tables into an archive, and by purging, you can delete cases that are no longer needed. This process helps maintain optimal database performance and manage storage costs effectively.References: Pega Community documentation on the Purge/Archive wizard and database maintenance best practices.

Keyed data pages can return multiple embedded pages if the data structure includes lists or other page structures. They can also have multiple keys, which allows them to return data based on a combination of key values. References: Pega Platform Help - Data Pages.

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.

When analyzing a data transform that is exceeding preferred performance parameters, the Performance Analyzer (PAL) (C) is the most suitable tool to use. PAL provides detailed metrics on various aspects of system performance, including CPU usage, database interactions, and rule execution times. By using PAL to analyze the performance of a data transform, you can identify specific areas where inefficiencies occur, such as excessive database reads or writes, loop iterations, or other resource-intensive operations. This insight allows for targeted optimizations to improve the performance of the data transform and the overall application.References: Pega Community documentation on Performance Analyzer (PAL) and performance troubleshooting.

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.

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.

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

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.

The correct configuration for two parallel cases that run independently is the Subprocess shape with the Spinoff flow option enabled (Option C). This allows the Retirement planning case to proceed in parallel without waiting for, or reporting to, the Account review case. References: Pega official documentation on case design and flow shapes.

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.

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.

Controlling access to an attachment category can be achieved through various configurations. Using a When condition like "IsCurrentStageTesting" (A) allows for dynamic access control based on the case's current stage, enabling attachments to be accessible only under certain conditions. Assigning privileges, such as "DeleteOwn" (C), to users enables fine-grained control over actions users can perform on attachments, such as deleting their own attachments, thus enhancing security and compliance with business rules.References: Pega Community documentation on attachment categories and access control.

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.

• 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 multiple teams can update the same application version without affecting each other's work, the following actions are recommended:

• B: Create branches for each team's application. This allows teams to work on isolated versions of the application and merge their changes when ready.
• D: Create a new application for each team built on the base application. This creates separate instances of the application for each team to work on, which they can then synchronize with the base application as needed. References: Pega official documentation on branch rulesets and application development.

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

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

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.

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.

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.

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.

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.

Building a mobile app from a Pega Platform application requires configuring certain key components for security and connectivity. Creating a certificate set (A) is essential for securing the app, ensuring that communications between the mobile app and the server are encrypted and authenticated. Configuring access to the Pega Mobile Build Server (B) is necessary for the app build and distribution process, allowing the Pega application to package and deploy mobile apps through Pega's cloud-based build service.References: Pega Community documentation on mobile app development and deployment.

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.

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

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.

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.

Pega Web Mashup is ideal for scenarios where minimal resources are available for updating the Pega Platform with each new release, as it allows external applications to embed Pega UI elements with minimal maintenance. Additionally, it's useful when users are expected to create cases, open assignments, and manage data privacy within an embedded Pega frame in an external web page. References: Pega Platform Help - Pega Web Mashup.

Access of Role to Object (ARO) is used to define the level of access that a role has to instances of a class. In this case, an ARO can be created for the car dealers' role to restrict modify access to orders in the Fulfillment stage. References: Pega Platform Help - Security.

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.

Building mobile applications with Pega Platform, it's true that the Pega Mobile Build Server is configured in Dev Studio using your Android or iOS developer certificates (B). This server is a cloud-based service provided by Pega to facilitate the mobile app build process. It's also true that the Pega Mobile Build Server requires HTTPS access (D) to ensure secure communication during the build process.References: Pega Community documentation on mobile app development and Pega Mobile Build Server configuration.

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.

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.