PEGACPSSA23V1 Certified Pega Senior System Architect 23 Exam Questions and Answers

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.

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.

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.

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.

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. Ref erences: Pega official documentation on the Application Guardrails landing page and guardrail scores.

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.

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.

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.

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

An association rule differs from a class join in that it is a reusable rule that can be used by anyone with appropriate permissions when creating reports. This makes it available across multiple reports. Class joins, on the other hand, are specific to each report definition and are not reusable in the same way. References: Pega Reporting Guide - Associations vs. Joins.

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.

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.

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.

To start operations at a specific GMT time regardless of where the server is located, you would use the Queue-For-Processing method in an activity. This method adds a task to a queue to be processed either by a standard or a dedicated queue processor. A dedicated queue processor can be configured to operate on a schedule, so it can start processing at midnight GMT. References: Pega SSA course materials on queue processors and timed events.

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 major skim operation copies rules from the highest minor version of the current major version of a ruleset to create a new major version. In this scenario, the ruleset being skimmed is ABC:02-02-01, indicating that the current major version is 02.

Given this, the ruleset versions that would be used by the skim operation to copy rules into ABC:03-01-01 would be the highest minor versions within the major version 02.

02-01-01 : This is not the highest minor version (since we have 02-02-01), so it would not be used. The answer should be " No. "

01-02-01 : This is from a different major version (01), so it would not be used. The answer should be " No. "

02-01-05 : Despite having a higher patch version, it belongs to the minor version 01 within the major version 02. Since we have a higher minor version 02, this would not be used. The answer should be " No. "

Only the highest minor version from the current major version (in this case, 02-02-01) is used for the skim operation to create the new major version ABC:03-01-01. If the ruleset version 02-02-01 were listed, the correct answer would be " Yes " for that version, but as it is not listed, none of the provided ruleset versions would be used in this skim operation.

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.

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.

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.

A Declare OnChange rule is designed to perform an action when a specified property changes. The action that a Declare OnChange rule can perform includes executing a data transform, which allows for the automated update of properties when a change is detected in the specified property. References: Pega official documentation on Declare OnChange rules.

In Pega Platform, when configuring multiple pre-processing actions on a single flow action, the order of execution is as follows:

Execution Order:

Apply data transform

Run activity

Run robotic automation

This sequence is based on the typical order in which Pega processes these types of actions: data transforms are applied first to set initial values or transform the data as needed, followed by the execution of any activities for more complex processing, and finally, any configured robotic automation is run.

To ensure that the advisor and the student can simultaneously edit the draft proposal, configure the locking on the case type to allow multiple users (B). This setting enables a shared access model, where multiple users can work on the case at the same time. Additionally, Pega ' s conflict resolution mechanisms can be utilized to check for changes before committing them to the database, ensuring that any concurrent edits are properly managed and the integrity of the proposal is maintained. References: Pega Community documentation on case locking and concurrent editing.

Performance-related alerts are recorded in the ALERT log. This log contains entries for operations that exceed specified performance thresholds, providing insights into potential performance issues. References: Pega Platform Help - System Logs.

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.

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.

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 rule types that you can mark as relevant records are those that are frequently referenced and are of high importance in the application. Reports (B) and Sections (D) can be marked as relevant records to easily access and modify these important rules. References: Pega official documentation on relevant records.

The purpose of the Policy Verification landing page in Pega Platform is to test if a user has the required access to a case (A). This tool allows administrators and developers to verify access control policies by simulating how the policies would apply to different users, ensuring that the security configurations align with the application ' s requirements and that users have appropriate access levels to cases and data. References: Pega Community documentation on security policies and Policy Verification tool.

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.

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.

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.

To resolve performance issues caused by resource-intensive queue processors, it ' s essential to ensure that these processors are associated with appropriate node types (A) and that application nodes are configured with node types (D). Associating queue processors with specific node types allows for the distribution of workload across the application infrastructure, optimizing resource utilization and improving performance. Configuring application nodes with node types ensures that tasks are executed on the most suitable nodes, further enhancing system efficiency and scalability. References: Pega Community documentation on queue processors and node types.

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.

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.

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.

Dedicating and classifying a node for the job scheduler allows the job scheduler to run on a node that is optimized for batch processing. This ensures that resource-intensive jobs do not impact the performance of the user nodes, thus maintaining peak performance at all hours. References: Pega Platform Help - Job Schedulers.

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.