Question 590
For a global logistics company, the original problem was: An analyst pivots event records to monthly metrics but assumes unexpected new event categories appear automatically in a fixed static pivot. What observation confirms success?
Explanation
Correct Answer
A new event category follows the documented behavior rather than silently corrupting existing columns. This validates the relevant action: Use a supported dynamic pivot or maintain an explicit governed category list consistent with the consumer schema. The underlying Snowflake behavior is: Static pivot category definitions cannot automatically represent every newly appearing dimension value.
Incorrect Answers
A controlled tie fixture shows precisely the required ranking behavior. This evidence tests a DIFFERENT situation: A finance report uses RANK to assign unique row numbers but produces ties and gaps in the sequence. The correction required in this case is: Use a supported dynamic pivot or maintain an explicit governed category list consistent with the consumer schema.
The output includes one row per intended order line while preserving source order identifiers. This evidence tests a DIFFERENT situation: A dataset stores orders as nested JSON arrays, but a report produces one row per order instead of one per line item. The correction required in this case is: Use a supported dynamic pivot or maintain an explicit governed category list consistent with the consumer schema.
The pipeline produces identical required outputs with fewer repeated full scans. This evidence tests a DIFFERENT situation: A nightly transformation consumes excessive time because the same large staging table is scanned multiple times in separate jobs. The correction required in this case is: Use a supported dynamic pivot or maintain an explicit governed category list consistent with the consumer schema.