Exam Bundle

The stream detects a new column, updates schema metadata and resumes after restart would demonstrate the separate action Configure Auto Loader `addNewColumns` and a persistent schemaLocation, which addresses “New JSON attributes should become accepted target columns after a managed restart.” It does not verify the requirement “An existing schema location was deleted and streaming now cannot reliably recover its previous schema” following Restore the persisted Auto Loader schema directory from backup or safely rebootstrap.

The target schema includes the approved field with existing rows preserved pertains to a different control (Allow the supported schema evolution update and restart as required) and a different need (An optional field appears for the first time and is approved for schema evolution). It cannot establish that Restore the persisted Auto Loader schema directory from backup or safely rebootstrap met the stated goal.

This signal belongs to the adjacent case “A foreign schema evolves and analysts cannot see a new remote column,” whose remedy is Refresh the supported foreign catalog metadata or mappings. The observed result for the present requirement is The stream resumes with the expected column definitions and history state.

The alternative Assign separate source path and stream checkpoint to each ingestion stream has a distinct purpose—Two independent source directories feed two different bronze tables. It would not establish the required outcome (The source container has high object count and low-latency event-based discovery is required); the necessary verification concerns Files are discovered through events without a costly whole-container listing.

This action solves a different issue: “A file-notification source reports files out of original creation order.” Its normal signal is Out-of-order arrivals produce correct logical records. Here the requested behavior is “The source container has high object count and low-latency event-based discovery is required,” so that signal is not sufficient.

This action solves a different issue: “A stream retries processing after a transient worker crash.” Its normal signal is The restart does not logically duplicate previously committed files. Here the requested behavior is “The source container has high object count and low-latency event-based discovery is required,” so that signal is not sufficient.

Each target advances only for its own discovered files would demonstrate the separate action Assign separate source path and stream checkpoint to each ingestion stream, which addresses “Two independent source directories feed two different bronze tables.” It does not verify the requirement “The source container has high object count and low-latency event-based discovery is required” following Choose supported Auto Loader file-event notification mode.

The restart does not logically duplicate previously committed files pertains to a different control (Keep the durable checkpoint and write to a transactionally safe Delta sink) and a different need (A stream retries processing after a transient worker crash). It cannot establish that Choose supported Auto Loader file-event notification mode met the stated goal.

Out-of-order arrivals produce correct logical records pertains to a different control (Make downstream transformations order-independent or sequence by event metadata) and a different need (A file-notification source reports files out of original creation order). It cannot establish that Choose supported Auto Loader file-event notification mode met the stated goal.

Choose supported Auto Loader file-event notification mode is appropriate when “The source container has high object count and low-latency event-based discovery is required”; it would be verified by Files are discovered through events without a costly whole-container listing. It does not directly satisfy “Two independent source directories feed two different bronze tables,” whose relevant acceptance evidence is Each target advances only for its own discovered files.

This action solves a different issue: “A file-notification source reports files out of original creation order.” Its normal signal is Out-of-order arrivals produce correct logical records. Here the requested behavior is “Two independent source directories feed two different bronze tables,” so that signal is not sufficient.

Keep the durable checkpoint and write to a transactionally safe Delta sink is appropriate when “A stream retries processing after a transient worker crash”; it would be verified by The restart does not logically duplicate previously committed files. It does not directly satisfy “Two independent source directories feed two different bronze tables,” whose relevant acceptance evidence is Each target advances only for its own discovered files.

Out-of-order arrivals produce correct logical records pertains to a different control (Make downstream transformations order-independent or sequence by event metadata) and a different need (A file-notification source reports files out of original creation order). It cannot establish that Assign separate source path and stream checkpoint to each ingestion stream met the stated goal.

That observation is a valid indicator for “The source container has high object count and low-latency event-based discovery is required” when using Choose supported Auto Loader file-event notification mode. The scenario instead tests “Two independent source directories feed two different bronze tables”; the relevant result is Each target advances only for its own discovered files.

That observation is a valid indicator for “The team changes from directory listing to file notifications midstream” when using Preserve the query checkpoint while switching to supported notification mode. The scenario instead tests “Two independent source directories feed two different bronze tables”; the relevant result is Each target advances only for its own discovered files.

The alternative Assign separate source path and stream checkpoint to each ingestion stream has a distinct purpose—Two independent source directories feed two different bronze tables. It would not establish the required outcome (A stream retries processing after a transient worker crash); the necessary verification concerns The restart does not logically duplicate previously committed files.

The alternative Choose supported Auto Loader file-event notification mode has a distinct purpose—The source container has high object count and low-latency event-based discovery is required. It would not establish the required outcome (A stream retries processing after a transient worker crash); the necessary verification concerns The restart does not logically duplicate previously committed files.

The alternative Make downstream transformations order-independent or sequence by event metadata has a distinct purpose—A file-notification source reports files out of original creation order. It would not establish the required outcome (A stream retries processing after a transient worker crash); the necessary verification concerns The restart does not logically duplicate previously committed files.

This signal belongs to the adjacent case “A file-notification source reports files out of original creation order,” whose remedy is Make downstream transformations order-independent or sequence by event metadata. The observed result for the present requirement is The restart does not logically duplicate previously committed files.

Subsequent arrivals are discovered without replaying committed input would demonstrate the separate action Preserve the query checkpoint while switching to supported notification mode, which addresses “The team changes from directory listing to file notifications midstream.” It does not verify the requirement “A stream retries processing after a transient worker crash” following Keep the durable checkpoint and write to a transactionally safe Delta sink.

Files are discovered through events without a costly whole-container listing pertains to a different control (Choose supported Auto Loader file-event notification mode) and a different need (The source container has high object count and low-latency event-based discovery is required). It cannot establish that Keep the durable checkpoint and write to a transactionally safe Delta sink met the stated goal.

Assign separate source path and stream checkpoint to each ingestion stream belongs to the separate case “Two independent source directories feed two different bronze tables,” where Each target advances only for its own discovered files would be expected. That differs from the condition in this stem: “The team changes from directory listing to file notifications midstream.”

This action solves a different issue: “The source container has high object count and low-latency event-based discovery is required.” Its normal signal is Files are discovered through events without a costly whole-container listing. Here the requested behavior is “The team changes from directory listing to file notifications midstream,” so that signal is not sufficient.

Make downstream transformations order-independent or sequence by event metadata is appropriate when “A file-notification source reports files out of original creation order”; it would be verified by Out-of-order arrivals produce correct logical records. It does not directly satisfy “The team changes from directory listing to file notifications midstream,” whose relevant acceptance evidence is Subsequent arrivals are discovered without replaying committed input.

Files are discovered through events without a costly whole-container listing pertains to a different control (Choose supported Auto Loader file-event notification mode) and a different need (The source container has high object count and low-latency event-based discovery is required). It cannot establish that Preserve the query checkpoint while switching to supported notification mode met the stated goal.

Out-of-order arrivals produce correct logical records would demonstrate the separate action Make downstream transformations order-independent or sequence by event metadata, which addresses “A file-notification source reports files out of original creation order.” It does not verify the requirement “The team changes from directory listing to file notifications midstream” following Preserve the query checkpoint while switching to supported notification mode.

The restart does not logically duplicate previously committed files pertains to a different control (Keep the durable checkpoint and write to a transactionally safe Delta sink) and a different need (A stream retries processing after a transient worker crash). It cannot establish that Preserve the query checkpoint while switching to supported notification mode met the stated goal.

Preserve the query checkpoint while switching to supported notification mode is appropriate when “The team changes from directory listing to file notifications midstream”; it would be verified by Subsequent arrivals are discovered without replaying committed input. It does not directly satisfy “A file-notification source reports files out of original creation order,” whose relevant acceptance evidence is Out-of-order arrivals produce correct logical records.

Choose supported Auto Loader file-event notification mode belongs to the separate case “The source container has high object count and low-latency event-based discovery is required,” where Files are discovered through events without a costly whole-container listing would be expected. That differs from the condition in this stem: “A file-notification source reports files out of original creation order.”

The alternative Assign separate source path and stream checkpoint to each ingestion stream has a distinct purpose—Two independent source directories feed two different bronze tables. It would not establish the required outcome (A file-notification source reports files out of original creation order); the necessary verification concerns Out-of-order arrivals produce correct logical records.

Files are discovered through events without a costly whole-container listing pertains to a different control (Choose supported Auto Loader file-event notification mode) and a different need (The source container has high object count and low-latency event-based discovery is required). It cannot establish that Make downstream transformations order-independent or sequence by event metadata met the stated goal.

Each target advances only for its own discovered files would demonstrate the separate action Assign separate source path and stream checkpoint to each ingestion stream, which addresses “Two independent source directories feed two different bronze tables.” It does not verify the requirement “A file-notification source reports files out of original creation order” following Make downstream transformations order-independent or sequence by event metadata.

Subsequent arrivals are discovered without replaying committed input pertains to a different control (Preserve the query checkpoint while switching to supported notification mode) and a different need (The team changes from directory listing to file notifications midstream). It cannot establish that Make downstream transformations order-independent or sequence by event metadata met the stated goal.