What is the practical consequence of relying on a naming convention such as a date suffix instead of table-format partitioning and metadata?
Select an answer to reveal the explanation.
Short Explanation
Conventions only work while everyone remembers them. You need the format's metadata so the engine enforces the intent, so mistakes become impossible rather than merely discouraged.
Full Explanation
Naming conventions are agreements held in people's heads and in scattered code. Every consumer must independently parse and honour them, new team members will not know them, and typos produce silently wrong results because nothing validates them. That is the practical consequence: every consumer must implement the convention correctly, and nothing detects or prevents violations. The claim that queries cannot filter on dates at all without the convention is wrong because date filtering is normal query capability that does not depend on filenames. The claim that object storage rejects files whose names do not follow registered patterns is wrong because object storage accepts arbitrary keys; it enforces no pattern. The claim that the convention limits the table to one writer per day is wrong because the convention imposes no writer limits, and the absence of coordination is exactly the danger. For the exam, prefer enforced metadata over conventions: the format makes the guarantee, rather than relying on everyone being careful.