[Work Delegation and Asynchronous Processing] Hospital XYZ wants to analyze patient data and identify those at high risk of readmission. The hospital…

Data Flows are specifically engineered for complex data integration and large-scale processing tasks. A key advantage is their ability to use multiple Data Sets as sources, allowing them to natively combine and transform data from disparate systems like an EHR and an admissions database. Furthermore, Data Flows are the designated Pega tool for high-volume batch and real-time stream processing, leveraging scalable architecture to efficiently analyze large datasets, such as an entire patient population. A Queue Processor, by contrast, is designed for processing discrete, individual tasks from a single queue and is not optimized for large-scale data aggregation from multiple sources.

C. Data Flow can prioritize tasks based on urgency.

This is incorrect. Task prioritization is a defining feature of Queue Processors, which are designed to process queued items based on factors like urgency, not Data Flows.

D. Data Flow can process data in real-time.

This is not a distinguishing advantage. While Data Flows excel at real-time stream processing, Queue Processors also execute tasks in a near-real-time manner as they are queued.

1. Pega Platform™ Documentation

"Data Flows": "A data flow enables you to combine

process

and move data from one or more sources to one or more destinations... Data flows are scalable and resilient." This supports the ability to handle multiple sources (A) and large volumes (B).

Source: Pega Community

Pega Platform 8.8 Documentation

"Decisioning and analytics > Data Flows".

2. Pega Platform™ Documentation

"Creating a data flow": The process explicitly involves adding and combining multiple data sources. "In the Data flow record

you can combine multiple data sources and then use a wide range of shapes to process the data that these sources provide." This directly validates option A.

Source: Pega Community

Pega Platform 8.8 Documentation

"Decisioning and analytics > Data Flows > Creating a data flow".

3. Pega Platform™ Documentation

"Queue Processor rules": "Use a Queue Processor rule for simple queue management or when you need to queue a recurring or delayed task." This highlights its purpose for discrete

task-based processing

contrasting with the large-scale data analysis function of a Data Flow.

Source: Pega Community

Pega Platform 8.8 Documentation

"Asynchronous processing > Queue Processor rules".