You save $34.99
A data engineer must validate the completed action: Tune read/shuffle partition counts to match data volume and executor capacity. It targets this failure: A Spark job creates 5,000 partitions for a small 500 MB input and spends more time scheduling than computing. Which test outcome should be accepted?
Too many tiny tasks increase scheduling overhead and file output fragmentation.
Incremental updates reduce unnecessary reads and rewrites when source change data is available. It does not show that the same workload completes faster with a reasonable number of partitions.
Controlled concurrency can reduce end-to-end pipeline runtime without saturating dependencies. It does not show that the same workload completes faster with a reasonable number of partitions.
Column pruning and selective filters reduce unnecessary data scan and transfer. It does not show that the same workload completes faster with a reasonable number of partitions.
A Fabric release must resolve two independent technical requirements. Requirement A: An event source can update or delete records, making a simple append-only incremental filter insufficient. Requirement B: Customer mailing addresses change and auditors must query the historical address at the time of each sale. Select TWO actions that directly satisfy both requirements.
CDC retains insert/update/delete semantics that append-only loading may lose. Confirm that a changed source record updates one target row and a deletion is handled per policy.
Type 2 slowly changing dimensions preserve prior attribute versions rather than overwriting history. Confirm that a historical sale resolves to the address version valid on its sale date.
Streaming architectures ingest and query events with low delay compared with scheduled batch loads.
Namespace and batch isolation prevent filename collisions across producers.
The reviewer will approve this deployment only when it fixes both issues: (a) Business analysts need to clean a small table visually with Power Query and load the result into a supported destination. (b) A notebook needs a different date range on every scheduled invocation without source-code edits. Which proposed pair of changes is appropriate?
Step 1 resolves requirement A: Dataflow Gen2 provides visual ingestion/transformation, reducing the need for custom Spark code. Step 2 resolves requirement B: Parameterized notebook execution separates business run context from transformation logic. Both acceptance tests are required: the refreshed destination contains the correctly typed and filtered rows; and two scheduled runs process distinct requested windows without code changes.
Dataflow Gen2 provides visual ingestion/transformation, reducing the need for custom Spark code. Parameterized notebook execution separates business run context from transformation logic. The proposed steps (Configure a pipeline schedule with correct timezone and recurrence; define pipeline parameters and pass the intended parameter map to the Notebook activity) address other capabilities instead of this required pair.
Dataflow Gen2 provides visual ingestion/transformation, reducing the need for custom Spark code. The other proposed action (define pipeline parameters and pass the intended parameter map to the Notebook activity) 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 (Configure a pipeline schedule with correct timezone and recurrence) does not implement the first control. Dataflow Gen2 provides visual ingestion/transformation, reducing the need for custom Spark code.
A Microsoft Fabric project must complete both tasks before signoff. Task 1: Operations needs ten-minute averages recalculated every two minutes over a live signal. Task 2: A KQL database should query an existing OneLake Delta dataset without reingesting every row into a native table. Choose exactly TWO controls that collectively meet the requirements.
A OneLake shortcut exposes external Delta data for KQL querying without a full ingestion copy. Confirm that a source change becomes visible through the shortcut with appropriate permissions.
Overlapping hopping windows recompute aggregates over sliding intervals. Confirm that a source event participates in the correct overlapping windows.
Checkpoints persist streaming offsets, progress and state for recoverable jobs.
A too-short watermark can exclude valid late events; a longer delay retains more state.
An auditor reviews the applied Fabric control: Replace full overwrite with an incremental Delta MERGE or change feed load keyed by stable IDs. It was selected to address: A Lakehouse table is repeatedly rewritten in full even when only 1% of records change. Which evidence demonstrates the intended result?
Incremental updates reduce unnecessary reads and rewrites when source change data is available.
Column statistics support cost-based query planning without forcing a specific data distribution. It does not show that updated rows are correct and the write volume falls compared with full refresh.
Materialized views maintain precomputed summaries to accelerate repeated analytic queries. It does not show that updated rows are correct and the write volume falls compared with full refresh.
Optimized staged-to-Lakehouse copy can avoid extra serialization and transfer overhead. It does not show that updated rows are correct and the write volume falls compared with full refresh.
A Fabric data engineering release must address both of these independent requirements: (1) A telemetry stream needs operational querying by KQL and durable Delta storage for long-term batch analytics. (2) An Eventstream must fan out identical data to an application endpoint and an Eventhouse table. Which combined plan meets both without substituting an unrelated change?
Step 1 resolves requirement A: Eventhouse and Lakehouse serve different real-time query and durable lake storage requirements. Step 2 resolves requirement B: A stream can distribute selected events to more than one supported consumer. Both acceptance tests are required: one test event is queryable in Eventhouse and lands in the targeted Delta table; and a correlated event identifier is observed in both sinks once under the expected semantics.
Eventhouse and Lakehouse serve different real-time query and durable lake storage requirements. The other proposed action (parse with an explicit schema and route malformed rows to a quarantine output) addresses a different operation. A stream can distribute selected events to more than one supported consumer.
Eventhouse and Lakehouse serve different real-time query and durable lake storage requirements. A stream can distribute selected events to more than one supported consumer. The proposed steps (Set a durable, unique checkpointLocation in OneLake for that streaming query; parse with an explicit schema and route malformed rows to a quarantine output) address other capabilities instead of this required pair.
A stream can distribute selected events to more than one supported consumer. The other proposed action (Set a durable, unique checkpointLocation in OneLake for that streaming query) does not implement the first control. Eventhouse and Lakehouse serve different real-time query and durable lake storage requirements.
The Fabric engineering team must address this requirement: An internal shortcut works for workspace admins but not for a new Viewer. Which implementation meets the requirement and provides this acceptance evidence: the Viewer reads only intended shortcut data after scoped access is granted?
Admins can inherit broader data access than a Viewer; shortcut visibility is not universal authorization. Verify that the Viewer reads only intended shortcut data after scoped access is granted.
Dataflow source/query schema and destination mapping must agree. However, this alone does not show that the Viewer reads only intended shortcut data after scoped access is granted.
Schema drift can break a streaming destination even when the source remains connected. However, this alone does not show that the Viewer reads only intended shortcut data after scoped access is granted.
Type overflow creates a deterministic mapping failure, not a transient network fault. However, this alone does not show that the Viewer reads only intended shortcut data after scoped access is granted.
A shared Fabric backlog includes two mandatory controls. First: A reader requires both a row filter and a column filter on a OneLake table, but the team plans to put them in separate roles. Second: A data security incident requires both Fabric item activity history and source-data lineage from a pipeline. Which two-part implementation satisfies them together?
Step 1 resolves requirement A: Combining row and column filters in unsupported separate roles can cause query errors. Step 2 resolves requirement B: Item audit events do not alone identify each source row or transformation step. Both acceptance tests are required: the user reads only the allowed rows and columns with no role-combination error; and an investigation links the responsible identity and job to the source and destination artifacts.
Item audit events do not alone identify each source row or transformation step. The other proposed action (Apply labels/endorsement for classification and trust, and separately collect supported audit activity) does not implement the first control. Combining row and column filters in unsupported separate roles can cause query errors.
Combining row and column filters in unsupported separate roles can cause query errors. Item audit events do not alone identify each source row or transformation step. 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.
Combining row and column filters in unsupported separate roles can cause query errors. The other proposed action (apply appropriate Microsoft Purview sensitivity labels to the supported Fabric items) addresses a different operation. Item audit events do not alone identify each source row or transformation step.
An enterprise Fabric solution must resolve this issue: A pipeline must pass an environment-specific Lakehouse name into the notebook it invokes. The acceptance criterion is: a test run logs the target environment identifier and writes only to that destination. Which implementation should be selected?
Explicit parameter mapping makes notebook execution independent of hardcoded environment names. Verify that a test run logs the target environment identifier and writes only to that destination.
Query transformations and data destination settings are separate deployment concerns. However, this alone does not show that a test run logs the target environment identifier and writes only to that destination.
Parameterized notebook execution separates business run context from transformation logic. However, this alone does not show that a test run logs the target environment identifier and writes only to that destination.
Spark code supports programmable distributed transforms and Delta upsert patterns. However, this alone does not show that a test run logs the target environment identifier and writes only to that destination.
A data engineer must validate the completed action: Inspect supported-item dependencies and deployment comparison before promoting related items together. It targets this failure: A deployment is reported successful, but an item referenced by a notebook was not included in the promotion. Which test outcome should be accepted?
Item definitions may rely on other items or connection bindings that need independent promotion.
A linked branch does not automatically mean every local workspace change has been committed. It does not show that the destination resolves every required referenced item before jobs are enabled.
Branch-based review resolves competing definition edits before a shared release branch is updated. It does not show that the destination resolves every required referenced item before jobs are enabled.
A Git merge does not necessarily update every connected workspace or deployment stage. It does not show that the destination resolves every required referenced item before jobs are enabled.
An auditor reviews the applied Fabric control: Parse with an explicit schema and route malformed rows to a quarantine output. It was selected to address: A streaming source emits JSON with an optional temperature field and parsing failures terminate the job. Which evidence demonstrates the intended result?
Separating invalid records from typed valid rows allows streaming jobs to continue safely.
Overlapping hopping windows recompute aggregates over sliding intervals. It does not show that a malformed test record is quarantined while valid events remain queryable.
The stream must have an active compatible destination for events to be materialized there. It does not show that a malformed test record is quarantined while valid events remain queryable.
Native tables store ingested data inside the KQL database for efficient query patterns. It does not show that a malformed test record is quarantined while valid events remain queryable.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
