Pega PRCP Platform Fundamentals

Exceeding 15 SmartShapes in a flow violates PRPC guardrails and results in multiple issues: increased complexity making debugging difficult, reduced performance due to excessive processing nodes, and decreased clarity for developers maintaining the flow.

When a covered work object (A) is opened for transactions, PRPC locks both the covered object (A) and its parent cover object to maintain referential integrity. The other covered objects (B) remain unlocked until accessed.

When a work object within a cover object is opened in perform harness, PRPC locks both the individual work object and the parent cover object. This dual locking mechanism ensures data consistency across the cover/covered relationship.

The integrator shape in a PRPC flow refers to a Connect activity type. Connect activities are used for integrations with external systems and services, making them the appropriate activity type for the integrator shape.

Backward chaining calculates property values dynamically when they are needed or referenced, rather than upfront when input properties change. This fits the described behavior of computing the Area property on demand using Length and Width.

Model chaining in Pega DOES override properties in child classes with properties from parent class models. Option B states it doesn't override, which is the false statement the question seeks. Options A, C, and D describe actual behaviors of model chaining.

The Pega organization setup wizard creates all necessary rules automatically during the setup process. You don't need to manually create any rules before running the wizard. The wizard handles the creation of required classes, rule sets, and application rules.

In a Pega Data Model (or Declare Expressions / Model rules like Data Transforms), property initialization can be defined using property references in value fields, literal values, calling functions, or boolean expressions. Property-Set is an activity method, not a model rule initialization option.

Pega's implementation methodology follows the sequence: Business Value Assessment (BVA) → Conception → Elaboration → Construction → Transition. This is similar to Rational Unified Process stages. Options A, B, and C have incorrect ordering of these phases.

Business Value Assessment (BVA) focuses on defining success factors and ROI, not technical requirements or design. Business architects lead BVA to align technical implementation with business goals. Options B and C incorrectly describe BVA's purpose or leadership role.

For exceptions to appear in the tracer, both the rule set must be selected AND exceptions must be enabled in Events to Trace. Break conditions and checked-out rule tracing are separate concerns.

Decision tables in Pega can be referenced three ways: from decision shapes in flows, using Property-Map-DecisionTable method in activities, and through Rule-Declare-Expression. Option D correctly lists all three methods. Each approach serves different use cases in Pega applications.

Declare OnChange is specifically designed to execute activities when a property value changes. Declare Expressions (A) compute derived property values. Declare Constraint (B) validates property relationships. Declare Trigger (C) doesn't exist as a standard Pega declarative rule type.

Service level rules can execute activities when deadlines are reached and can increase work object urgency when goals or deadlines are met. They don't directly reset property values (A, B, C are incorrect). The urgency increase helps prioritize work items based on SLA compliance.

Data-Operator-Party is Pega's standard class for representing operator parties, including originators. The naming pattern follows Pega's class hierarchy convention. Options B, C, and D use incorrect class naming patterns that don't follow Pega conventions.

After Page-New creates a temporary page, you should clean it up with Page-Remove to prevent memory leaks. This is especially important when the page is only used temporarily during the activity. Obj-Save (D) would persist data, which isn't needed for temporary pages. The other options don't address cleanup.

Rule-Obj-Validate is the standard Pega rule for validating property values entered through HTML forms. It contains validation logic for individual properties or entire pages. Rule-Form-HTML (A) defines form structure, not validation. Options C and D are methods, not the primary validation mechanism.

Aggregate properties (Page Lists and Page Groups) use three index keywords in activities: () adds to the end, () adds at a specific position, and () adds at the beginning. Options A, B, and C are missing one of these three or include incorrect keywords like () or ().

In Pega, flow actions are categorized into Connector flow actions (which transition a case to the next step) and Local flow actions (which perform updates without leaving the current assignment). Assignment records are stored under Assign- classes, not Work- or Data-.