A new ingestion pipeline is being designed for a source that feeds regulatory reporting. Which requirement should the design satisfy?
Select an answer to reveal the explanation.
Short Explanation
Validate the incoming structure against the expected schema, reject or quarantine bad records, and capture metadata and lineage as part of the load. For regulatory data, an unvalidated load isn't safer; it just moves the problem into the report.
Full Explanation
The correct requirement is to validate the incoming structure against the expected schema, reject or quarantine records that fail, and capture metadata and lineage as part of the load. A governed ingestion pipeline enforces the schema contract at load time, handles non-conforming records explicitly rather than silently, and records metadata and lineage so consumers and auditors can trace what arrived and from where.
The option that loads whatever arrives without validation is incorrect because unvalidated loading does not preserve data so much as preserve corruption, pushing the failure downstream into reports where it is far more expensive to find.
The option that defers metadata capture until the pipeline has proven stable in production is incorrect because metadata captured retrospectively is reconstructed guesswork, and the period before it is captured has no provenance at all.
The option that ingests only the aggregates the reporting dashboard displays is incorrect because ingesting only aggregates discards the detail needed to investigate, reconcile or re-derive a figure.
For the exam, ingestion design covers schema enforcement, quality handling and governance capture together.