Practise the vocabulary for ETL, ELT, Change Data Capture (CDC), and incremental vs full load patterns.
0 / 6 completed
1 / 6
The key difference between ETL and ELT is:
ETL (legacy): transform → load using a dedicated transformation layer (Informatica, Talend). ELT (modern): load raw data into a cloud warehouse (Snowflake, BigQuery), then transform in-warehouse using SQL/dbt. ELT became feasible as cloud warehouses gained massive compute at low cost.
2 / 6
Change Data Capture (CDC) is used when:
CDC captures the delta (changes only), reducing data transfer volume and enabling near-real-time replication. Common methods: log-based CDC (reads database transaction logs — Debezium), trigger-based CDC, and timestamp-based incremental extraction.
3 / 6
An incremental load in a data pipeline means:
Incremental loads are more efficient than full loads for large tables: only the delta is processed. Requires a reliable changed-at timestamp or CDC. Challenge: deleted records are invisible to incremental loads — soft deletes or CDC are needed to handle them.
4 / 6
An upsert operation in a data warehouse refers to:
Upsert (MERGE/UPDATE-INSERT) is essential for incremental loads: avoid duplicates from new records while keeping existing records current. SQL: MERGE INTO target USING source ON target.id = source.id WHEN MATCHED THEN UPDATE ... WHEN NOT MATCHED THEN INSERT...
5 / 6
The phrase 'ELT became feasible as cloud warehouses gained compute power' means:
The ELT shift: cloud DWH pricing (pay-per-query, auto-scaling) made it cheaper to run transformations in the warehouse than to provision and maintain ETL transformation infrastructure. dbt democratised ELT by letting analysts write transformations in SQL.
6 / 6
Data lineage in a data engineering context means:
Data lineage answers: 'Where did this number come from?' If a revenue figure looks wrong, lineage lets you trace it back through transformations to the source tables and identify where the error was introduced. Tools: OpenLineage, Marquez, dbt lineage graph, modern data catalogs.
What does the "ETL vs ELT Vocabulary" exercise practise?How many questions are in this exercise?
This exercise has 6 questions, each multiple-choice with a full explanation shown after you answer.
What English level is this exercise for?
This exercise is tagged Intermediate. If the vocabulary feels difficult, browse the Data Engineering Language category page for an easier module to start with.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free with no account, sign-up, or paywall.
Do I get feedback if I answer incorrectly?
Yes — whichever option you choose, right or wrong, you'll immediately see an explanation clarifying the correct term and why the other options don't fit.
Can I retry this exercise?
Yes — once you finish all the questions, a "Try again" button on the results screen resets the exercise so you can practise as many times as you like.
Do I need an account to track my progress?
No account is required. Your progress bar and score for this session are tracked in the browser as you go, but nothing is saved once you leave the page.
Is "ETL vs ELT Vocabulary" part of a larger series?
Yes — it's one exercise in the Data Engineering Language category on CoderSlingo. See the category page for the full list of related exercises on similar terminology.
Can I link directly to this exercise?
Yes — this exercise has its own permanent URL, so you can bookmark it or share the link directly with a colleague or study partner.
Where can I find more exercises like this one?
See the Data Engineering Language category page for related exercises, or browse the main Exercises hub for other IT English topics.