Marketing keeps adding campaign tags to portal events without a rigid relational migration each time. Which lake-friendly approach supports that evolution?
Select an answer to reveal the explanation.
Short Explanation
Campaign tags multiply like sticky notes on a fridge. Schema-on-read lets new fields show up in the lake without smashing yesterday’s data. Flexible event payloads keep marketing agile while engineers still query what matters.
Full Explanation
Evolving web-event tags benefit from flexible, often schema-on-read lake designs. Marketing can introduce campaign parameters without blocking ingest or forcing destructive reloads of history. Rigid upfront schemas that reject novelty create operational friction for Cap. 10 analyzers that must track changing outreach.