Pega Process Configuration & Administration

JMS (Java Message Service) requires a listener to receive and process messages from a queue or topic. The listener continuously monitors the messaging destination and invokes service processing when messages arrive. EJB uses direct RMI/IIOP calls, SOAP and HTTP use request/response patterns - none require continuous listeners like JMS.

Thread-scoped data pages (formerly declare pages) live within the requestor thread context. When the requestor logs off, the session times out, or the session expires, the requestor context and its threads are destroyed, removing the pages from memory. This makes all three scenarios correct.

Summary View rules in PEGA can generate graphical reports. List View rules display tabular data and do not create graphs. The Obj-Graph method is not the correct approach for Summary View-based graphing. Summary View is the mechanism for creating report visualizations and graphs.

The framework class layer contains common, reusable rules designed to be shared and extended across the entire enterprise or multiple implementations. It does not replace Pega standard work classes, nor is it a temporary placeholder or intended solely for localized, specialized rules.

A screen flow is designed for sequential user actions within a single assignment and cannot act as a starter flow to create new cases. Standard flows are required to initialize work items, while screen flows require an existing context, making 'Cannot be a starter flow' the correct choice.

The check-in and check-out version control features in Pega apply exclusively to rule resolution, which operates on classes inheriting from the Rule- base class. Classes under Data-, History-, or Work- represent runtime instances and data records that do not use rule-based version control.

Properties with the px prefix are system-maintained and read-only. Pega prevents modifying them using standard methods like Property-Set. Developers must use the specialized Property-Set-Special method to force-write values to these system properties, making other options incorrect.

Properties on the primary page can be accessed using dot notation (.myProperty) or by explicitly prefixing the page name as Primary.myProperty or primary.myProperty. The keyword Primary is case-insensitive, but local variables use the local prefix, and case-sensitive property naming conventions must be matched.

Pega stores the serialized XML or JSON representation of a rule or work instance in a binary large object (BLOB) column named pzPVStream. Other options like pzInsStream, pzObjStream, and pzRefStream are incorrect column names that do not store the main instance BLOB payload.

For circumstancing with an as-of date, the rule's as-of date (09/13/2009) must match the creation date (09/13/2009), and the active system date (09/20/2009) must fall within the defined range (01/01/2009 to 12/30/2009). The other choices fail because their system date ranges do not include the current date.

Pega maps concrete classes to relational database tables. When a class instance is saved, a corresponding row is created in the associated table. Rules like flows, models, activities, and flow actions are definitions rather than the general runtime instances that map to rows, making 'Instance of any class' correct.

A Rule-Admin-Product-Patch rule defines a subset of rulesets or patches and does not depend on the prior existence or migration of its parent Rule-Admin-Product rule on the destination system. The product patch can be created and imported independently, making the statement false.

Out-of-the-box activities in Pega provide pre-configured functions for common workflows. They can route work to workbaskets or worklists, update status values, and manage cover or folder structures. Because all these tasks are supported by standard OOTB activities, 'All of the above' is the correct selection.

During loop execution over a list, Pega automatically stores the current iteration index in the standard parameter pyForEachCount. The other parameters like pyIterationNumber, pyForEach, and pyCount do not exist as standard loop counters in Pega's engine API, making them incorrect.

Split-forEach is the flow shape designed to iterate over elements in an embedded list, spawning a separate flow execution for each item. Spin-Off creates subprocesses but not specifically for list iteration, while Sub-Flow calls another flow and Swim Lane is for organizational grouping.

The primary page of an activity does not always need to be defined on the Pages & Classes tab - it can be set programmatically within the activity itself or inherited. The absolute constraint 'must always' makes this statement false.

A cover and its covered work objects must belong to the same class group as they are structurally linked - the cover object encapsulates related covered cases. They cannot be in different class groups.

Object-level locks are higher-level constructs that persist longer than database locks, specifically designed to prevent concurrent modifications by multiple users. Database locks are lower-level, shorter-duration mechanisms for maintaining data integrity at the storage level.