You save $34.99
A Microsoft Fabric project must complete both tasks before signoff. Task 1: A telemetry producer publishes data to an Eventstream but a consumer reads no events because its destination is disconnected. Task 2: KQL queries over a frequently reused Delta shortcut are too slow, but the source should remain in OneLake. Choose exactly TWO controls that collectively meet the requirements.
The stream must have an active compatible destination for events to be materialized there. Confirm that a test message travels from source through the configured path to the sink.
Query acceleration caches relevant shortcut data for faster queries while retaining source storage. Confirm that the benchmark shows improved query latency with source freshness inside the approved window.
Checkpoint compatibility depends on sources, grouping keys, operators and state schema.
A too-short watermark can exclude valid late events; a longer delay retains more state.
After a production change, the runbook records: Review the destination mapping and normalize incompatible event types before ingestion. The previous problem was: An Eventstream destination table rejects events after a new field type was introduced in source JSON. What test result confirms effective remediation?
Schema drift can break a streaming destination even when the source remains connected.
System-created staging permissions can be tied to an original owner and may outlive a user's access. It does not show that both old and new valid event shapes map correctly or are quarantined by policy.
Expired source access interrupts ingestion even if the KQL query syntax is valid. It does not show that both old and new valid event shapes map correctly or are quarantined by policy.
An authentication failure must be fixed at the connection boundary, not by changing data mapping. It does not show that both old and new valid event shapes map correctly or are quarantined by policy.
The project has two blockers. Blocker A: A data pipeline has to branch based on an extracted row-count threshold before loading a warehouse. Blocker B: A notebook needs a different date range on every scheduled invocation without source-code edits. What pair of actions resolves both blockers?
Step 1 resolves requirement A: Conditional orchestration can route execution based on prior activity outputs. Step 2 resolves requirement B: Parameterized notebook execution separates business run context from transformation logic. Both acceptance tests are required: a low-row-count test takes the exception path and a valid count follows the load branch; and two scheduled runs process distinct requested windows without code changes.
Conditional orchestration can route execution based on prior activity outputs. Parameterized notebook execution separates business run context from transformation logic. The proposed steps (Review the Dataflow Gen2 destination mapping and configured write method before publishing; use a Dataflow Gen2 with Power Query transformations and a configured data destination) address other capabilities instead of this required pair.
Conditional orchestration can route execution based on prior activity outputs. The other proposed action (use a Dataflow Gen2 with Power Query transformations and a configured data destination) addresses a different operation. Parameterized notebook execution separates business run context from transformation logic.
Parameterized notebook execution separates business run context from transformation logic. The other proposed action (Review the Dataflow Gen2 destination mapping and configured write method before publishing) does not implement the first control. Conditional orchestration can route execution based on prior activity outputs.
An auditor reviews the applied Fabric control: Inspect computed dynamic expression values and checkpoint bounds for the failing run. It was selected to address: A Copy activity loads zero records because an incremental filter uses the next day instead of the stored watermark. Which evidence demonstrates the intended result?
Incorrect filter boundaries cause silent logical data loss even with technically successful Copy activity.
Expired source access interrupts ingestion even if the KQL query syntax is valid. It does not show that a representative changed row falls inside the corrected extraction window.
Many-to-many join expansion can inflate measures even when SQL executes without errors. It does not show that a representative changed row falls inside the corrected extraction window.
KQL table name resolution and authorization depend on the selected database context. It does not show that a representative changed row falls inside the corrected extraction window.
A data engineer must validate the completed action: Use supported single-column statistics and query-shape/indexing alternatives based on actual engine capabilities. It targets this failure: An engineer proposes creating composite multi-column histogram statistics in Fabric Warehouse to fix every join. Which test outcome should be accepted?
Fabric Warehouse manual statistics support is narrower than general SQL Server feature assumptions.
VACUUM removes files no longer needed beyond the retention threshold; aggressive cleanup can break readers or history. It does not show that the chosen supported statistics commands execute and queries improve or are safely rolled back.
Excessive partition cardinality creates metadata and file overhead that can dominate scans. It does not show that the chosen supported statistics commands execute and queries improve or are safely rolled back.
Optimized staged-to-Lakehouse copy can avoid extra serialization and transfer overhead. It does not show that the chosen supported statistics commands execute and queries improve or are safely rolled back.
The data platform team needs a narrowly scoped fix: A OneLake shortcut reports access denied after a storage account key was rotated. Which approach satisfies the documented test that the authorized reader lists the expected remote files without broader storage grants?
Shortcuts continue to depend on the external storage connection and current rights. Verify that the authorized reader lists the expected remote files without broader storage grants.
An authentication failure must be fixed at the connection boundary, not by changing data mapping. However, this alone does not show that the authorized reader lists the expected remote files without broader storage grants.
Type overflow creates a deterministic mapping failure, not a transient network fault. However, this alone does not show that the authorized reader lists the expected remote files without broader storage grants.
Expired source access interrupts ingestion even if the KQL query syntax is valid. However, this alone does not show that the authorized reader lists the expected remote files without broader storage grants.
The project has two blockers. Blocker A: A data security incident requires both Fabric item activity history and source-data lineage from a pipeline. Blocker B: A workspace reader is allowed to view a semantic model but must not alter its definition. What pair of actions resolves both blockers?
Step 1 resolves requirement A: Item audit events do not alone identify each source row or transformation step. Step 2 resolves requirement B: Item-specific usage rights can be narrower than contributor permissions to change Fabric artifacts. Both acceptance tests are required: an investigation links the responsible identity and job to the source and destination artifacts; and the user performs the allowed read/query action but cannot edit model definition or deploy changes.
Item audit events do not alone identify each source row or transformation step. The other proposed action (apply appropriate Microsoft Purview sensitivity labels to the supported Fabric items) addresses a different operation. Item-specific usage rights can be narrower than contributor permissions to change Fabric artifacts.
Item audit events do not alone identify each source row or transformation step. Item-specific usage rights can be narrower than contributor permissions to change Fabric artifacts. The proposed steps (Apply labels/endorsement for classification and trust, and separately collect supported audit activity; apply appropriate Microsoft Purview sensitivity labels to the supported Fabric items) address other capabilities instead of this required pair.
Item-specific usage rights can be narrower than contributor permissions to change Fabric artifacts. The other proposed action (Apply labels/endorsement for classification and trust, and separately collect supported audit activity) does not implement the first control. Item audit events do not alone identify each source row or transformation step.
An auditor reviews the applied Fabric control: Use a pipeline or scheduled notebook for the defined batch reconciliation unless low-latency streaming is required. It was selected to address: An engineer plans to solve a batch nightly sales reconciliation using Eventstream solely because the records are in JSON. Which evidence demonstrates the intended result?
Streaming imposes state and always-on operation costs that a finite batch task may not need.
Eventhouse and Lakehouse serve different real-time query and durable lake storage requirements. It does not show that one complete nightly batch reconciles totals without unnecessary continuous event processing.
Schema mapping makes raw event properties accessible as KQL columns. It does not show that one complete nightly batch reconciles totals without unnecessary continuous event processing.
Event-time aggregation distinguishes when a fact occurred from when it was processed. It does not show that one complete nightly batch reconciles totals without unnecessary continuous event processing.
An enterprise Fabric solution must resolve this issue: A time-series report must retain the original event_time for late sensor readings instead of assigning the arrival minute. The acceptance criterion is: a delayed reading contributes to the correct historical event-time bucket. Which implementation should be selected?
Event-time aggregation distinguishes when a fact occurred from when it was processed. Verify that a delayed reading contributes to the correct historical event-time bucket.
Arg_max selects the row with the greatest time value in each group. However, this alone does not show that a delayed reading contributes to the correct historical event-time bucket.
Overly long watermark delays retain unnecessary window or join state. However, this alone does not show that a delayed reading contributes to the correct historical event-time bucket.
A stream can distribute selected events to more than one supported consumer. However, this alone does not show that a delayed reading contributes to the correct historical event-time bucket.
An enterprise Fabric solution must resolve this issue: Direct Lake reporting over a Delta table is slow because newly written files lack read-optimized organization. The acceptance criterion is: a benchmark demonstrates improved read time without changing table content. Which implementation should be selected?
V-Order organizes Parquet layout to favor supported Fabric analytic readers. Verify that a benchmark demonstrates improved read time without changing table content.
Broadcasting a small table can avoid a costly large-side shuffle. However, this alone does not show that a benchmark demonstrates improved read time without changing table content.
Staging data typically has few rereads, so its write compression overhead may outweigh read benefit. However, this alone does not show that a benchmark demonstrates improved read time without changing table content.
Skewed partitions cause straggler tasks and spill even with high total cluster capacity. However, this alone does not show that a benchmark demonstrates improved read time without changing table content.
A data engineer must validate the completed action: Set a durable, unique checkpointLocation in OneLake for that streaming query. It targets this failure: Spark Structured Streaming must resume a Delta write after a compute restart without rereading every event as new. Which test outcome should be accepted?
Checkpoints persist streaming offsets, progress and state for recoverable jobs.
The stream must have an active compatible destination for events to be materialized there. It does not show that a restarted query continues from committed progress without duplicating Delta output.
Make-series generates regular time bins, including configured defaults for empty periods. It does not show that a restarted query continues from committed progress without duplicating Delta output.
Arg_max selects the row with the greatest time value in each group. It does not show that a restarted query continues from committed progress without duplicating Delta output.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
