Pegasystems PEGACPSSA23V1 Certified Pega Senior System Architect 23 Exam Practice Test

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

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.

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.

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.

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.

When deploying mashup code in a webpage, it is necessary to add the host URL in the Pega application to ensure that Pega Platform accepts incoming requests. This is part of configuring the trusted origins within the application's settings. References: Pega official documentation on Pega Web Mashup deployment and configuration.

Graphical user interface, application Description automatically generated

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.

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.

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.

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.

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.

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.

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

To allow both doctors and nurses to modify cases while complying with the identified security requirements, the best approach is to create a single access role for both doctors and nurses (C) and set the modify action to 5. This configuration grants both user groups the necessary permissions to modify cases throughout the case life cycle. By using a single access role with a high level of access for modifications, the application simplifies role management while ensuring that both doctors and nurses can perform their duties effectively, without compromising the security and integrity of patient cases.References: Pega Community documentation on Access Role to Object and case management best practices.

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.

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.

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.

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.

When configuring Pega Web Mashup, it's essential to create one DIV element in the hosting web page for each Pega gadget (A), ensuring that each gadget is properly isolated and rendered within its designated area on the web page. Additionally, adding a list of trusted domains in your application settings (B) is crucial for security, as it specifies which domains are authorized to host the mashup, preventing unauthorized use or embedding of the Pega functionalities in untrusted environments.References: Pega Community documentation on Pega Web Mashup configuration and security best practices.

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.

When considering post-processing actions on a flow action, it's crucial to understand their implications on the user experience and system behavior. The effect if the flow action is reloaded (A) is important because post-processing actions might not execute again, leading to inconsistent data or user experience. The sequence in which the system runs different actions (B) is critical to ensure that data transformations and business logic are applied in the correct order, maintaining data integrity and consistency. The timing of the commit for the flow action (C) influences transaction management, ensuring that all changes are saved correctly and that the system maintains data consistency, especially in multi-user environments.References: Pega Community documentation on flow actions and post-processing.

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

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.

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.

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

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.

When a report is created in a class group (MyCo-HR-SelfService-Work), it will return instances of its child classes (MyCo-HR-SelfService-Work-TimeOff and MyCo-HR-SelfService-Work-Expense) unless those child classes are stored in different database tables due to class table inheritance or other data storage configurations. References: Pega official documentation on reporting and class groups.

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

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: Each rule in Pega can indeed have multiple guardrail warnings. These warnings indicate the degree to which the rule deviates from Pega's best practices.
• C: Pega Platform performs a guardrail examination when a rule is saved. This is to ensure that developers are immediately aware of any potential issues that may arise from the rule they are creating or modifying. References: Pega official documentation on compliance score and guardrails.

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.

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.

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

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.