Free Practice Questions for Pegasystems PEGACPSSA23V1 Exam

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.

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

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.

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.

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.

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.

To satisfy the requirement that users assigned the role "Manager" can edit objects related to any studio work, the Access of Role to Object (ARO) record should be configured at the "UPlusMusic-Production-Work-Studio-" level (C). This level is the common parent class for all studio-related work, such as Recording and Editing. By setting the ARO at this level, it ensures that managers have the necessary permissions to edit any object that falls under the studio work hierarchy, without having to set permissions at each individual subclass level.References: Pega Community documentation on class hierarchy and Access of Role to Object configuration.

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.

The Purge/Archive wizard in Pega Platform is appropriately used to remove old cases to reduce the size of a database table (B). Over time, completed or resolved cases can accumulate in the system, leading to large table sizes that can negatively impact application performance. By archiving these cases, you can move them out of the primary database tables into an archive, and by purging, you can delete cases that are no longer needed. This process helps maintain optimal database performance and manage storage costs effectively.References: Pega Community documentation on the Purge/Archive wizard and database maintenance best practices.