Pega PRPC Platform Fundamentals Quiz

In Pega, Router, Notify, and Utility shapes in a flow rule execute activities. All activities are instances of the Rule-Obj-Activity rule type, with their specific behavior type (like Router or Utility) specified in their Security tab.

Step pages define the context for executing a specific step in an activity. They are optional because a step can run in the context of the activity's primary page. They are not automatically deleted upon activity completion and their class can differ from the activity's class.

The Requestor page holds session information including access roles, RuleSet list, and HTTP parameters. Process pages track work objects, Thread pages hold execution context, and User Pages is not a standard clipboard page.

In Pega, page lists and value lists use 1-based indexing, so the first element is at index 1 (not 0-based like some programming languages). They still use subscripts and braces like .Students(1) or .Values(1).

For a RuleSet with 5 versions, Rule-RuleSet-Name has 1 instance (one name entry) while Rule-RuleSet-Version has 5 instances (one per version like 01-01, 01-02, etc.). The name is shared across versions.

Page groups use non-numeric string subscripts (like pxResults('CustomerA')). Page lists use numeric subscripts, value lists are ordered values, and Java objects are not a clipboard structure with subscripts.

Not all classes require direct inheritance. Pattern inheritance and directed inheritance can be used separately. @baseclass is the root and has no inheritance, but other classes can inherit through patterns without direct parent specification.

Models can contain property references (page.property), literals (constant values), functions (built-in functions), and boolean expressions (conditions). Activity calls are not allowed in models - models define data transformation, not execution flow.

Application Accelerator creates work pools, RuleSets, work parties, forms, and work management structures. Communication/integration capabilities require manual configuration of connectors, services, or listener rules - they're not auto-generated.

Summary View in PRPC provides the group by functionality for aggregating and organizing data. List View displays individual records without grouping capabilities. The group by option is specifically available when you switch to Summary View to create aggregated reports.

Property rules in PRPC can be created with the same name in different rulesets (allowing versioning and specialization) and in different classes (enabling class-specific properties). They cannot be overridden with the same name in the same ruleset and class combination, but PRPC's inheritance facility allows derived classes to access properties defined in parent classes.

Monitor Activity workspace allows running the report wizard to generate reports, creating new reports from scratch, and browsing categories to find existing reports. Running processes from reports is not a standard feature of this workspace.

All custom classes in PRPC inherit from the three base classes: Work- (for work objects and case types), Data- (for reusable data and reference data), and History- (for historical instances and audit records). These form the foundation of PRPC's class hierarchy.

Pega rule resolution evaluates key factors including rule availability, Rulesets and Ruleset versions, circumstances (like date ranges or properties), and class inheritance to choose the right rule at runtime. Create Date Time is metadata and is not a factor in resolution logic.

Parse XML rules in PRPC are categorized under Integration-Mapping rules, which handle data transformation and mapping between external systems and PRPC. They are not Technical, Property, or any other rule category.

Router activities in PRPC use the AssignTo parameter to specify which work queue or user receives the assignment. SendTo and DirectTo are not valid parameters in standard router activities.

Organizations in PRPC are instances of the Data-Admin-Organization class. On a fresh installation, PRPC includes a default organization named pega.com, which serves as the initial organizational structure.

The ISO/OSI (Open Systems Interconnection) model consists of exactly 7 layers, from Physical (Layer 1) to Application (Layer 7). These layers are: Physical, Data Link, Network, Transport, Session, Presentation, and Application.

TCP/IP stands for Transmission Control Protocol/Internet Protocol. TCP handles reliable data delivery (transmission), while IP handles routing and addressing (internet). Together they form the foundational protocol suite of the Internet.

User-centered design requires understanding users first. After identifying application goals, knowing target users provides essential context for design decisions, task analysis, and function allocation. Task analysis and function allocation come later, after user needs are understood.