PEGACPSSA23V1 Certified Pega Senior System Architect 23 Exam Question and Answers

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

A keyed data page is best used for data that does not change frequently and can be retrieved by a unique key. A long list of vehicle parts that rarely changes fits this criterion because the data can be cached and doesn't require frequent updates, optimizing performance. References: Pega Platform Help - Data Pages.

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.

An edit validate rule is used to ensure that data is entered in a specific format. For membership numbers that need to match a particular pattern (M-######-0#), an edit validate rule would be the appropriate mechanism to enforce this format upon entry. References: Pega Platform Help - Edit Validate.

Pega Mobile Client supports leveraging various mobile device features to enhance app functionality and user experience. Barcode scanning (A) is commonly used in logistics and retail applications for quick identification and tracking of items. Biometric identification (C), such as fingerprint or facial recognition, adds an extra layer of security for user authentication. Push notifications (D) are crucial for real-time communication, alerting users to updates or required actions within the app, even when the app is not actively in use.References: Pega Community documentation on Pega Mobile Client 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 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.

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.

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.

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.

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.

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.

When two teams work on different enhancements within the same ruleset and wish to keep their work separate, the best practice is to create a new ruleset version for one of the teams and to use branch rulesets for each team. This allows for parallel development without interference, and the teams can merge their work back into the main ruleset when they're ready. References: Pega best practices for parallel development.

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

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 implement the requirement of associating users in different units to the same work queue, you associate the users to a common work group and then associate a work queue to that work group. This allows users from different units, who are part of the same work group, to access the same work queue. References: Pega official documentation on work groups and work queues.

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.

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.

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.

Rule resolution will choose the rule that is most specific to the circumstances of the case. Since the country is set to Japan, the rule resolution algorithm will choose the rule version that is circumstanced for Japan. Among the options, 01-01-02 is the circumstanced rule that matches the country condition of Japan and would be selected over the base rule and any other versions. References: Pega Platform Help - Rule Resolution.

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.

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

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

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.

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.

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.

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.

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

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

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.

Using a data page with a predefined key enhances performance by leveraging the caching mechanism of Pega. When a data page is loaded with a specific key, it is stored in memory. Subsequent accesses to the data page with the same key do not require fetching the data again from the external data source, significantly reducing the access time. This approach is particularly beneficial in cloud deployments where network latency can impact performance. It ensures that once the data for a particular customer is fetched and stored in the cache, accessing the same customer's information again is much faster, addressing the performance issue reported.References: Pega Community documentation on data pages and performance best practices.

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

Branched rulesets are used when multiple teams need to work on the same application version simultaneously. Each team can work in their own branch, allowing for concurrent development without affecting the main application until the branches are merged. References: Pega Platform Help - Branched Rulesets.

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.