You save $34.99
An enterprise Fabric solution must resolve this issue: A data engineer wants to reclaim obsolete Delta files immediately after a write, ignoring active readers and time travel. The acceptance criterion is: storage cleanup retains files needed by approved concurrent readers and historical queries. Which implementation should be selected?
VACUUM removes files no longer needed beyond the retention threshold; aggressive cleanup can break readers or history. Verify that storage cleanup retains files needed by approved concurrent readers and historical queries.
Early source-side filtering reduces data that the dataflow engine must move and transform. However, this alone does not show that storage cleanup retains files needed by approved concurrent readers and historical queries.
Column statistics support cost-based query planning without forcing a specific data distribution. However, this alone does not show that storage cleanup retains files needed by approved concurrent readers and historical queries.
Optimized staged-to-Lakehouse copy can avoid extra serialization and transfer overhead. However, this alone does not show that storage cleanup retains files needed by approved concurrent readers and historical queries.
A Fabric data engineer receives a change request: Analysts in the same workspace should access one dataset but not another unrelated sensitive dataset. Which action best produces this measurable result: an analyst opens the assigned item and receives a denial for the unrelated artifact?
Item permissions target a specific Fabric object while workspace roles cover more workspace resources. Verify that an analyst opens the assigned item and receives a denial for the unrelated artifact.
Endorsement communicates content quality and ownership rather than encryption or data authorization. However, this alone does not show that an analyst opens the assigned item and receives a denial for the unrelated artifact.
Classification, trust signaling and audit history solve distinct governance requirements. However, this alone does not show that an analyst opens the assigned item and receives a denial for the unrelated artifact.
Sensitivity labels mark data classification and inform downstream governance; they do not automatically grant read access. However, this alone does not show that an analyst opens the assigned item and receives a denial for the unrelated artifact.
The reviewer will approve this deployment only when it fixes both issues: (a) A platform administrator assumes assigning a workspace to a Fabric domain will automatically give every finance employee data access. (b) An approved OneLake cross-workspace connection stopped working immediately after outbound access protection was enabled. Which proposed pair of changes is appropriate?
Step 1 resolves requirement A: Domain assignment supports discoverability and governance but is not the row or item authorization boundary. Step 2 resolves requirement B: Outbound access protection blocks destinations by default until a permitted exception is configured. Both acceptance tests are required: an unassigned employee cannot read restricted content merely because the workspace has a Finance domain; and the specific approved connection succeeds while unrelated external targets remain blocked.
Domain assignment supports discoverability and governance but is not the row or item authorization boundary. Outbound access protection blocks destinations by default until a permitted exception is configured. The proposed steps (Configure the supported Apache Airflow job or workspace settings and validate the managed orchestration environment; disable item-level compute customization in the workspace Spark settings) address other capabilities instead of this required pair.
Domain assignment supports discoverability and governance but is not the row or item authorization boundary. The other proposed action (disable item-level compute customization in the workspace Spark settings) addresses a different operation. Outbound access protection blocks destinations by default until a permitted exception is configured.
Outbound access protection blocks destinations by default until a permitted exception is configured. The other proposed action (Configure the supported Apache Airflow job or workspace settings and validate the managed orchestration environment) does not implement the first control. Domain assignment supports discoverability and governance but is not the row or item authorization boundary.
The reviewer will approve this deployment only when it fixes both issues: (a) A Spark job fails when a Python library is installed interactively but absent in the scheduled environment. (b) A T-SQL MERGE job fails due to multiple source rows matching one target business key. Which proposed pair of changes is appropriate?
Step 1 resolves requirement A: Scheduled Spark jobs use their declared environment rather than an old notebook session's temporary libraries. Step 2 resolves requirement B: Conflicting source matches prevent unambiguous one-target-row updates. Both acceptance tests are required: the next scheduled run imports the dependency successfully; and the merge updates each target key once and produces the expected latest value.
Scheduled Spark jobs use their declared environment rather than an old notebook session's temporary libraries. The other proposed action (repair destination column mapping and data types, publish and rerun the dataflow) addresses a different operation. Conflicting source matches prevent unambiguous one-target-row updates.
Conflicting source matches prevent unambiguous one-target-row updates. The other proposed action (Introduce idempotent destination writes or a merge keyed by source batch/business ID) does not implement the first control. Scheduled Spark jobs use their declared environment rather than an old notebook session's temporary libraries.
Scheduled Spark jobs use their declared environment rather than an old notebook session's temporary libraries. Conflicting source matches prevent unambiguous one-target-row updates. The proposed steps (Introduce idempotent destination writes or a merge keyed by source batch/business ID; repair destination column mapping and data types, publish and rerun the dataflow) address other capabilities instead of this required pair.
The data platform team needs a narrowly scoped fix: A pipeline Notebook activity succeeds manually but fails from a schedule because one required base parameter is absent. Which approach satisfies the documented test that scheduled runs receive the expected parameter values and complete?
Parameterized execution cannot rely on interactive session variables. Verify that scheduled runs receive the expected parameter values and complete.
Shortcuts continue to depend on the external storage connection and current rights. However, this alone does not show that scheduled runs receive the expected parameter values and complete.
Checkpoint recovery and exactly-once behavior depend on sink capabilities and stable query state. However, this alone does not show that scheduled runs receive the expected parameter values and complete.
System-created staging permissions can be tied to an original owner and may outlive a user's access. However, this alone does not show that scheduled runs receive the expected parameter values and complete.
A Microsoft Fabric project must complete both tasks before signoff. Task 1: A new Fabric item type is not supported by the currently configured Git integration, yet an engineer assumes all workspace items are versioned. Task 2: A CI/CD system must promote item definitions to a destination Fabric workspace with no interactive user access. Choose exactly TWO controls that collectively meet the requirements.
Fabric Git integration support is item-specific; workspace membership alone is insufficient. Confirm that every release artifact has a documented supported source-of-truth path.
Automated release operations require explicit identity and API permissions independent of interactive workspace ownership. Confirm that a pipeline release updates only the intended workspace and produces an auditable run record.
Database project source control can make targeted DDL changes auditable.
Source-controlled definitions should not embed reusable production secrets.
A Fabric data engineering release must address both of these independent requirements: (1) A warehouse must support atomic replacement of a daily reporting partition rather than exposing a half-loaded table. (2) A large dimensional load joins source sales to a dimension that has no corresponding customer key. Which combined plan meets both without substituting an unrelated change?
Step 1 resolves requirement A: Staging prevents consumers from seeing incomplete reports during data movement. Step 2 resolves requirement B: Unknown dimension handling preserves fact integrity without fabricating dimension matches. Both acceptance tests are required: queries see either the prior complete partition or the validated replacement; and facts with missing keys follow the documented fallback and are counted in QA.
Unknown dimension handling preserves fact integrity without fabricating dimension matches. The other proposed action (Use a persisted high-watermark filter and update the watermark only after successful downstream commit) does not implement the first control. Staging prevents consumers from seeing incomplete reports during data movement.
Staging prevents consumers from seeing incomplete reports during data movement. Unknown dimension handling preserves fact integrity without fabricating dimension matches. The proposed steps (Use a persisted high-watermark filter and update the watermark only after successful downstream commit; use a controlled initial full load followed by an incremental ingestion strategy with source checkpoints) address other capabilities instead of this required pair.
Staging prevents consumers from seeing incomplete reports during data movement. The other proposed action (use a controlled initial full load followed by an incremental ingestion strategy with source checkpoints) addresses a different operation. Unknown dimension handling preserves fact integrity without fabricating dimension matches.
An auditor reviews the applied Fabric control: Apply labels/endorsement for classification and trust, and separately collect supported audit activity. It was selected to address: A confidential data pipeline needs item endorsements and sensitivity labels, but the team assumes either setting is equivalent to an audit trail. Which evidence demonstrates the intended result?
Classification, trust signaling and audit history solve distinct governance requirements.
Union-like access from multiple roles can explain visibility that a single restricted role does not predict. It does not show that the item displays its metadata and an activity query identifies who changed it.
Database object-level permissions and views can provide a controlled SQL projection. It does not show that the item displays its metadata and an activity query identifies who changed it.
Item audit events do not alone identify each source row or transformation step. It does not show that the item displays its metadata and an activity query identifies who changed it.
A team is working on two related Fabric work items. Work item A: An analyst is a member of both a broad OneLake data role and a restricted role and unexpectedly sees extra tables. Work item B: A data security incident requires both Fabric item activity history and source-data lineage from a pipeline. Select TWO specific implementation steps.
Item audit events do not alone identify each source row or transformation step. Confirm that an investigation links the responsible identity and job to the source and destination artifacts.
Multiple OneLake grant roles combine granted access; a restrictive grant does not revoke access granted elsewhere. Confirm that the analyst's effective permissions exclude private tables after the excess grant is removed.
Endorsement communicates content quality and ownership rather than encryption or data authorization.
Sensitivity labels mark data classification and inform downstream governance; they do not automatically grant read access.
A production analytics workflow has this requirement: A workspace's data engineers must control the default Apache Airflow integration behavior without editing each existing DAG. What is the most appropriate change if success must be shown by this test: a scheduled DAG runs using the approved workspace integration settings?
Airflow configuration belongs to the workspace/orchestration setup rather than individual Spark SQL statements. Verify that a scheduled DAG runs using the approved workspace integration settings.
Capacity exhaustion differs from transient faults and requires resource or concurrency management. However, this alone does not show that a scheduled DAG runs using the approved workspace integration settings.
Outbound access protection blocks destinations by default until a permitted exception is configured. However, this alone does not show that a scheduled DAG runs using the approved workspace integration settings.
Version-controlled runtime and dependency changes prevent surprise job differences. However, this alone does not show that a scheduled DAG runs using the approved workspace integration settings.
The data platform team needs a narrowly scoped fix: IoT sensor messages should be routed from a live event source to a Fabric Eventhouse without scheduled file exports. Which approach satisfies the documented test that a published sample event appears in the chosen Eventhouse table within the freshness objective?
Eventstream routes real-time events to supported sinks for KQL analytics. Verify that a published sample event appears in the chosen Eventhouse table within the freshness objective.
Make-series generates regular time bins, including configured defaults for empty periods. However, this alone does not show that a published sample event appears in the chosen Eventhouse table within the freshness objective.
Materialized aggregations can precompute repeated summaries to reduce query cost. However, this alone does not show that a published sample event appears in the chosen Eventhouse table within the freshness objective.
Checkpoint compatibility depends on sources, grouping keys, operators and state schema. However, this alone does not show that a published sample event appears in the chosen Eventhouse table within the freshness objective.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
