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.

Performance-related alerts are recorded in the ALERT log. This log contains entries for operations that exceed specified performance thresholds, providing insights into potential performance issues. References: Pega Platform Help - System Logs.

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

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.

When a report is created in a class group (MyCo-HR-SelfService-Work), it will return instances of its child classes (MyCo-HR-SelfService-Work-TimeOff and MyCo-HR-SelfService-Work-Expense) unless those child classes are stored in different database tables due to class table inheritance or other data storage configurations. References: Pega official documentation on reporting and class groups.

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

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.