PEGACPSSA23V1 Practice Exam Questions with Answers Certified Pega Senior System Architect 23 Exam Certification

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.

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.

To prevent the application from using the rule in TRB-HRApps-Work-Feedback, you would save an additional new version of the flow action applied to TRB-HRApps-Work-Feedback and set the availability to "Withdrawn". This marks the rule as no longer valid for use in the application. References: Pega official documentation on rule availability.

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.

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.

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.

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.

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

To create a custom status named Open-Review to be applied to assignments in one application, create a Field Value record named Open-Review for .pyStatusWork with the Apply To class set to the class group (A). This approach allows you to customize the status values used in your application and ensure that they are available for use in assignments within the specified class group, which typically corresponds to an application.References: Pega Community documentation on Field Value records and status values.

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.

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.

In Application Settings, you can specify different values for production levels using text (e.g., URLs, file paths) or picklists (for selecting from predefined options). These settings allow for easy adjustment of values according to the environment the application is running in. References: Pega Platform Help - Application Settings.

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.

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

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.

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

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.

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.

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.

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 copy items selected by a user to a page list property when the user submits the form, add a data transform to the flow action as a post-processing action (A). Post-processing actions occur after the user submits the form, making it the right moment to transfer the selected items into the page list property for further processing or storage.References: Pega Community documentation on data transforms and flow action post-processing.

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.

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

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.

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

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.

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.

A class group is used to associate child classes with a single database table. This mechanism is known as class table inheritance, where instances of different but related concrete classes that belong to the same class group are stored in the same database table. References: Pega official documentation on class groups and class inheritance.

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