PEGACPSSA23V1 Sample Questions Answers

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.

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.

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.

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

The requirement is to handle an error when it occurs and perform two actions: display a message to the user and send an email to the administrator. This can be done by configuring an error handling process that encapsulates both actions. Typically, this would involve configuring a flow or an activity that runs when an error occurs, and it would handle both displaying the error message to the user and sending the email. References: Pega Platform Help - Error Handling.

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

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.

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.

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.

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.

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.

Managing encrypted data in Pega Platform comes with certain limitations, one of which is that encrypted properties cannot be referenced using filter conditions in reports (A). This is because the encryption obscures the actual value of the property, making it impossible for the reporting engine to perform comparisons or filtering based on the encrypted data. This limitation is essential for maintaining data security, as it prevents unauthorized access to sensitive information through report queries.References: Pega Community documentation on encryption and reporting.

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

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.

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.

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.

Connectors establish a link to a service on another system (B). They are designed to communicate with external systems, such as sending a request to a web service or a REST service, and handle the response within a Pega application. This capability is part of Pega's integration features and enables the application to interact with multiple systems across different platforms.References: Pega Community documentation on connectors and integration.

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

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.

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.

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.

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

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.

• Inbound request received
• Map inbound data
• Request processing
• Map outbound data
• System returns a response

This sequence represents the typical flow of processing an inbound service request, from the initial receipt of the request to the final response after the necessary processing and mapping have been completed.

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.

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.

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.

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.

• A: Configuring a class join on the report definition allows you to join the operator information to each case, enabling you to list the user ID of the manager associated with the operator who creates a time-off case.
• C: Using an association rule to join operator information to each case accomplishes the same objective by defining a reusable join that can be referenced in multiple reports. References: Pega official documentation on report definitions and associations.

Graphical user interface, application Description automatically generated

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.

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.

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.

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.