You save $34.99
A production analytics workflow has this requirement: A Dataflow Gen2 query fails after it was configured with two output destinations in its item definition. What is the most appropriate change if success must be shown by this test: each query has one valid destination and publishing succeeds?
A single dataflow query supports a constrained destination configuration; invalid multiples fail validation. Verify that each query has one valid destination and publishing succeeds.
Retries and reruns can reexecute completed work, so append-only sinks need duplicate protection. However, this alone does not show that each query has one valid destination and publishing succeeds.
Dynamic expressions depend on the actual shape of activity JSON output. However, this alone does not show that each query has one valid destination and publishing succeeds.
Shortcuts continue to depend on the external storage connection and current rights. However, this alone does not show that each query has one valid destination and publishing succeeds.
A Microsoft Fabric project must complete both tasks before signoff. Task 1: A large Delta table is commonly filtered by customer_id, but all files are scanned despite the narrow predicate. Task 2: A Dataflow Gen2 with heavy query folding disabled consumes excessive capacity processing raw source rows. Choose exactly TWO controls that collectively meet the requirements.
Early source-side filtering reduces data that the dataflow engine must move and transform. Confirm that fewer records cross the connector and the output aggregates remain correct.
Data layout optimization can improve file pruning for selective queries. Confirm that a before-and-after query reads fewer relevant data files with identical results.
Caching saves recomputation but consumes memory and requires cleanup discipline.
Skewed partitions cause straggler tasks and spill even with high total cluster capacity.
A team is working on two related Fabric work items. Work item A: A Delta Lakehouse table contains millions of tiny files following many microbatch appends and scan time is increasing. Work item B: A Copy activity takes twice as long after a network migration and a teammate proposes raising Spark executor count. Select TWO specific implementation steps.
Data movement bottlenecks can be independent of Spark compute. Confirm that the selected Copy tuning improves transfer MB/s without affecting notebook resources.
File compaction reduces small-file overhead and can improve read efficiency. Confirm that a benchmark shows fewer data files and faster equivalent queries with matching results.
Queued ingestion batching combines small chunks to improve throughput, but adds a bounded freshness delay.
Materialized views maintain precomputed summaries to accelerate repeated analytic queries.
An auditor reviews the applied Fabric control: Use a manifest or completion event and validate expected file counts before starting the load. It was selected to address: A 200 GB nightly file arrives in pieces and the Copy activity starts before all parts are uploaded. Which evidence demonstrates the intended result?
A file-ready boundary prevents reading partially delivered source data.
The first snapshot establishes a baseline; later loads need only changed records. It does not show that the pipeline starts only after all manifest entries are present and valid.
Bronze history and curated current-state views serve different retention and reporting needs. It does not show that the pipeline starts only after all manifest entries are present and valid.
Type 1 updates replace the current attribute without retaining prior versions. It does not show that the pipeline starts only after all manifest entries are present and valid.
The project has two blockers. Blocker A: An Eventhouse ingestion pipeline has rising latency but no application exception. Blocker B: A warehouse analyst wants recent failed and canceled SQL statements correlated to users. What pair of actions resolves both blockers?
Step 1 resolves requirement A: Freshness degradation can occur before a hard ingestion failure. Step 2 resolves requirement B: SQL query monitoring provides query-level facts rather than only Fabric item health. Both acceptance tests are required: an alert triggers when measured ingestion delay exceeds the agreed objective; and the selected canceled query is traced to its recorded request and user.
Freshness degradation can occur before a hard ingestion failure. SQL query monitoring provides query-level facts rather than only Fabric item health. The proposed steps (Capture notebook run metadata, environment reference and execution result; inspect Spark job monitoring and the current concurrency/queue state) address other capabilities instead of this required pair.
SQL query monitoring provides query-level facts rather than only Fabric item health. The other proposed action (Capture notebook run metadata, environment reference and execution result) does not implement the first control. Freshness degradation can occur before a hard ingestion failure.
Freshness degradation can occur before a hard ingestion failure. The other proposed action (inspect Spark job monitoring and the current concurrency/queue state) addresses a different operation. SQL query monitoring provides query-level facts rather than only Fabric item health.
A production analytics workflow has this requirement: A T-SQL transformation needs one row per customer using grouped spend totals. What is the most appropriate change if success must be shown by this test: customer totals reconcile with a reference sum of source transactions?
Relational aggregation collapses transactional detail into grouped measures. Verify that customer totals reconcile with a reference sum of source transactions.
Denormalization trades duplication for simpler downstream analytic reads. However, this alone does not show that customer totals reconcile with a reference sum of source transactions.
Mirroring depends on source-specific permissions and configuration, not only workspace Reader rights. However, this alone does not show that customer totals reconcile with a reference sum of source transactions.
A Lakehouse combines file storage with Delta tables and Spark development. However, this alone does not show that customer totals reconcile with a reference sum of source transactions.
The reviewer will approve this deployment only when it fixes both issues: (a) A Spark notebook repeatedly recomputes the same expensive parsed dataset for several downstream summaries. (b) A warehouse query joins raw transaction detail before aggregating even though the final report needs only per-day totals. Which proposed pair of changes is appropriate?
Step 1 resolves requirement A: Caching saves recomputation but consumes memory and requires cleanup discipline. Step 2 resolves requirement B: Reducing intermediate row counts can lower join and shuffle cost. Both acceptance tests are required: repeated summary stages complete faster without causing memory pressure; and the report totals match a reference query with faster execution.
Caching saves recomputation but consumes memory and requires cleanup discipline. Reducing intermediate row counts can lower join and shuffle cost. The proposed steps (Evaluate and enable the supported optimized copy to Lakehouse setting when staging is enabled; apply a supported V-Order optimization strategy for the selected Delta workload) address other capabilities instead of this required pair.
Caching saves recomputation but consumes memory and requires cleanup discipline. The other proposed action (apply a supported V-Order optimization strategy for the selected Delta workload) addresses a different operation. Reducing intermediate row counts can lower join and shuffle cost.
Reducing intermediate row counts can lower join and shuffle cost. The other proposed action (Evaluate and enable the supported optimized copy to Lakehouse setting when staging is enabled) does not implement the first control. Caching saves recomputation but consumes memory and requires cleanup discipline.
A Fabric engineer has implemented the following change: Use KQL summarize arg_max(timestamp, *) by device_id with validated timestamp semantics. The original requirement was: A KQL query must retrieve the latest device status per device from a stream of updates. Which observation best validates that the change works?
Arg_max selects the row with the greatest time value in each group.
KQL binning groups events into fixed time buckets. It does not show that each device returns one latest known status from the controlled input.
Event-time aggregation distinguishes when a fact occurred from when it was processed. It does not show that each device returns one latest known status from the controlled input.
Eventhouse and Lakehouse serve different real-time query and durable lake storage requirements. It does not show that each device returns one latest known status from the controlled input.
A shared Fabric backlog includes two mandatory controls. First: Business analysts need to clean a small table visually with Power Query and load the result into a supported destination. Second: A team needs one reusable child pipeline called by several source-specific parent pipelines. Which two-part implementation satisfies them together?
Step 1 resolves requirement A: Dataflow Gen2 provides visual ingestion/transformation, reducing the need for custom Spark code. Step 2 resolves requirement B: Pipeline reuse reduces duplicated workflows while retaining explicit input contracts. Both acceptance tests are required: the refreshed destination contains the correctly typed and filtered rows; and two parents invoke the same child with separate source IDs and results stay isolated.
Pipeline reuse reduces duplicated workflows while retaining explicit input contracts. The other proposed action (Use a Fabric notebook or Spark job definition instead of only a visual Dataflow) does not implement the first control. Dataflow Gen2 provides visual ingestion/transformation, reducing the need for custom Spark code.
Dataflow Gen2 provides visual ingestion/transformation, reducing the need for custom Spark code. The other proposed action (define notebook parameters or a supported parameter cell and supply values through the pipeline activity) addresses a different operation. Pipeline reuse reduces duplicated workflows while retaining explicit input contracts.
Dataflow Gen2 provides visual ingestion/transformation, reducing the need for custom Spark code. Pipeline reuse reduces duplicated workflows while retaining explicit input contracts. The proposed steps (Use a Fabric notebook or Spark job definition instead of only a visual Dataflow; define notebook parameters or a supported parameter cell and supply values through the pipeline activity) address other capabilities instead of this required pair.
A Fabric data engineering release must address both of these independent requirements: (1) An external ADLS Gen2 folder must be exposed in a Lakehouse without copying the entire source into Fabric. (2) A Dataflow Gen2 query is configured for Warehouse output but staging is disabled, blocking destination configuration. Which combined plan meets both without substituting an unrelated change?
Step 1 resolves requirement A: Shortcuts present source data under OneLake paths without physically duplicating the source files. Step 2 resolves requirement B: Warehouse dataflow destinations can depend on an intermediate staging path. Both acceptance tests are required: a new external file appears through the shortcut with authorized access; and the dataflow accepts the warehouse destination and refreshes successfully.
Warehouse dataflow destinations can depend on an intermediate staging path. The other proposed action (Evaluate supported Fabric database mirroring for the source and target use case) does not implement the first control. Shortcuts present source data under OneLake paths without physically duplicating the source files.
Shortcuts present source data under OneLake paths without physically duplicating the source files. The other proposed action (correct mirroring source prerequisites and authorization, then restart synchronization) addresses a different operation. Warehouse dataflow destinations can depend on an intermediate staging path.
Shortcuts present source data under OneLake paths without physically duplicating the source files. Warehouse dataflow destinations can depend on an intermediate staging path. The proposed steps (Evaluate supported Fabric database mirroring for the source and target use case; correct mirroring source prerequisites and authorization, then restart synchronization) address other capabilities instead of this required pair.
An enterprise Fabric solution must resolve this issue: A customer pipeline failed overnight and operators need the exact failing Copy activity, duration and source error. The acceptance criterion is: the report identifies the failing activity, run ID, error and elapsed time. Which implementation should be selected?
Run-level status does not replace individual activity diagnostics for failure localization. Verify that the report identifies the failing activity, run ID, error and elapsed time.
Editing/publishing validation and scheduled refresh are distinct operational states. However, this alone does not show that the report identifies the failing activity, run ID, error and elapsed time.
SQL query monitoring provides query-level facts rather than only Fabric item health. However, this alone does not show that the report identifies the failing activity, run ID, error and elapsed time.
Notebook failures can originate in the Spark job rather than pipeline orchestration. However, this alone does not show that the report identifies the failing activity, run ID, error and elapsed time.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
