PEGACPLSA24V1 Sample Questions & Answers

Constellation moves away from server-rendered HTML (Section-based). It sends metadata via DX API to a client-side engine, which enforces design system consistency. This means custom HTML/JSP sections are generally not supported or require specific custom components.

Email Bots (a form of IVA) use NLP to understand email content, extract data (entities), and automate case creation/routing.

IVA provides connectors for social messaging platforms, allowing case interaction via chat.

Prediction Studio is the dedicated workspace for managing AI models, predictive analytics, and text analytics configurations.

The Queue Management landing page in Admin Studio provides visibility into Queue Processors, allowing admins to view status, inspect broken items, and trace or requeue them.

For structural differences and significant variations in data/logic across multiple dimensions (LOB and Region), Class Specialization (often via the Situational Layer Cake) is superior to circumstancing. It allows for distinct class-based inheritance, better reuse, and easier maintenance of complex variations.

The Data-Instance-First approach (often facilitated by App Studio's data modeling tools) focuses on defining the business data objects and records within Pega first. This allows development and testing to proceed using local storage/simulation before connecting to actual live integrations, promoting a center-out approach.

The Wait Shape has a specific configuration 'Wait for Case Completion' -> 'All child cases'. This automatically pauses the parent flow until all instantiated child cases reach a resolved status, handling the dynamic nature of the child count.

Queue Processors (Standard) are designed for immediate or delayed asynchronous processing of individual items (like cases). They use Kafka for message durability, support automatic retries, and distribute the workload across available nodes naturally. Job Schedulers are better for recurring schedule-based tasks, but for processing a feed of items, queuing them to a Queue Processor is the robust pattern.

While basic filtering happens in the query, complex logic comparing user skills (from Operator profile) against assignment requirements is best handled in the 'GetNextWorkCriteria' Decision Tree or the 'getContent' activity customization if standard skill routing isn't sufficient. However, standard Skill-based routing is a core feature enabled on the Operator record ('Use skills for routing'). If we assume standard configuration: The 'Get Next Work' logic automatically checks skills if enabled. For custom logic, the Decision Tree is the extensibility point.

Thread scope associates the Data Page with a specific case or interaction thread. It is not shared across threads or users. 'Requestor' scope would share it across all threads for that user (which might be valid depending on 'interaction' definition, but Thread is safer for case-specific context). However, the prompt says 'duration of user's interaction' (Requestor) vs 'different user' (Requestor). Actually, Requestor scope is best for 'User Session'. Thread is for 'Case Tab'. Re-reading: 'reloads it if a different user requests it' implies sharing is NOT desired between users. Requestor Scope fits 'User's interaction'. Thread fits 'Specific Tab'. Given 'User's interaction' usually implies the Requestor session. Let's select Requestor.