Exam Bundle

That observation is a valid indicator for “A batch pipeline writes too many output files for its final dataset size” when using Adjust output partitioning before writing within safe memory limits. The scenario instead tests “A new curated dataset requires centralized ownership and consistent permission inheritance”; the relevant result is The intended owner and inherited privileges apply to the new dataset.

That observation is a valid indicator for “The table has huge amounts of obsolete files and operators need retention-aware cleanup” when using Use appropriately configured `VACUUM` with safe retention conditions. The scenario instead tests “A new curated dataset requires centralized ownership and consistent permission inheritance”; the relevant result is The intended owner and inherited privileges apply to the new dataset.

This signal belongs to the adjacent case “A new liquid clustered table is created but no clustering keys were selected automatically,” whose remedy is Review predictive optimization eligibility and query workload instead of assuming an error. The observed result for the present requirement is The intended owner and inherited privileges apply to the new dataset.

This action solves a different issue: “A high-cardinality filter benefits from clustering rather than massive Hive partitions.” Its normal signal is File count and selective scan cost decrease without partition explosion. Here the requested behavior is “Queries filter on changing subsets of customer, date and region fields,” so that signal is not sufficient.

This action solves a different issue: “A UC managed table should choose clustering columns from observed workloads.” Its normal signal is Selected keys adapt to query patterns over time where beneficial. Here the requested behavior is “Queries filter on changing subsets of customer, date and region fields,” so that signal is not sufficient.

The alternative Stop ZORDER on the liquid-clustered table and run supported clustering maintenance has a distinct purpose—An old Delta table uses ZORDER but is migrated to `CLUSTER BY`. It would not establish the required outcome (Queries filter on changing subsets of customer, date and region fields); the necessary verification concerns Data skipping improves for common filters after clustering maintenance.

This signal belongs to the adjacent case “A UC managed table should choose clustering columns from observed workloads,” whose remedy is Use `CLUSTER BY AUTO` with required predictive optimization support. The observed result for the present requirement is Data skipping improves for common filters after clustering maintenance.

That observation is a valid indicator for “A query filters by an indexed or statistically tracked customer/date field” when using Ensure relevant column statistics and appropriate data layout for pruning. The scenario instead tests “Queries filter on changing subsets of customer, date and region fields”; the relevant result is Data skipping improves for common filters after clustering maintenance.

That observation is a valid indicator for “Queries commonly filter on different high-cardinality attributes that change over time” when using Use supported liquid clustering rather than creating thousands of tiny partitions. The scenario instead tests “Queries filter on changing subsets of customer, date and region fields”; the relevant result is Data skipping improves for common filters after clustering maintenance.

Enable predictive optimization with supported workspace/metastore settings is appropriate when “Optimizations must run automatically for eligible managed Delta tables”; it would be verified by Maintenance history shows automatic optimization on eligible tables. It does not directly satisfy “A UC managed table should choose clustering columns from observed workloads,” whose relevant acceptance evidence is Selected keys adapt to query patterns over time where beneficial.

This action solves a different issue: “A managed table's storage optimization should reflect observed query patterns automatically.” Its normal signal is Optimization activity and improved data skipping follow the workload. Here the requested behavior is “A UC managed table should choose clustering columns from observed workloads,” so that signal is not sufficient.

Run supported `OPTIMIZE` or automatic clustering maintenance is appropriate when “A large table is already liquid clustered on a new key but old files are not reorganized”; it would be verified by File layout changes and targeted query scan cost decreases. It does not directly satisfy “A UC managed table should choose clustering columns from observed workloads,” whose relevant acceptance evidence is Selected keys adapt to query patterns over time where beneficial.

Optimizer avoids unnecessary rewrites when predicted benefit is negligible would demonstrate the separate action Accept cost-aware optimizer selection rather than force arbitrary keys, which addresses “A very small table receives no automatic clustering keys despite configuration.” It does not verify the requirement “A UC managed table should choose clustering columns from observed workloads” following Use `CLUSTER BY AUTO` with required predictive optimization support.

This signal belongs to the adjacent case “A new liquid clustered table is created but no clustering keys were selected automatically,” whose remedy is Review predictive optimization eligibility and query workload instead of assuming an error. The observed result for the present requirement is Selected keys adapt to query patterns over time where beneficial.

That observation is a valid indicator for “A managed table's storage optimization should reflect observed query patterns automatically” when using Enable appropriate predictive optimization features for supported managed tables. The scenario instead tests “A UC managed table should choose clustering columns from observed workloads”; the relevant result is Selected keys adapt to query patterns over time where beneficial.

This action solves a different issue: “A UC managed table should choose clustering columns from observed workloads.” Its normal signal is Selected keys adapt to query patterns over time where beneficial. Here the requested behavior is “A prior `ZORDER BY` strategy is being replaced by liquid clustering,” so that signal is not sufficient.

This action solves a different issue: “A high-cardinality filter benefits from clustering rather than massive Hive partitions.” Its normal signal is File count and selective scan cost decrease without partition explosion. Here the requested behavior is “A prior `ZORDER BY` strategy is being replaced by liquid clustering,” so that signal is not sufficient.

The alternative Stop ZORDER on the liquid-clustered table and run supported clustering maintenance has a distinct purpose—An old Delta table uses ZORDER but is migrated to `CLUSTER BY`. It would not establish the required outcome (A prior `ZORDER BY` strategy is being replaced by liquid clustering); the necessary verification concerns The table reports clustering keys and maintenance runs successfully.

This signal belongs to the adjacent case “A very small table receives no automatic clustering keys despite configuration,” whose remedy is Accept cost-aware optimizer selection rather than force arbitrary keys. The observed result for the present requirement is The table reports clustering keys and maintenance runs successfully.

Maintenance history shows automatic optimization on eligible tables pertains to a different control (Enable predictive optimization with supported workspace/metastore settings) and a different need (Optimizations must run automatically for eligible managed Delta tables). It cannot establish that Migrate table layout to supported liquid clustering and stop using ZORDER for it met the stated goal.

This signal belongs to the adjacent case “A new liquid clustered table is created but no clustering keys were selected automatically,” whose remedy is Review predictive optimization eligibility and query workload instead of assuming an error. The observed result for the present requirement is The table reports clustering keys and maintenance runs successfully.

This action solves a different issue: “A UC managed table should choose clustering columns from observed workloads.” Its normal signal is Selected keys adapt to query patterns over time where beneficial. Here the requested behavior is “A large table is already liquid clustered on a new key but old files are not reorganized,” so that signal is not sufficient.

This action solves a different issue: “An old Delta table uses ZORDER but is migrated to `CLUSTER BY`.” Its normal signal is The table metadata and scan plan reflect its new clustering layout. Here the requested behavior is “A large table is already liquid clustered on a new key but old files are not reorganized,” so that signal is not sufficient.

Optimize data layout or query access before increasing disk cache settings belongs to the separate case “A query shows little benefit from disk caching because every run reads new files,” where Measured remote read volume falls for the relevant recurring access pattern would be expected. That differs from the condition in this stem: “A large table is already liquid clustered on a new key but old files are not reorganized.”

This signal belongs to the adjacent case “Very large files cause poor parallelism for typical query scans,” whose remedy is Choose a balanced target file size and tune supported write optimization. The observed result for the present requirement is File layout changes and targeted query scan cost decreases.

This signal belongs to the adjacent case “An old Delta table uses ZORDER but is migrated to `CLUSTER BY`,” whose remedy is Stop ZORDER on the liquid-clustered table and run supported clustering maintenance. The observed result for the present requirement is File layout changes and targeted query scan cost decreases.

That observation is a valid indicator for “Queries filter on changing subsets of customer, date and region fields” when using Choose supported liquid clustering for the Delta table. The scenario instead tests “A large table is already liquid clustered on a new key but old files are not reorganized”; the relevant result is File layout changes and targeted query scan cost decreases.

This action solves a different issue: “Queries commonly filter on different high-cardinality attributes that change over time.” Its normal signal is Filtering improves without exploding partition directory counts. Here the requested behavior is “A very small table receives no automatic clustering keys despite configuration,” so that signal is not sufficient.

Run `OPTIMIZE` or enable supported automatic compaction is appropriate when “Queries spend excessive time opening small files after frequent appends”; it would be verified by File count falls and average file size increases. It does not directly satisfy “A very small table receives no automatic clustering keys despite configuration,” whose relevant acceptance evidence is Optimizer avoids unnecessary rewrites when predicted benefit is negligible.

This action solves a different issue: “A prior `ZORDER BY` strategy is being replaced by liquid clustering.” Its normal signal is The table reports clustering keys and maintenance runs successfully. Here the requested behavior is “A very small table receives no automatic clustering keys despite configuration,” so that signal is not sufficient.

The optimizer selects keys only when sufficient benefit is predicted pertains to a different control (Review predictive optimization eligibility and query workload instead of assuming an error) and a different need (A new liquid clustered table is created but no clustering keys were selected automatically). It cannot establish that Accept cost-aware optimizer selection rather than force arbitrary keys met the stated goal.

That observation is a valid indicator for “Queries filter on changing subsets of customer, date and region fields” when using Choose supported liquid clustering for the Delta table. The scenario instead tests “A very small table receives no automatic clustering keys despite configuration”; the relevant result is Optimizer avoids unnecessary rewrites when predicted benefit is negligible.

Automatic/manual maintenance targets tables with demonstrated query benefit pertains to a different control (Use cost-aware optimization policies rather than blanket frequent rewrites) and a different need (Maintenance cost is rising on tables rarely queried). It cannot establish that Accept cost-aware optimizer selection rather than force arbitrary keys met the stated goal.