1. Ingestion Patterns advanced Multiple choice

    A connector extracts a SaaS object by paging with offset and a limit of 500 under a modified-at filter. Every nightly run loads exactly 10000 rows and finishes green. Reconciliation shows 61000 matching records at source. The API returns HTTP 200 with an empty page at offset 10000 and support confirms an undocumented deep-paging cap. Which change actually closes the gap?

    3 min answer connectorspaginationsilent-failurewatermarks
  2. Ingestion Patterns advanced

    A data-ingestion platform runs hundreds of connectors, each with different APIs, rate limits, failure modes and schemas. How should isolation, retries, scheduling, checkpointing, backfills and schema evolution be designed?

    2 min answer airbytefivetranconnectorsisolation
  3. Ingestion Patterns advanced

    A platform ingests high-volume telemetry from many sources. Which ingestion pattern properties matter most?

    2 min answer ingestionbackpressureidempotencyschema
  4. Ingestion Patterns intermediate

    A platform team proposes one ingestion standard: every source publishes to Kafka and the warehouse loads only from Kafka. That includes 40 SaaS connectors that pull once a day. The argument is one path, one set of tools, and replayability everywhere. Review it — what would you remove, what would you keep and what would you leave alone?

    3 min answer ingestionkafkauniformityoperability
  5. Ingestion Patterns intermediate

    An analytics team extracts daily using a `modified_at` watermark. Reconciliation shows the warehouse has 3% more customers than the source. Why?

    2 min answer cdcingestiondata-quality