You save $34.99
An enterprise Fabric solution must resolve this issue: A Lakehouse batch produces thousands of small files because each upstream region writes to a separate tiny partition. The acceptance criterion is: partition/file counts fall and the target read benchmark improves without missing regions. Which implementation should be selected?
Excessive partition cardinality creates metadata and file overhead that can dominate scans. Verify that partition/file counts fall and the target read benchmark improves without missing regions.
Data movement bottlenecks can be independent of Spark compute. However, this alone does not show that partition/file counts fall and the target read benchmark improves without missing regions.
Column pruning and selective filters reduce unnecessary data scan and transfer. However, this alone does not show that partition/file counts fall and the target read benchmark improves without missing regions.
Staging data typically has few rereads, so its write compression overhead may outweigh read benefit. However, this alone does not show that partition/file counts fall and the target read benchmark improves without missing regions.
A Fabric data engineer receives a change request: The finance team needs proof that a Spark notebook ran against its approved production environment and runtime. Which action best produces this measurable result: an audit record links a published table to the notebook run and runtime configuration?
Run provenance identifies the environment that produced a dataset. Verify that an audit record links a published table to the notebook run and runtime configuration.
Monitoring visibility can be separated from authoring or item modification privileges. However, this alone does not show that an audit record links a published table to the notebook run and runtime configuration.
Run-level status does not replace individual activity diagnostics for failure localization. However, this alone does not show that an audit record links a published table to the notebook run and runtime configuration.
Upstream data arrival is separate from semantic model refresh completion. However, this alone does not show that an audit record links a published table to the notebook run and runtime configuration.
A Fabric release must resolve two independent technical requirements. Requirement A: A PySpark transformation runs out of driver memory after calling collect() on a huge DataFrame. Requirement B: An Eventhouse KQL ingestion mapping rejects payloads whose timestamp arrives as an unparseable text field. Select TWO actions that directly satisfy both requirements.
Collect moves data to driver memory and can exhaust it irrespective of executor capacity. Confirm that a large input completes with bounded driver memory consumption.
KQL ingestion requires compatible column types and valid mapping expressions. Confirm that a test event lands with a correct datetime column and no mapping error.
Parameterized execution cannot rely on interactive session variables.
Rate limiting is generally transient and worsens with uncontrolled immediate retries.
The data platform team needs a narrowly scoped fix: A Spark job's largest customer accounts put nearly all join records in one partition. Which approach satisfies the documented test that task durations become more balanced with unchanged join results?
Skewed partitions cause straggler tasks and spill even with high total cluster capacity. Verify that task durations become more balanced with unchanged join results.
Limiting extraction to changed files avoids redundant input/output work. However, this alone does not show that task durations become more balanced with unchanged join results.
Data layout optimization can improve file pruning for selective queries. However, this alone does not show that task durations become more balanced with unchanged join results.
Fabric Warehouse manual statistics support is narrower than general SQL Server feature assumptions. However, this alone does not show that task durations become more balanced with unchanged join results.
The reviewer will approve this deployment only when it fixes both issues: (a) A team needs KQL queries over continuously arriving event logs and time-series telemetry. (b) A shortcut was created but users assume it permanently copies data even if source permissions are revoked. Which proposed pair of changes is appropriate?
Step 1 resolves requirement A: Eventhouse supports KQL-based event exploration and real-time analytics. Step 2 resolves requirement B: A shortcut is a reference to data, not an independently secured copy with unlimited access. Both acceptance tests are required: new event records are searchable by KQL with the required freshness; and an unauthorized reader is denied at the shortcut/source boundary.
Eventhouse supports KQL-based event exploration and real-time analytics. The other proposed action (enable the required staging and verify the chosen Warehouse destination) addresses a different operation. A shortcut is a reference to data, not an independently secured copy with unlimited access.
A shortcut is a reference to data, not an independently secured copy with unlimited access. The other proposed action (Use GROUP BY with aggregate functions in a supported warehouse query) does not implement the first control. Eventhouse supports KQL-based event exploration and real-time analytics.
Eventhouse supports KQL-based event exploration and real-time analytics. A shortcut is a reference to data, not an independently secured copy with unlimited access. The proposed steps (Use GROUP BY with aggregate functions in a supported warehouse query; enable the required staging and verify the chosen Warehouse destination) address other capabilities instead of this required pair.
The Fabric engineering team must address this requirement: A Dataflow Gen2 refresh fails with a Power Query conversion error because an amount column now contains the string N/A in several source rows. Which implementation meets the requirement and provides this acceptance evidence: rows with valid amounts load as numbers and invalid source values are captured for remediation?
Invalid source text causes a deterministic type-conversion failure that extra retries or staging changes cannot repair. Verify that rows with valid amounts load as numbers and invalid source values are captured for remediation.
An authentication failure must be fixed at the connection boundary, not by changing data mapping. However, this alone does not show that rows with valid amounts load as numbers and invalid source values are captured for remediation.
Type overflow creates a deterministic mapping failure, not a transient network fault. However, this alone does not show that rows with valid amounts load as numbers and invalid source values are captured for remediation.
KQL table name resolution and authorization depend on the selected database context. However, this alone does not show that rows with valid amounts load as numbers and invalid source values are captured for remediation.
A Fabric data engineer receives a change request: An external consumer has an item Read grant but cannot read Lakehouse data through a supported OneLake endpoint. Which action best produces this measurable result: the intended user can query the approved data and not a protected neighboring table?
Item visibility and data-plane read rights can be independently evaluated. Verify that the intended user can query the approved data and not a protected neighboring table.
Item audit events do not alone identify each source row or transformation step. However, this alone does not show that the intended user can query the approved data and not a protected neighboring table.
Promotion is a discoverability signal; certification requires an authorized organizational review process. However, this alone does not show that the intended user can query the approved data and not a protected neighboring table.
Sensitivity labels mark data classification and inform downstream governance; they do not automatically grant read access. However, this alone does not show that the intended user can query the approved data and not a protected neighboring table.
The data platform team needs a narrowly scoped fix: A 40-million-row transform has large duplicate groups and deduplication must follow business priority rules. Which approach satisfies the documented test that repeated runs select the same winning record for each business key?
Deterministic precedence avoids unpredictable retained records. Verify that repeated runs select the same winning record for each business key.
Mirroring replicates supported source changes into Fabric with managed synchronization. However, this alone does not show that repeated runs select the same winning record for each business key.
Explicit conversion protects numerical fidelity during ingestion. However, this alone does not show that repeated runs select the same winning record for each business key.
Power Query-based dataflow transformations suit low-code batch shaping. However, this alone does not show that repeated runs select the same winning record for each business key.
A Fabric engineer has implemented the following change: Configure a narrowly authorized deployment identity and scoped pipeline permissions. The original requirement was: An automated deployment is using an overprivileged owner credential even though the release updates only two selected items. Which observation best validates that the change works?
Least-privilege CI/CD identities reduce lateral impact if automation credentials are compromised.
Automated release operations require explicit identity and API permissions independent of interactive workspace ownership. It does not show that the release can update approved items and is denied on an unrelated workspace.
Reverting item definitions is a separate action from restoring underlying data that may have changed. It does not show that the release can update approved items and is denied on an unrelated workspace.
Environment comparison reveals additions, deletions and changed definitions before an update. It does not show that the release can update approved items and is denied on an unrelated workspace.
A data engineer must validate the completed action: Use supported Fabric item/deployment REST APIs with an appropriately authorized service principal. It targets this failure: A CI/CD system must promote item definitions to a destination Fabric workspace with no interactive user access. Which test outcome should be accepted?
Automated release operations require explicit identity and API permissions independent of interactive workspace ownership.
Source-controlled definitions should not embed reusable production secrets. It does not show that a pipeline release updates only the intended workspace and produces an auditable run record.
Database projects make selected relational schemas deployable and reviewable as source artifacts. It does not show that a pipeline release updates only the intended workspace and produces an auditable run record.
Database schema deployment can have destructive consequences even when a source diff is syntactically valid. It does not show that a pipeline release updates only the intended workspace and produces an auditable run record.
A shared Fabric backlog includes two mandatory controls. First: A source SQL database has a reliable last_modified_utc column and nightly changes should not require full extraction. Second: A 200 GB nightly file arrives in pieces and the Copy activity starts before all parts are uploaded. Which two-part implementation satisfies them together?
Step 1 resolves requirement A: A high-watermark incremental load fetches changes since the last committed boundary. Step 2 resolves requirement B: A file-ready boundary prevents reading partially delivered source data. Both acceptance tests are required: an unchanged second run loads no new rows and a late updated row is captured; and the pipeline starts only after all manifest entries are present and valid.
A high-watermark incremental load fetches changes since the last committed boundary. A file-ready boundary prevents reading partially delivered source data. The proposed steps (Implement an SCD Type 2 dimension with effective dates, expiration and surrogate keys; write immutable or versioned raw source files into bronze before curated transformations) address other capabilities instead of this required pair.
A file-ready boundary prevents reading partially delivered source data. The other proposed action (Implement an SCD Type 2 dimension with effective dates, expiration and surrogate keys) does not implement the first control. A high-watermark incremental load fetches changes since the last committed boundary.
A high-watermark incremental load fetches changes since the last committed boundary. The other proposed action (write immutable or versioned raw source files into bronze before curated transformations) addresses a different operation. A file-ready boundary prevents reading partially delivered source data.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
