SnowPro Advanced: Data Engineer · Free practice question 8 of 10
Tag propagation across data movement
A governance policy requires that tags applied to a source table's columns automatically appear on any table derived from it through CTAS, COPY INTO, or INSERT-SELECT. Which statement about Snowflake tag propagation is correct?
- A.Tags always propagate automatically to any derived object.
- B.Tag propagation across data-movement operations must be explicitly enabled on the tag.
- C.Tags only propagate to derived objects that live in the same schema as the source.
- D.Tags cannot propagate — every derived object must be tagged manually with ALTER.
Show answer and explanation
Correct answer: B. Tag propagation across data-movement operations must be explicitly enabled on the tag.
Why: By default, Snowflake tags remain pinned to the object they were applied to. To have a tag follow data through CTAS / COPY INTO / INSERT-SELECT, propagation has to be enabled on the tag itself. That gives governance teams control over which tags should track lineage across derived objects and which should stay on the original.
More free SnowPro Advanced: Data Engineer questions
- Snowpark lazy evaluation
- Dynamic tables with TARGET_LAG
- Snowpipe Streaming for sub-10-second latency
- Fan-in task DAGs with AFTER
- Time Travel vs Fail-safe recovery window
- Maintaining externally managed Iceberg tables
- External table partition metadata refresh
- Query Acceleration max scale factor
- Alerting on Cortex AI credit usage