Which risk is introduced by transferring source data as manually prepared files rather than through a supported connector?
Select an answer to reveal the explanation.
Short Explanation
When you use hand-made files, they arrive whether they're right or not. Nothing checks the schema, nothing raises an alarm when a column is missing, and nothing records where it came from - the failure surfaces later, in a report.
Full Explanation
The correct choice is the one stating that there is no schema enforcement, no failure signal, and no lineage, so bad or missing data reaches consumers unnoticed. Supported connectors enforce expectations, report failures, and record provenance. A manual file transfer has none of those, so a truncated extract, a renamed column, or a skipped day propagates silently and is usually discovered by a confused consumer.
The option claiming manually prepared files cannot be stored in object storage is incorrect because manually produced files can certainly be stored; storage is not the objection.
The option claiming the lakehouse cannot register data that arrived as a file is incorrect because file-based data can be registered as tables - registration is not restricted by how the file arrived.
The option claiming manual transfers always exceed the platform's per-load size limit is incorrect because there is no such universal size limit, and size is not the risk being described.
For the exam, the risk of manual movement is undetected data quality failure and missing lineage.