Pegasystems PEGACPSSA23V1 Certified Pega Senior System Architect 23 Exam Practice Test

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.

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.

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

At 4.5 hours after the case reaches the assignment, the SLA would have passed the goal and deadline, and entered the passed deadline period. The initial urgency is 15, the goal adds 10 (total 25), and the deadline adds 15 (total 40). After the passed deadline, the urgency increases by 10 every hour up to a limit of 10 events. By 4.5 hours, there would have been two passed deadline events, adding 20 to the urgency, leading to a total urgency of 60. References: Pega Platform Help - Service Level Agreements.

A native app is suitable for remote areas without internet access because it can be installed on the device and has the capability to function offline. This allows the courier company employees to scan and track parcels regardless of internet connectivity. References: Pega Mobile Client Developer Guide.

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.

• A: When using a Pega Web Mashup, leveraging the standard authentication service IACAuthentication and updating the authentication activities to match the external system's requirements is a common practice.
• D: Configuring application permissions by specifying a list of trusted domains in the application rule is important for security purposes and to control which external domains are allowed to embed the mashup. References: Pega official documentation on Pega Web Mashup configuration.

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.

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.

To report potholes through a mobile application using the Pega API, the POST/cases method would be used to submit the report case, and the GET/casetypes method would be used to access the related case type to ensure the correct case type is used for the report. References: Pega Platform API Guide.

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.

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.

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.

For each scenario, the appropriate mobile application solution is as follows:

• "SDK application" is suitable for Globobank's scenario because they want to build a mobile app of its Pega Platform application to embed in its mobile app. The SDK would allow them to integrate Pega's capabilities within their existing mobile application environment.
• "Signed application" is needed for Metrobank, which wants to distribute their mobile app on Android and iOS app stores. For an application to be accepted on these platforms, it must be properly signed with a developer certificate.
• "Unsigned application" fits the scenario for Localbank, as they want to build a mobile app for a Pega Platform application but cannot distribute developer certificates to app developers. An unsigned application does not require these certificates, allowing development to proceed without them.

Based on these explanations, here are the matched solutions:

• SDK application -> Globobank wants to build a mobile app of its Pega Platform application to embed in its mobile app.
• Signed application -> Metrobank wants to build a mobile app for distribution on Android and iOS app stores.
• Unsigned application -> Localbank wants to build a mobile app for a Pega Platform application, but developer certificates cannot be distributed to app developers.

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.

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.

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.

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.

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.

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.

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 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 include access groups in your Product rule, you can add the access groups to the application record, which incorporates all the necessary rules for the application. Additionally, you can add the access group directly to the Product rule in the 'Individual instances to include' section, which allows you to specify individual rules and data instances that the Product rule should include. References: Pega Platform Help - Creating a Product rule.

To ensure that the values are only initiated once for each flow action, add logic to the pre-processing data transform to test if the values were already initiated (A). This logic can prevent the reinitialization of values that have already been set, allowing the pre-processing to only set default values when they are not present, avoiding any unwanted overwrites or duplications of effort.References: Pega Community documentation on data transforms and flow action pre-processing.

To ensure that only HR Managers have read access to a candidate's reference letter attachment, the tasks involved include restricting read access according to a When condition (B) and configuring attribute-based access control on the Attachment Category (C). The When condition can specify criteria that must be met for the attachment to be accessible, such as the user's role being an HR Manager. Attribute-based access control allows for the definition of access rules based on attributes of the data or user, providing a flexible and granular approach to securing sensitive attachments like reference letters.References: Pega Community documentation on attachment security and attribute-based access control.

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.

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.

When integrating multiple Pega Web Mashups into a single page, it is necessary to identify unique names for each mashup to ensure that they are embedded and function independently without conflict on the client's page. References: Pega Platform Help - Pega Web Mashup.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.