Pega PRPC Platform Administration Quiz

In Pega, the standard class groups that contain process commander by default on installation are PegaAccel (accelerator), Data-Admin (administrative data), and History-PegaSample (sample history data). Work-Cover, PegaSamples, and Work-Folder are not default process commander class groups.

Context-sensitive Declarative Expressions are used for embedded data, not context-free ones. Context-free expressions operate on pages and properties but don't have the context awareness needed for embedded data processing.

In Pega, alert levels for the PegaAlert log are configured in the prconfig.xml file, which is the main configuration file for Pega platform settings. The other files listed serve different purposes.

Local variables are limited to the execution scope of a single activity and cannot be passed between different activities. The other statements are true: local variables cannot be traced in Tracer, and parameter pages are not visible in the clipboard viewer, making the first statement the false one.

Once a ticket is raised in Pega, you cannot automatically resume from the exact point where the ticket was invoked. The ticket creates a break in processing that requires manual resolution or workflow intervention to continue.

Pega automatically maintains history tables for work items (History-Work-), configurations or data instances (History-Data-), and rule modifications (History-Rule-). Therefore, history records are created across all of these categories, making the options specifying individual classes too narrow and All of the Above correct.

In Pega, SLAs (Service Level Agreements) can be defined for work objects but NOT for individual assignments. SLAs track time compliance at the work object level, not at the assignment level.

Pega alerts and their threshold configurations are traditionally managed within the prconfig.xml file. The other options are incorrect: prlogging.xml controls logging configurations, prweb.xml handles web deployment descriptors, and System Settings rules are not the standard location for these configuration parameters.

Activities (Rule-Obj-Activity) contain complex logic and code that should not be delegated to business users. Decision tables, decision trees, and map values are designed for business user delegation as they provide visual, rule-based interfaces without code.

To create a zip archive containing rules in Pega, you use File > Export Archive from the Developer Portal. Rule-Admin-Product is for product rules, and the Delete a RuleSet option is for deletion, not archiving.

In PEGA PRPC, rules can be specialized by combining Class and Circumstances. The Class determines the rule's position in the class hierarchy, while Circumstances provide conditions for when the rule applies. Option D ('a&c' meaning Class & Circumstances) correctly identifies both mechanisms needed for country/state-specific specialization.

In Pega, a circumstance rule represents a specialization of a base rule. Because a circumstance rule cannot exist without inheriting from or overriding a base definition, the system requires a base rule to be created first, making the True option incorrect and False correct.

RuleSet prerequisites are NOT part of rule resolution (the 6 R's) and are NOT enforced during runtime. Prerequisites are design-time constraints used for packaging and rule validation, not runtime rule selection. The rule resolution process operates on rules already available in the system; prerequisites ensure proper packaging during development.

In PEGA PRPC v5.5 and later, agents can run in Standard mode (processing work from database queues) and Advanced mode (processing assignments and supporting additional features like service processing). Legacy mode refers to pre-v5.5 behavior. The correct answers are Standard and Advanced.

The Rule Instance Cache is an in-memory cache that stores the XML representation of frequently accessed rules to improve performance. It caches the rule definition (XML), not the generated code or instantiated objects. This is distinct from First Use Assembly cache which caches generated Java code.

PLA (Pega Landing Area) provides overall health monitoring and diagnostics for PEGA applications. PAL (Performance Analyzer) focuses on performance metrics. SMA (System Management Application) is for cluster management. Preflight checks deployment readiness. PLA is the comprehensive health check tool.

CPU counters for PAL rely on JVM capabilities and operating system support, meaning they are not universally available across all platforms. The False option is correct because PAL cannot guarantee these counters are active on every server setup, and distractors suggesting otherwise are incorrect.

Alerts should NOT be disabled in production systems. Alerts provide critical visibility into system issues, performance problems, and errors. Disabling them would remove essential monitoring capability, making it impossible to detect and respond to production issues. Production environments require alerting for operational awareness.

To pass parameters to a ListView in an Activity, you use a Property-Set step BEFORE calling Obj-List-View to place values onto the parameter page. The Obj-List-View method then reads from this parameter page. You don't pass parameters directly in the Obj-List-View method call, and ListView rules DO accept parameters.