You save $34.99
An auditor reviews the applied Fabric control: Fix the supported ingestion mapping or source timestamp format and test typed conversion. It was selected to address: An Eventhouse KQL ingestion mapping rejects payloads whose timestamp arrives as an unparseable text field. Which evidence demonstrates the intended result?
KQL ingestion requires compatible column types and valid mapping expressions.
A missing or renamed column breaks Spark analysis before valid execution. It does not show that a test event lands with a correct datetime column and no mapping error.
Unbalanced shuffle partitions can exhaust one executor while others remain underutilized. It does not show that a test event lands with a correct datetime column and no mapping error.
Shortcut path references are not automatically rewritten when source folders are relocated. It does not show that a test event lands with a correct datetime column and no mapping error.
An auditor reviews the applied Fabric control: Configure supported workspace outbound access protection and allow only approved destinations. It was selected to address: A team needs to control which external destinations OneLake-enabled workspace items can connect to for sensitive datasets. Which evidence demonstrates the intended result?
Outbound protection restricts data egress paths independently of ordinary item-level read permissions.
Compute needs depend on workload characteristics, not only table size or the latest small test. It does not show that an approved endpoint remains reachable and an unapproved outbound connection is blocked.
Domain metadata and endorsement communicate ownership and trust, not write grants. It does not show that an approved endpoint remains reachable and an unapproved outbound connection is blocked.
Airflow configuration belongs to the workspace/orchestration setup rather than individual Spark SQL statements. It does not show that an approved endpoint remains reachable and an unapproved outbound connection is blocked.
A Fabric data engineering release must address both of these independent requirements: (1) An operations team needs relational T-SQL transformations and governed SQL reporting tables with ACID transactions. (2) An external ADLS Gen2 folder must be exposed in a Lakehouse without copying the entire source into Fabric. Which combined plan meets both without substituting an unrelated change?
Step 1 resolves requirement A: Warehouse is optimized for supported SQL data engineering and analytics operations. Step 2 resolves requirement B: Shortcuts present source data under OneLake paths without physically duplicating the source files. Both acceptance tests are required: T-SQL loads and analytic queries run against the intended warehouse tables; and a new external file appears through the shortcut with authorized access.
Shortcuts present source data under OneLake paths without physically duplicating the source files. The other proposed action (Use PySpark groupBy with suitable aggregate expressions on the distributed DataFrame) does not implement the first control. Warehouse is optimized for supported SQL data engineering and analytics operations.
Warehouse is optimized for supported SQL data engineering and analytics operations. The other proposed action (use a supported transformation tool to expand nested records and map types before loading the Warehouse) addresses a different operation. Shortcuts present source data under OneLake paths without physically duplicating the source files.
Warehouse is optimized for supported SQL data engineering and analytics operations. Shortcuts present source data under OneLake paths without physically duplicating the source files. The proposed steps (Use PySpark groupBy with suitable aggregate expressions on the distributed DataFrame; use a supported transformation tool to expand nested records and map types before loading the Warehouse) address other capabilities instead of this required pair.
The project has two blockers. Blocker A: A database project contains a table definition change that would unintentionally drop production data. Blocker B: A CI/CD system must promote item definitions to a destination Fabric workspace with no interactive user access. What pair of actions resolves both blockers?
Step 1 resolves requirement A: Database schema deployment can have destructive consequences even when a source diff is syntactically valid. Step 2 resolves requirement B: Automated release operations require explicit identity and API permissions independent of interactive workspace ownership. Both acceptance tests are required: the deployment test preserves existing production rows and rejects unapproved drops; and 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. Automated release operations require explicit identity and API permissions independent of interactive workspace ownership. The proposed steps (Sync the approved Git state into the appropriate workspace and promote the tested definitions; connect the supported workspace to a Git repository/branch and commit supported item definitions) address other capabilities instead of this required pair.
Database schema deployment can have destructive consequences even when a source diff is syntactically valid. The other proposed action (connect the supported workspace to a Git repository/branch and commit supported item definitions) addresses a different operation. Automated release operations require explicit identity and API permissions independent of interactive workspace ownership.
Automated release operations require explicit identity and API permissions independent of interactive workspace ownership. The other proposed action (Sync the approved Git state into the appropriate workspace and promote the tested definitions) does not implement the first control. Database schema deployment can have destructive consequences even when a source diff is syntactically valid.
A Fabric release must resolve two independent technical requirements. Requirement A: An Eventhouse suddenly contains no new records because its ingestion source connection expired. Requirement B: A shortcut target was moved to another storage path and data appears missing in a Lakehouse. Select TWO actions that directly satisfy both requirements.
Expired source access interrupts ingestion even if the KQL query syntax is valid. Confirm that a new source event appears after the connection is restored.
Shortcut path references are not automatically rewritten when source folders are relocated. Confirm that a sample file is visible from the corrected shortcut path.
Parameterized execution cannot rely on interactive session variables.
Retries and reruns can reexecute completed work, so append-only sinks need duplicate protection.
After a production change, the runbook records: Use supported Eventstream transformation operations before the selected destination. The previous problem was: A team needs to filter malformed sensor events and transform fields before sending data to Eventhouse. What test result confirms effective remediation?
Stream transformations can filter or project event fields before ingestion.
Custom microbatch side effects can rerun; checkpoint alone does not make arbitrary writes exactly once. It does not show that the target receives valid transformed events and rejected records are accounted for.
Overly long watermark delays retain unnecessary window or join state. It does not show that the target receives valid transformed events and rejected records are accounted for.
A stream can distribute selected events to more than one supported consumer. It does not show that the target receives valid transformed events and rejected records are accounted for.
A Fabric engineer has implemented the following change: Export or query supported historical run telemetry and aggregate status and duration by week. The original requirement was: An engineer must report weekly median pipeline runtime and failure rate, not only the latest run. Which observation best validates that the change works?
Historical monitoring supports reliability trends beyond a single run inspection.
Notebook failures can originate in the Spark job rather than pipeline orchestration. It does not show that the weekly report reconciles sampled run IDs with counted successes and failures.
Queue wait time and execution time require different capacity and performance actions. It does not show that the weekly report reconciles sampled run IDs with counted successes and failures.
Event-to-query latency differs from service-only ingest processing time. It does not show that the weekly report reconciles sampled run IDs with counted successes and failures.
An enterprise Fabric solution must resolve this issue: An approved OneLake cross-workspace connection stopped working immediately after outbound access protection was enabled. The acceptance criterion is: the specific approved connection succeeds while unrelated external targets remain blocked. Which implementation should be selected?
Outbound access protection blocks destinations by default until a permitted exception is configured. Verify that the specific approved connection succeeds while unrelated external targets remain blocked.
Domains group analytics content by business ownership rather than granting fine-grained data permissions. However, this alone does not show that the specific approved connection succeeds while unrelated external targets remain blocked.
Domain metadata and endorsement communicate ownership and trust, not write grants. However, this alone does not show that the specific approved connection succeeds while unrelated external targets remain blocked.
Version-controlled runtime and dependency changes prevent surprise job differences. However, this alone does not show that the specific approved connection succeeds while unrelated external targets remain blocked.
The Fabric engineering team must address this requirement: A Spark notebook fails with an executor OOM after a skewed join on a hot customer ID. Which implementation meets the requirement and provides this acceptance evidence: the hot-key test completes without executor OOM and preserves join results?
Unbalanced shuffle partitions can exhaust one executor while others remain underutilized. Verify that the hot-key test completes without executor OOM and preserves join results.
Type overflow creates a deterministic mapping failure, not a transient network fault. However, this alone does not show that the hot-key test completes without executor OOM and preserves join results.
A single dataflow query supports a constrained destination configuration; invalid multiples fail validation. However, this alone does not show that the hot-key test completes without executor OOM and preserves join results.
An authentication failure must be fixed at the connection boundary, not by changing data mapping. However, this alone does not show that the hot-key test completes without executor OOM and preserves join results.
A Fabric engineer has implemented the following change: Keep versioned bronze changes and select the latest approved version per key in the curated load. The original requirement was: A marketing dataset contains daily revisions but only the most recently approved version should feed a gold table. Which observation best validates that the change works?
Bronze history and curated current-state views serve different retention and reporting needs.
A file-ready boundary prevents reading partially delivered source data. It does not show that gold includes only approved current revisions and older versions remain auditable.
Bronze ingestion preserves source evidence separately from silver/gold business interpretations. It does not show that gold includes only approved current revisions and older versions remain auditable.
Snapshot processing can provide an auditable consistent cutoff rather than a partial stream. It does not show that gold includes only approved current revisions and older versions remain auditable.
A shared Fabric backlog includes two mandatory controls. First: A warehouse dashboard refreshes slowly and users blame source ingestion without checking actual SQL workload. Second: Daily notebook outputs should generate an alert when row counts drop outside an accepted band. Which two-part implementation satisfies them together?
Step 1 resolves requirement A: Query history exposes SQL execution trends distinct from copy/load duration. Step 2 resolves requirement B: Data quality anomalies may not appear as compute failures unless explicitly measured. Both acceptance tests are required: the slow query shape and its historical duration are identified; and a deliberately truncated batch triggers an anomaly alert while the prior good batch does not.
Data quality anomalies may not appear as compute failures unless explicitly measured. The other proposed action (Check the semantic model refresh history and dependencies after the upstream load) does not implement the first control. Query history exposes SQL execution trends distinct from copy/load duration.
Query history exposes SQL execution trends distinct from copy/load duration. Data quality anomalies may not appear as compute failures unless explicitly measured. The proposed steps (Check the semantic model refresh history and dependencies after the upstream load; compare multiple refresh-history durations and per-query execution behavior) address other capabilities instead of this required pair.
Query history exposes SQL execution trends distinct from copy/load duration. The other proposed action (compare multiple refresh-history durations and per-query execution behavior) addresses a different operation. Data quality anomalies may not appear as compute failures unless explicitly measured.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
