Pega PRPC Fundamentals Quiz

Browser session timeout settings (such as the timeout interval) are defined on the requestor Pega rule (specifically via the requestor type), which governs session state, rather than at the access group or portal level.

Standard Pega harnesses have four standard variations: New, Perform, Review, and Confirm. List items like Pending, Open, and Reopen are either statuses or handled differently rather than being standard harness types, making the first statement false and thus the correct answer to the question.

In Pega, most activity methods, including Property-Remove, update the system property pxMethodStatus to indicate the success or failure status of the method execution. Property-specific or developer-defined properties like pyPropertyStatus are not automatically updated by system methods.

In Pega, Repeating Rows or Repeating Layouts are used with page lists or page groups to present list-like properties. Page Group is a valid property mode for repeating rows, whereas Value List/Group hold single values and cannot represent complex structures. However, Page List is also typical; Page Group is acceptable here.

Decision Tables are versatile evaluation rules that can be invoked across Pega. They are referenced in Flow Decision shapes, called in Activities, executed as collection steps, or used as calculations in Declare Expressions.

While SMA can manage and connect to multiple nodes configured in a cluster, it operates in the context of one selected node at a time. Administrators cannot execute commands or monitor metrics across multiple nodes simultaneously.

DB trace feature is actually ENABLED by default in Pega systems. This feature helps diagnose database-related performance issues and query problems. The statement claiming it is disabled by default is incorrect, which is why the correct answer is False.

Property-Set-Special method is specifically recommended for setting px (platform) properties on the clipboard. Px properties are system-generated properties that Pega uses for internal operations. Py properties are for user-specific data, pz for temporary processing, and Parameters/Local Variables are managed differently. Property-Set-Special is optimized for px property manipulation.

Rule-Message rules define reusable error message text and templates in Pega. These messages are associated with properties or pages to flag validation issues, whereas other listed options are not valid Pega rule types.

A key tenet of the 'Build for Change' guardrail is delegating business logic to business users. Activities are technical rule types that business users cannot easily maintain; hence, business logic should use Decision Tables or Data Transforms.

Agent information is NOT stored in the pegatrules.xml file. Agents are stored in Rule-Agent-Queue and Data-Agent-Queue tables, which manage agent scheduling and execution. The pegatrules.xml file contains other rule declarations but not agent-specific information.

Pega stores the complete XML representation of case and rules data in a compressed BLOB (Binary Large Object) column called the Storage Stream (specifically pzPVStream) in the database.

A property is made available for exposing by setting its column visibility to Required. This configuration makes the property visible and accessible for external systems or reporting. Declaring as an Exposed Property is not the correct mechanism, and direct database changes are not recommended. The column visibility setting is the proper way to control property exposure.

EditAttachment is the correct flow action in Pega PRPC for creating new versions of existing file attachments. CreateNewVersion and CreateNewAttachment are not standard flow actions. The EditAttachment action handles versioning by creating a new version when editing an existing attachment.

The pxThread clipboard page represents the thread execution context in Pega and is an instance of the Code-Pega-Thread class. Other classes like Code-Pega-List represent lists, not the thread itself.

Data-Party-Com, Data-Party-Gov, and Data-Party-Operator are standard Pega concrete classes derived from Data-Party to represent work parties. Data-Party-Opr is not a standard work party class in Pega.

The Application Accelerator generates RuleSets, Harnesses, Flows, and Validation rules automatically based on the application profile. It cannot create Constraints rules, which enforce strict property value relationships and must be created manually.

In Pega, sections cannot be directly included within other sections. While you can reference a section from another section using harnesses or dynamic layouts, you cannot nest one section inside another section as a direct parent-child relationship.

The Clipboard is an internal debugging and development tool in Pega that should not be accessible to application users in production environments. It is intended for developers and administrators to troubleshoot and inspect clipboard pages during development and testing.

A Validation rule in Pega is primarily used to ensure that all required fields are complete and that data meets specified criteria. It does not validate data types (that's done by edit validates), check security permissions, or notify interested parties (that's done by routing).