You save $34.99
An auditor reviews the applied Fabric control: Update the supported shortcut connection authentication and test access to the source path. It was selected to address: A Lakehouse shortcut suddenly fails after a cloud storage credential was rotated. Which evidence demonstrates the intended result?
Shortcuts depend on the current external source connection and permissions.
Managed gateway connectivity enables approved on-premises source access for supported connectors. It does not show that file listing works through the shortcut after credentials are corrected.
A Lakehouse combines file storage with Delta tables and Spark development. It does not show that file listing works through the shortcut after credentials are corrected.
Distributed Spark processing supports large programmable transforms beyond simple portal mapping. It does not show that file listing works through the shortcut after credentials are corrected.
A shared Fabric backlog includes two mandatory controls. First: A user sees a table through a notebook but an unauthorized third-party reader should not bypass its OneLake row filters. Second: A confidential data pipeline needs item endorsements and sensitivity labels, but the team assumes either setting is equivalent to an audit trail. Which two-part implementation satisfies them together?
Step 1 resolves requirement A: OneLake can block unsupported engines when a table requires enforcement of granular row or column restrictions. Step 2 resolves requirement B: Classification, trust signaling and audit history solve distinct governance requirements. Both acceptance tests are required: the supported engine returns filtered rows and an unsupported path cannot bypass them; and the item displays its metadata and an activity query identifies who changed it.
Classification, trust signaling and audit history solve distinct governance requirements. The other proposed action (Use the applicable Microsoft Fabric/Microsoft Purview audit log search with principal, time and operation filters) does not implement the first control. OneLake can block unsupported engines when a table requires enforcement of granular row or column restrictions.
OneLake can block unsupported engines when a table requires enforcement of granular row or column restrictions. The other proposed action (correlate audit events with pipeline run identifiers and supported lineage records) addresses a different operation. Classification, trust signaling and audit history solve distinct governance requirements.
OneLake can block unsupported engines when a table requires enforcement of granular row or column restrictions. Classification, trust signaling and audit history solve distinct governance requirements. The proposed steps (Use the applicable Microsoft Fabric/Microsoft Purview audit log search with principal, time and operation filters; correlate audit events with pipeline run identifiers and supported lineage records) address other capabilities instead of this required pair.
A shared Fabric backlog includes two mandatory controls. First: A notebook needs a different date range on every scheduled invocation without source-code edits. Second: A nightly pipeline must not send a completion notice if the data quality notebook fails. Which two-part implementation satisfies them together?
Step 1 resolves requirement A: Parameterized notebook execution separates business run context from transformation logic. Step 2 resolves requirement B: Dependency outcomes prevent false operational success claims. Both acceptance tests are required: two scheduled runs process distinct requested windows without code changes; and the success notice appears only after validation and the failure notice carries the error when validation fails.
Parameterized notebook execution separates business run context from transformation logic. The other proposed action (enable required staging and configure the supported Warehouse data destination) addresses a different operation. Dependency outcomes prevent false operational success claims.
Dependency outcomes prevent false operational success claims. The other proposed action (Use a Dataflow Gen2 with Power Query transformations and a configured data destination) does not implement the first control. Parameterized notebook execution separates business run context from transformation logic.
Parameterized notebook execution separates business run context from transformation logic. Dependency outcomes prevent false operational success claims. The proposed steps (Use a Dataflow Gen2 with Power Query transformations and a configured data destination; enable required staging and configure the supported Warehouse data destination) address other capabilities instead of this required pair.
After a production change, the runbook records: Disable item-level compute customization in the workspace Spark settings. The previous problem was: A production workspace must disallow notebook authors from freely overriding pool sizes because cost controls depend on approved defaults. What test result confirms effective remediation?
Workspace governance can enforce shared Spark compute settings instead of permitting arbitrary environment overrides.
Workspace-level configuration governs data access and connectivity across multiple items. It does not show that a contributor cannot change the blocked environment compute configuration.
Airflow tasks rely on configured connections and runtime settings independent of a Fabric pipeline definition. It does not show that a contributor cannot change the blocked environment compute configuration.
Airflow configuration belongs to the workspace/orchestration setup rather than individual Spark SQL statements. It does not show that a contributor cannot change the blocked environment compute configuration.
A data engineer must validate the completed action: Choose latest event by version/time with deterministic tie-breaking before target MERGE. It targets this failure: A customer database emits multiple events for one key during the same extraction window. Which test outcome should be accepted?
Deterministic deduplication avoids nondeterministic outcomes when keys repeat.
Namespace and batch isolation prevent filename collisions across producers. It does not show that repeated runs choose the same latest state for the same customer key.
Type 2 slowly changing dimensions preserve prior attribute versions rather than overwriting history. It does not show that repeated runs choose the same latest state for the same customer key.
Transport retry can redeliver messages even when the consumer recovered correctly. It does not show that repeated runs choose the same latest state for the same customer key.
A Fabric data engineer receives a change request: A retailer needs a fact table with order-line grain and product/customer dimension keys for analysis. Which action best produces this measurable result: two items on one order produce two fact rows with valid dimensional references?
Dimensional modeling separates measurable events from descriptive attributes at a declared grain. Verify that two items on one order produce two fact rows with valid dimensional references.
Schema-aware mapping prevents silent column misplacement after a source reorder. However, this alone does not show that two items on one order produce two fact rows with valid dimensional references.
CDC retains insert/update/delete semantics that append-only loading may lose. However, this alone does not show that two items on one order produce two fact rows with valid dimensional references.
Snapshot processing can provide an auditable consistent cutoff rather than a partial stream. However, this alone does not show that two items on one order produce two fact rows with valid dimensional references.
The project has two blockers. Blocker A: A team's short interactive Spark notebooks take too long to start because they use a custom pool designed for long batch jobs. Blocker B: A workspace's data engineers must control the default Apache Airflow integration behavior without editing each existing DAG. What pair of actions resolves both blockers?
Step 1 resolves requirement A: Starter pools can reduce Spark session startup cost compared with capacity-level custom pools. Step 2 resolves requirement B: Airflow configuration belongs to the workspace/orchestration setup rather than individual Spark SQL statements. Both acceptance tests are required: a small interactive notebook starts within the agreed latency threshold; and a scheduled DAG runs using the approved workspace integration settings.
Airflow configuration belongs to the workspace/orchestration setup rather than individual Spark SQL statements. The other proposed action (Review and configure relevant workspace OneLake settings and data security controls rather than notebook code alone) does not implement the first control. Starter pools can reduce Spark session startup cost compared with capacity-level custom pools.
Starter pools can reduce Spark session startup cost compared with capacity-level custom pools. Airflow configuration belongs to the workspace/orchestration setup rather than individual Spark SQL statements. The proposed steps (Review and configure relevant workspace OneLake settings and data security controls rather than notebook code alone; use domain discovery and item endorsement while retaining scoped workspace/item permissions) address other capabilities instead of this required pair.
Starter pools can reduce Spark session startup cost compared with capacity-level custom pools. The other proposed action (use domain discovery and item endorsement while retaining scoped workspace/item permissions) addresses a different operation. Airflow configuration belongs to the workspace/orchestration setup rather than individual Spark SQL statements.
An auditor reviews the applied Fabric control: Use supported Git branching and pull request review before merging item-definition changes. It was selected to address: Two engineers overwrite each other's notebook edits because they share a single feature branch. Which evidence demonstrates the intended result?
Branch-based review resolves competing definition edits before a shared release branch is updated.
Promotion of definitions does not imply every environment-specific connection is automatically safe. It does not show that both feature changes are merged with a reviewed history rather than lost updates.
Reverting item definitions is a separate action from restoring underlying data that may have changed. It does not show that both feature changes are merged with a reviewed history rather than lost updates.
Source-controlled definitions should not embed reusable production secrets. It does not show that both feature changes are merged with a reviewed history rather than lost updates.
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 warehouse T-SQL query fails because the developer uses a function unsupported in the Fabric Warehouse engine. 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: SQL dialect support differs by Fabric engine and operation. Both acceptance tests are required: scheduled runs receive the expected parameter values and complete; and the revised statement runs in the target Warehouse and passes result tests.
Parameterized execution cannot rely on interactive session variables. SQL dialect support differs by Fabric engine and operation. The proposed steps (Deploy the incompatible stateful query with an explicit new checkpoint and replay plan; review source and destination OneLake data grants and effective security roles) address other capabilities instead of this required pair.
Parameterized execution cannot rely on interactive session variables. The other proposed action (review source and destination OneLake data grants and effective security roles) addresses a different operation. SQL dialect support differs by Fabric engine and operation.
SQL dialect support differs by Fabric engine and operation. The other proposed action (Deploy the incompatible stateful query with an explicit new checkpoint and replay plan) does not implement the first control. Parameterized execution cannot rely on interactive session variables.
A Fabric data engineering release must address both of these independent requirements: (1) An Eventhouse ingestion pipeline has rising latency but no application exception. (2) The finance team needs proof that a Spark notebook ran against its approved production environment and runtime. Which combined plan meets both without substituting an unrelated change?
Step 1 resolves requirement A: Freshness degradation can occur before a hard ingestion failure. Step 2 resolves requirement B: Run provenance identifies the environment that produced a dataset. Both acceptance tests are required: an alert triggers when measured ingestion delay exceeds the agreed objective; and an audit record links a published table to the notebook run and runtime configuration.
Freshness degradation can occur before a hard ingestion failure. Run provenance identifies the environment that produced a dataset. The proposed steps (Compare multiple refresh-history durations and per-query execution behavior; compute and publish validation metrics and attach an alert to a threshold breach) address other capabilities instead of this required pair.
Run provenance identifies the environment that produced a dataset. The other proposed action (Compare multiple refresh-history durations and per-query execution behavior) 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 (compute and publish validation metrics and attach an alert to a threshold breach) addresses a different operation. Run provenance identifies the environment that produced a dataset.
A Microsoft Fabric project must complete both tasks before signoff. Task 1: A telemetry producer publishes data to an Eventstream but a consumer reads no events because its destination is disconnected. Task 2: KQL queries over a frequently reused Delta shortcut are too slow, but the source should remain in OneLake. Choose exactly TWO controls that collectively meet the requirements.
The stream must have an active compatible destination for events to be materialized there. Confirm that a test message travels from source through the configured path to the sink.
Query acceleration caches relevant shortcut data for faster queries while retaining source storage. Confirm that the benchmark shows improved query latency with source freshness inside the approved window.
Checkpoint compatibility depends on sources, grouping keys, operators and state schema.
A too-short watermark can exclude valid late events; a longer delay retains more state.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
