You save $34.99
A shared Fabric backlog includes two mandatory controls. First: Each item in a file manifest must be processed by the same notebook without writing 100 nearly identical activities. Second: A notebook needs a different date range on every scheduled invocation without source-code edits. Which two-part implementation satisfies them together?
Step 1 resolves requirement A: Loop activities apply repeatable steps to each collection element. Step 2 resolves requirement B: Parameterized notebook execution separates business run context from transformation logic. Both acceptance tests are required: every input file has one traceable child execution and the configured concurrency limit is respected; and two scheduled runs process distinct requested windows without code changes.
Loop activities apply repeatable steps to each collection element. 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. Loop activities apply repeatable steps to each collection element.
Loop activities apply repeatable steps to each collection element. 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.
The Fabric engineering team must address this requirement: A nightly ingest needs to copy source files to a Lakehouse, then run a notebook and notify an operations group on failure. Which implementation meets the requirement and provides this acceptance evidence: a test run copies files, transforms them and triggers the failure route when the notebook fails?
Pipelines orchestrate multi-step activities with dependency conditions, unlike a single query or notebook. Verify that a test run copies files, transforms them and triggers the failure route when the notebook fails.
Dataflow Gen2 provides visual ingestion/transformation, reducing the need for custom Spark code. However, this alone does not show that a test run copies files, transforms them and triggers the failure route when the notebook fails.
Spark code supports programmable distributed transforms and Delta upsert patterns. However, this alone does not show that a test run copies files, transforms them and triggers the failure route when the notebook fails.
Parameterized notebook execution separates business run context from transformation logic. However, this alone does not show that a test run copies files, transforms them and triggers the failure route when the notebook fails.
A shared Fabric backlog includes two mandatory controls. First: A pipeline Notebook activity succeeds manually but fails from a schedule because one required base parameter is absent. Second: A Spark notebook fails with an executor OOM after a skewed join on a hot customer ID. Which two-part implementation satisfies them together?
Step 1 resolves requirement A: Parameterized execution cannot rely on interactive session variables. Step 2 resolves requirement B: Unbalanced shuffle partitions can exhaust one executor while others remain underutilized. Both acceptance tests are required: scheduled runs receive the expected parameter values and complete; and the hot-key test completes without executor OOM and preserves join results.
Parameterized execution cannot rely on interactive session variables. Unbalanced shuffle partitions can exhaust one executor while others remain underutilized. The proposed steps (Use separate supported queries or remove the conflicting destination assignment; apply explicit type conversion with an error-handling or quarantine branch before writing the numeric destination) address other capabilities instead of this required pair.
Parameterized execution cannot rely on interactive session variables. The other proposed action (apply explicit type conversion with an error-handling or quarantine branch before writing the numeric destination) addresses a different operation. Unbalanced shuffle partitions can exhaust one executor while others remain underutilized.
Unbalanced shuffle partitions can exhaust one executor while others remain underutilized. The other proposed action (Use separate supported queries or remove the conflicting destination assignment) does not implement the first control. Parameterized execution cannot rely on interactive session variables.
A Microsoft Fabric project must complete both tasks before signoff. Task 1: A customer pipeline failed overnight and operators need the exact failing Copy activity, duration and source error. Task 2: An Eventstream's Eventhouse sink stops receiving data although the source connector still appears healthy. Choose exactly TWO controls that collectively meet the requirements.
Source activity does not prove a downstream destination is consuming messages. Confirm that monitoring identifies the stalled destination and the last accepted event.
Run-level status does not replace individual activity diagnostics for failure localization. Confirm 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.
Notebook failures can originate in the Spark job rather than pipeline orchestration.
The data platform team needs a narrowly scoped fix: An ingestion pipeline replays a successful Copy after a downstream failure and duplicates target rows. Which approach satisfies the documented test that rerunning the same batch leaves stable row counts?
Retries and reruns can reexecute completed work, so append-only sinks need duplicate protection. Verify that rerunning the same batch leaves stable row counts.
KQL table name resolution and authorization depend on the selected database context. However, this alone does not show that rerunning the same batch leaves stable row counts.
Many-to-many join expansion can inflate measures even when SQL executes without errors. However, this alone does not show that rerunning the same batch leaves stable row counts.
Conflicting source matches prevent unambiguous one-target-row updates. However, this alone does not show that rerunning the same batch leaves stable row counts.
A Fabric data engineer receives a change request: A Fabric deployment pipeline stage was accidentally assigned to the same workspace as another stage. Which action best produces this measurable result: deployment comparison shows distinct development/test/production workspaces?
Stage separation isolates release scopes so testing does not modify the production workspace. Verify that deployment comparison shows distinct development/test/production workspaces.
Source-controlled definitions should not embed reusable production secrets. However, this alone does not show that deployment comparison shows distinct development/test/production workspaces.
Least-privilege CI/CD identities reduce lateral impact if automation credentials are compromised. However, this alone does not show that deployment comparison shows distinct development/test/production workspaces.
A linked branch does not automatically mean every local workspace change has been committed. However, this alone does not show that deployment comparison shows distinct development/test/production workspaces.
During a Microsoft Fabric deployment review, the following problem is identified: A PySpark join spills heavily because a large fact table joins a tiny static lookup with a full shuffle. The reviewer requires the following result: the physical plan shows the intended join strategy and job runtime improves. What should the engineer implement?
Broadcasting a small table can avoid a costly large-side shuffle. Verify that the physical plan shows the intended join strategy and job runtime improves.
Incremental updates reduce unnecessary reads and rewrites when source change data is available. However, this alone does not show that the physical plan shows the intended join strategy and job runtime improves.
Reducing intermediate row counts can lower join and shuffle cost. However, this alone does not show that the physical plan shows the intended join strategy and job runtime improves.
File compaction reduces small-file overhead and can improve read efficiency. However, this alone does not show that the physical plan shows the intended join strategy and job runtime improves.
After a production change, the runbook records: Use the supported certification/endorsement process for the approved Fabric item. The previous problem was: A highly trusted sales model should be marked as reviewed so analysts can distinguish it from experimental versions. What test result confirms effective remediation?
Endorsement communicates content quality and ownership rather than encryption or data authorization.
OneLake can block unsupported engines when a table requires enforcement of granular row or column restrictions. It does not show that the approved item shows its endorsement status in discovery and unauthorized editing remains blocked.
Item audit events do not alone identify each source row or transformation step. It does not show that the approved item shows its endorsement status in discovery and unauthorized editing remains blocked.
Dynamic data masking changes displayed results for eligible low-privilege readers rather than encrypting stored values. It does not show that the approved item shows its endorsement status in discovery and unauthorized editing remains blocked.
A Fabric data engineer receives a change request: A notebook accidentally converts a huge Spark DataFrame to pandas and crashes the driver. Which action best produces this measurable result: a large dataset runs without driver out-of-memory and outputs correct aggregate results?
Collecting full distributed data to the driver defeats Spark scaling and can exhaust memory. Verify that a large dataset runs without driver out-of-memory and outputs correct aggregate results.
Mirroring depends on source-specific permissions and configuration, not only workspace Reader rights. However, this alone does not show that a large dataset runs without driver out-of-memory and outputs correct aggregate results.
Internal shortcuts avoid redundant copies and simplify data sharing. However, this alone does not show that a large dataset runs without driver out-of-memory and outputs correct aggregate results.
Ingestion validation separates bad source rows from trustworthy analytic data. However, this alone does not show that a large dataset runs without driver out-of-memory and outputs correct aggregate results.
A Fabric data engineering release must address both of these independent requirements: (1) A large dimensional load joins source sales to a dimension that has no corresponding customer key. (2) A source table has no change timestamp and no CDC capability, but changes must be detected reliably each night. Which combined plan meets both without substituting an unrelated change?
Step 1 resolves requirement A: Unknown dimension handling preserves fact integrity without fabricating dimension matches. Step 2 resolves requirement B: Incremental detection must be based on an actual observable change signal. Both acceptance tests are required: facts with missing keys follow the documented fallback and are counted in QA; and modified and removed rows are recognized when two snapshots differ.
Incremental detection must be based on an actual observable change signal. The other proposed action (Stage and validate the new partition, then publish or swap it as a controlled committed step) does not implement the first control. Unknown dimension handling preserves fact integrity without fabricating dimension matches.
Unknown dimension handling preserves fact integrity without fabricating dimension matches. The other proposed action (use a batch load with a completeness check and a committed publish boundary) addresses a different operation. Incremental detection must be based on an actual observable change signal.
Unknown dimension handling preserves fact integrity without fabricating dimension matches. Incremental detection must be based on an actual observable change signal. The proposed steps (Stage and validate the new partition, then publish or swap it as a controlled committed step; use a batch load with a completeness check and a committed publish boundary) address other capabilities instead of this required pair.
The data platform team needs a narrowly scoped fix: A finance ingestion must run at 02:00 daily with no external source event signal. Which approach satisfies the documented test that run history contains the expected daily occurrence at the configured schedule?
Scheduled triggers execute a workflow at defined times independent of source change events. Verify that run history contains the expected daily occurrence at the configured schedule.
Warehouse destinations in Dataflow Gen2 can require staging before the destination write. However, this alone does not show that run history contains the expected daily occurrence at the configured schedule.
Spark code supports programmable distributed transforms and Delta upsert patterns. However, this alone does not show that run history contains the expected daily occurrence at the configured schedule.
Parameterized notebook execution separates business run context from transformation logic. However, this alone does not show that run history contains the expected daily occurrence at the configured schedule.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
