Exam Bundle

This signal belongs to the adjacent case “A dimension is referenced before its first record arrives from the master system,” whose remedy is Use an unknown/inferred member and reconcile it later. The observed result for the present requirement is Fact revenue totals remain correct when analyzing multiple promotions.

That observation is a valid indicator for “A corrected dimension description should replace prior text with no requirement for history” when using Use SCD Type 1 overwrite semantics for that attribute. The scenario instead tests “A many-to-many relationship between products and promotions causes duplicate fact joins”; the relevant result is Fact revenue totals remain correct when analyzing multiple promotions.

Queries group facts by the correct date, product and store attributes would demonstrate the separate action Build a sales fact table linked to conformed dimensions by surrogate keys, which addresses “Revenue should be analyzed by date, product and store using a stable relational model.” It does not verify the requirement “A many-to-many relationship between products and promotions causes duplicate fact joins” following Introduce a governed bridge table or appropriate allocation logic.

The alternative Evaluate supported UniForm/interoperability features and protocol requirements has a distinct purpose—A Delta-managed table should be read through an interoperable Iceberg interface where supported. It would not establish the required outcome (A primary Databricks pipeline needs ACID transactions and Delta features); the necessary verification concerns Concurrent reads observe consistent committed Delta versions.

This action solves a different issue: “A consumer reports unsupported table protocol features after a writer upgrade.” Its normal signal is The consumer successfully loads the table's current protocol. Here the requested behavior is “A primary Databricks pipeline needs ACID transactions and Delta features,” so that signal is not sufficient.

This action solves a different issue: “An external partner needs Iceberg-compatible open table metadata.” Its normal signal is The partner's supported Iceberg reader discovers and queries the expected snapshot. Here the requested behavior is “A primary Databricks pipeline needs ACID transactions and Delta features,” so that signal is not sufficient.

The partner's supported Iceberg reader discovers and queries the expected snapshot pertains to a different control (Use a supported Iceberg table or interoperable format layout for the shared workload) and a different need (An external partner needs Iceberg-compatible open table metadata). It cannot establish that Use a supported Delta table for the curated dataset met the stated goal.

File pruning metrics improve after clustering maintenance would demonstrate the separate action Use supported liquid clustering for the eligible managed table, which addresses “A table is optimized for selective queries on high-cardinality fields.” It does not verify the requirement “A primary Databricks pipeline needs ACID transactions and Delta features” following Use a supported Delta table for the curated dataset.

This signal belongs to the adjacent case “A consumer reports unsupported table protocol features after a writer upgrade,” whose remedy is Choose a compatible reader/runtime or a supported migration approach. The observed result for the present requirement is Concurrent reads observe consistent committed Delta versions.

The alternative Use supported liquid clustering for the eligible managed table has a distinct purpose—A table is optimized for selective queries on high-cardinality fields. It would not establish the required outcome (An external partner needs Iceberg-compatible open table metadata); the necessary verification concerns The partner's supported Iceberg reader discovers and queries the expected snapshot.

The alternative Evaluate supported UniForm/interoperability features and protocol requirements has a distinct purpose—A Delta-managed table should be read through an interoperable Iceberg interface where supported. It would not establish the required outcome (An external partner needs Iceberg-compatible open table metadata); the necessary verification concerns The partner's supported Iceberg reader discovers and queries the expected snapshot.

The alternative Choose a compatible reader/runtime or a supported migration approach has a distinct purpose—A consumer reports unsupported table protocol features after a writer upgrade. It would not establish the required outcome (An external partner needs Iceberg-compatible open table metadata); the necessary verification concerns The partner's supported Iceberg reader discovers and queries the expected snapshot.

This signal belongs to the adjacent case “A primary Databricks pipeline needs ACID transactions and Delta features,” whose remedy is Use a supported Delta table for the curated dataset. The observed result for the present requirement is The partner's supported Iceberg reader discovers and queries the expected snapshot.

File pruning metrics improve after clustering maintenance would demonstrate the separate action Use supported liquid clustering for the eligible managed table, which addresses “A table is optimized for selective queries on high-cardinality fields.” It does not verify the requirement “An external partner needs Iceberg-compatible open table metadata” following Use a supported Iceberg table or interoperable format layout for the shared workload.

This signal belongs to the adjacent case “A consumer reports unsupported table protocol features after a writer upgrade,” whose remedy is Choose a compatible reader/runtime or a supported migration approach. The observed result for the present requirement is The partner's supported Iceberg reader discovers and queries the expected snapshot.

This action solves a different issue: “A table is optimized for selective queries on high-cardinality fields.” Its normal signal is File pruning metrics improve after clustering maintenance. Here the requested behavior is “A Delta-managed table should be read through an interoperable Iceberg interface where supported,” so that signal is not sufficient.

Choose a compatible reader/runtime or a supported migration approach is appropriate when “A consumer reports unsupported table protocol features after a writer upgrade”; it would be verified by The consumer successfully loads the table's current protocol. It does not directly satisfy “A Delta-managed table should be read through an interoperable Iceberg interface where supported,” whose relevant acceptance evidence is The alternative engine reads a consistent supported table snapshot.

Use a supported Iceberg table or interoperable format layout for the shared workload is appropriate when “An external partner needs Iceberg-compatible open table metadata”; it would be verified by The partner's supported Iceberg reader discovers and queries the expected snapshot. It does not directly satisfy “A Delta-managed table should be read through an interoperable Iceberg interface where supported,” whose relevant acceptance evidence is The alternative engine reads a consistent supported table snapshot.

The partner's supported Iceberg reader discovers and queries the expected snapshot would demonstrate the separate action Use a supported Iceberg table or interoperable format layout for the shared workload, which addresses “An external partner needs Iceberg-compatible open table metadata.” It does not verify the requirement “A Delta-managed table should be read through an interoperable Iceberg interface where supported” following Evaluate supported UniForm/interoperability features and protocol requirements.

The consumer successfully loads the table's current protocol would demonstrate the separate action Choose a compatible reader/runtime or a supported migration approach, which addresses “A consumer reports unsupported table protocol features after a writer upgrade.” It does not verify the requirement “A Delta-managed table should be read through an interoperable Iceberg interface where supported” following Evaluate supported UniForm/interoperability features and protocol requirements.

This signal belongs to the adjacent case “A table is optimized for selective queries on high-cardinality fields,” whose remedy is Use supported liquid clustering for the eligible managed table. The observed result for the present requirement is The alternative engine reads a consistent supported table snapshot.

Evaluate supported UniForm/interoperability features and protocol requirements is appropriate when “A Delta-managed table should be read through an interoperable Iceberg interface where supported”; it would be verified by The alternative engine reads a consistent supported table snapshot. It does not directly satisfy “A table is optimized for selective queries on high-cardinality fields,” whose relevant acceptance evidence is File pruning metrics improve after clustering maintenance.

The alternative Use a supported Iceberg table or interoperable format layout for the shared workload has a distinct purpose—An external partner needs Iceberg-compatible open table metadata. It would not establish the required outcome (A table is optimized for selective queries on high-cardinality fields); the necessary verification concerns File pruning metrics improve after clustering maintenance.

Choose a compatible reader/runtime or a supported migration approach is appropriate when “A consumer reports unsupported table protocol features after a writer upgrade”; it would be verified by The consumer successfully loads the table's current protocol. It does not directly satisfy “A table is optimized for selective queries on high-cardinality fields,” whose relevant acceptance evidence is File pruning metrics improve after clustering maintenance.

That observation is a valid indicator for “A Delta-managed table should be read through an interoperable Iceberg interface where supported” when using Evaluate supported UniForm/interoperability features and protocol requirements. The scenario instead tests “A table is optimized for selective queries on high-cardinality fields”; the relevant result is File pruning metrics improve after clustering maintenance.

Concurrent reads observe consistent committed Delta versions would demonstrate the separate action Use a supported Delta table for the curated dataset, which addresses “A primary Databricks pipeline needs ACID transactions and Delta features.” It does not verify the requirement “A table is optimized for selective queries on high-cardinality fields” following Use supported liquid clustering for the eligible managed table.

That observation is a valid indicator for “A consumer reports unsupported table protocol features after a writer upgrade” when using Choose a compatible reader/runtime or a supported migration approach. The scenario instead tests “A table is optimized for selective queries on high-cardinality fields”; the relevant result is File pruning metrics improve after clustering maintenance.

This action solves a different issue: “A table is optimized for selective queries on high-cardinality fields.” Its normal signal is File pruning metrics improve after clustering maintenance. Here the requested behavior is “A consumer reports unsupported table protocol features after a writer upgrade,” so that signal is not sufficient.

Use a supported Iceberg table or interoperable format layout for the shared workload belongs to the separate case “An external partner needs Iceberg-compatible open table metadata,” where The partner's supported Iceberg reader discovers and queries the expected snapshot would be expected. That differs from the condition in this stem: “A consumer reports unsupported table protocol features after a writer upgrade.”

Use a supported Delta table for the curated dataset belongs to the separate case “A primary Databricks pipeline needs ACID transactions and Delta features,” where Concurrent reads observe consistent committed Delta versions would be expected. That differs from the condition in this stem: “A consumer reports unsupported table protocol features after a writer upgrade.”

That observation is a valid indicator for “A table is optimized for selective queries on high-cardinality fields” when using Use supported liquid clustering for the eligible managed table. The scenario instead tests “A consumer reports unsupported table protocol features after a writer upgrade”; the relevant result is The consumer successfully loads the table's current protocol.

That observation is a valid indicator for “A primary Databricks pipeline needs ACID transactions and Delta features” when using Use a supported Delta table for the curated dataset. The scenario instead tests “A consumer reports unsupported table protocol features after a writer upgrade”; the relevant result is The consumer successfully loads the table's current protocol.

The partner's supported Iceberg reader discovers and queries the expected snapshot pertains to a different control (Use a supported Iceberg table or interoperable format layout for the shared workload) and a different need (An external partner needs Iceberg-compatible open table metadata). It cannot establish that Choose a compatible reader/runtime or a supported migration approach met the stated goal.