What are the core components of a Foundry pipeline and their roles?

• A. Sources (input datasets), transformations (processing steps), streams (real-time outputs), and orchestration (scheduling and execution).
• B. Inputs, processing scripts, dashboards, and orchestration.
• C. Sources (input datasets), transformations (processing steps), sinks (output datasets), and orchestration (scheduling and execution).
• D. Sources, transformations, stores, and orchestration.

Answer: (C)

Foundry pipelines are organized around four elements: sources, transformations, sinks, and orchestration. Data enters the pipeline from sources as input datasets. Transformations are the processing steps that shape, clean, or enrich the data. The results are written to sinks, which are the output datasets the pipeline produces. Orchestration controls when and how the pipeline runs, handling scheduling, execution order, and monitoring.

This combination fits the usual ETL/ELT pattern: you bring in data, apply logic, store the results, and manage the run itself. The other options mix in terms like streams, dashboards, or stores that don’t align with the standard pipeline outputs or control mechanisms.