You save $34.99
An auditor reviews the applied Fabric control: Configure supported dynamic data masking on sensitive columns and test privilege-based behavior. It was selected to address: A financial warehouse requires dynamically masking account identifiers for lower-privilege SQL readers. Which evidence demonstrates the intended result?
Dynamic data masking changes displayed results for eligible low-privilege readers rather than encrypting stored values.
Promotion is a discoverability signal; certification requires an authorized organizational review process. It does not show that an ordinary reader sees masked identifiers while an authorized privileged account sees the permitted original.
Item audit events do not alone identify each source row or transformation step. It does not show that an ordinary reader sees masked identifiers while an authorized privileged account sees the permitted original.
Endorsement communicates content quality and ownership rather than encryption or data authorization. It does not show that an ordinary reader sees masked identifiers while an authorized privileged account sees the permitted original.
The reviewer will approve this deployment only when it fixes both issues: (a) A mirrored source table is unavailable in Fabric because its source permissions do not allow the required replication metadata access. (b) A T-SQL transformation needs one row per customer using grouped spend totals. Which proposed pair of changes is appropriate?
Step 1 resolves requirement A: Mirroring depends on source-specific permissions and configuration, not only workspace Reader rights. Step 2 resolves requirement B: Relational aggregation collapses transactional detail into grouped measures. Both acceptance tests are required: the table appears in mirrored status and subsequent changes replicate; and customer totals reconcile with a reference sum of source transactions.
Mirroring depends on source-specific permissions and configuration, not only workspace Reader rights. The other proposed action (create an internal OneLake shortcut to the approved source table or folder) addresses a different operation. Relational aggregation collapses transactional detail into grouped measures.
Relational aggregation collapses transactional detail into grouped measures. The other proposed action (Create a supported OneLake shortcut to the external source with valid credentials and permissions) does not implement the first control. Mirroring depends on source-specific permissions and configuration, not only workspace Reader rights.
Mirroring depends on source-specific permissions and configuration, not only workspace Reader rights. Relational aggregation collapses transactional detail into grouped measures. The proposed steps (Create a supported OneLake shortcut to the external source with valid credentials and permissions; create an internal OneLake shortcut to the approved source table or folder) address other capabilities instead of this required pair.
A Fabric data engineering release must address both of these independent requirements: (1) Two unrelated streaming queries mistakenly share one checkpoint path and restart with inconsistent progress. (2) A KQL query must retrieve the latest device status per device from a stream of updates. Which combined plan meets both without substituting an unrelated change?
Step 1 resolves requirement A: Checkpoint directories contain query-specific state and cannot be safely shared between jobs. Step 2 resolves requirement B: Arg_max selects the row with the greatest time value in each group. Both acceptance tests are required: both queries restart with their own correct offsets and no state collisions; and each device returns one latest known status from the controlled input.
Checkpoint directories contain query-specific state and cannot be safely shared between jobs. Arg_max selects the row with the greatest time value in each group. The proposed steps (Use the event's timestamp in window and bin calculations and retain arrival time separately; ingest events into an Eventhouse native table with the required schema and ingestion mapping) address other capabilities instead of this required pair.
Checkpoint directories contain query-specific state and cannot be safely shared between jobs. The other proposed action (ingest events into an Eventhouse native table with the required schema and ingestion mapping) addresses a different operation. Arg_max selects the row with the greatest time value in each group.
Arg_max selects the row with the greatest time value in each group. The other proposed action (Use the event's timestamp in window and bin calculations and retain arrival time separately) does not implement the first control. Checkpoint directories contain query-specific state and cannot be safely shared between jobs.
The reviewer will approve this deployment only when it fixes both issues: (a) A Fabric pipeline must ingest from an on-premises SQL Server accessible only through a corporate gateway. (b) A business asks to denormalize small product attributes into a gold sales table for faster analyst queries. Which proposed pair of changes is appropriate?
Step 1 resolves requirement A: Managed gateway connectivity enables approved on-premises source access for supported connectors. Step 2 resolves requirement B: Denormalization trades duplication for simpler downstream analytic reads. Both acceptance tests are required: the Copy activity reads the authorized source without opening the server publicly; and the gold table includes valid product labels and agrees with dimensional source counts.
Denormalization trades duplication for simpler downstream analytic reads. The other proposed action (Use a documented left join and unknown-dimension handling rather than dropping unmatched records) does not implement the first control. Managed gateway connectivity enables approved on-premises source access for supported connectors.
Managed gateway connectivity enables approved on-premises source access for supported connectors. The other proposed action (create a supported OneLake shortcut to the external source with valid credentials and permissions) addresses a different operation. Denormalization trades duplication for simpler downstream analytic reads.
Managed gateway connectivity enables approved on-premises source access for supported connectors. Denormalization trades duplication for simpler downstream analytic reads. The proposed steps (Use a documented left join and unknown-dimension handling rather than dropping unmatched records; create a supported OneLake shortcut to the external source with valid credentials and permissions) address other capabilities instead of this required pair.
A production analytics workflow has this requirement: A streaming source delivers messages at least once after network retries. What is the most appropriate change if success must be shown by this test: a redelivered event does not increase distinct business-event count?
Transport retry can redeliver messages even when the consumer recovered correctly. Verify that a redelivered event does not increase distinct business-event count.
Bronze history and curated current-state views serve different retention and reporting needs. However, this alone does not show that a redelivered event does not increase distinct business-event count.
Type 1 updates replace the current attribute without retaining prior versions. However, this alone does not show that a redelivered event does not increase distinct business-event count.
Event time supports domain analysis and processing time supports operational freshness diagnosis. However, this alone does not show that a redelivered event does not increase distinct business-event count.
A production analytics workflow has this requirement: A team tunes Spark for read-heavy workloads but its pool was sized using only a small ingestion test. What is the most appropriate change if success must be shown by this test: observed read latency and CU use meet the documented acceptance benchmark?
Compute needs depend on workload characteristics, not only table size or the latest small test. Verify that observed read latency and CU use meet the documented acceptance benchmark.
Outbound access protection blocks destinations by default until a permitted exception is configured. However, this alone does not show that observed read latency and CU use meet the documented acceptance benchmark.
Business domains organize content, while workspaces and OneLake roles govern operational access. However, this alone does not show that observed read latency and CU use meet the documented acceptance benchmark.
Workspace-level configuration governs data access and connectivity across multiple items. However, this alone does not show that observed read latency and CU use meet the documented acceptance benchmark.
After a production change, the runbook records: Commit workspace changes through Fabric Git integration and confirm synchronization state. The previous problem was: A team connected a Fabric workspace to a Git branch but assumes new uncommitted edits are already safely stored in the repository. What test result confirms effective remediation?
A linked branch does not automatically mean every local workspace change has been committed.
Version control alone does not enforce release quality or change authorization. It does not show that the intended item definition appears in the selected commit with no pending uncommitted changes.
Database projects make selected relational schemas deployable and reviewable as source artifacts. It does not show that the intended item definition appears in the selected commit with no pending uncommitted changes.
Automated release operations require explicit identity and API permissions independent of interactive workspace ownership. It does not show that the intended item definition appears in the selected commit with no pending uncommitted changes.
The reviewer will approve this deployment only when it fixes both issues: (a) Business analysts need to clean a small table visually with Power Query and load the result into a supported destination. (b) Engineers need complex PySpark transformations and Delta MERGE logic on a large Lakehouse table. Which proposed pair of changes is appropriate?
Step 1 resolves requirement A: Dataflow Gen2 provides visual ingestion/transformation, reducing the need for custom Spark code. Step 2 resolves requirement B: Spark code supports programmable distributed transforms and Delta upsert patterns. Both acceptance tests are required: the refreshed destination contains the correctly typed and filtered rows; and a parameterized run updates the expected Delta table without full replacement.
Dataflow Gen2 provides visual ingestion/transformation, reducing the need for custom Spark code. Spark code supports programmable distributed transforms and Delta upsert patterns. The proposed steps (Constrain ForEach activity concurrency and configure a controlled retry budget; use a ForEach activity over the manifest and supply the current item to a parameterized child activity) address other capabilities instead of this required pair.
Dataflow Gen2 provides visual ingestion/transformation, reducing the need for custom Spark code. The other proposed action (use a ForEach activity over the manifest and supply the current item to a parameterized child activity) addresses a different operation. Spark code supports programmable distributed transforms and Delta upsert patterns.
Spark code supports programmable distributed transforms and Delta upsert patterns. The other proposed action (Constrain ForEach activity concurrency and configure a controlled retry budget) does not implement the first control. Dataflow Gen2 provides visual ingestion/transformation, reducing the need for custom Spark code.
The reviewer will approve this deployment only when it fixes both issues: (a) A Fabric pipeline must ingest from an on-premises SQL Server accessible only through a corporate gateway. (b) A T-SQL transformation needs one row per customer using grouped spend totals. Which proposed pair of changes is appropriate?
Step 1 resolves requirement A: Managed gateway connectivity enables approved on-premises source access for supported connectors. Step 2 resolves requirement B: Relational aggregation collapses transactional detail into grouped measures. Both acceptance tests are required: the Copy activity reads the authorized source without opening the server publicly; and customer totals reconcile with a reference sum of source transactions.
Relational aggregation collapses transactional detail into grouped measures. The other proposed action (Create a supported OneLake shortcut to the external source with valid credentials and permissions) does not implement the first control. Managed gateway connectivity enables approved on-premises source access for supported connectors.
Managed gateway connectivity enables approved on-premises source access for supported connectors. Relational aggregation collapses transactional detail into grouped measures. The proposed steps (Create a supported OneLake shortcut to the external source with valid credentials and permissions; change authoritative data at the source and query the mirrored replica for analytics) address other capabilities instead of this required pair.
Managed gateway connectivity enables approved on-premises source access for supported connectors. The other proposed action (change authoritative data at the source and query the mirrored replica for analytics) addresses a different operation. Relational aggregation collapses transactional detail into grouped measures.
The project has two blockers. Blocker A: A producer sends nested events that require field extraction before analytics users can query key dimensions. Blocker B: An Eventhouse shortcut includes six tables but only one table is needed for KQL and the engineer assumes one shortcut can target all of them. What pair of actions resolves both blockers?
Step 1 resolves requirement A: Schema mapping makes raw event properties accessible as KQL columns. Step 2 resolves requirement B: KQL OneLake shortcuts target one table or subfolder per shortcut, so broad collection mapping needs separate entries. Both acceptance tests are required: an event with nested attributes produces queryable correctly typed keys; and the intended table is queryable and unrelated source tables are not inadvertently exposed.
Schema mapping makes raw event properties accessible as KQL columns. KQL OneLake shortcuts target one table or subfolder per shortcut, so broad collection mapping needs separate entries. The proposed steps (Test the changed query as a new deployment with a new checkpoint and explicit starting-offset/replay plan; parse with an explicit schema and route malformed rows to a quarantine output) address other capabilities instead of this required pair.
KQL OneLake shortcuts target one table or subfolder per shortcut, so broad collection mapping needs separate entries. The other proposed action (Test the changed query as a new deployment with a new checkpoint and explicit starting-offset/replay plan) does not implement the first control. Schema mapping makes raw event properties accessible as KQL columns.
Schema mapping makes raw event properties accessible as KQL columns. The other proposed action (parse with an explicit schema and route malformed rows to a quarantine output) addresses a different operation. KQL OneLake shortcuts target one table or subfolder per shortcut, so broad collection mapping needs separate entries.
The Fabric engineering team must address this requirement: A warehouse query repeatedly filters and joins on columns with poor estimates despite a correct table schema. Which implementation meets the requirement and provides this acceptance evidence: the plan's row estimates and elapsed time improve after appropriate statistics maintenance?
Column statistics support cost-based query planning without forcing a specific data distribution. Verify that the plan's row estimates and elapsed time improve after appropriate statistics maintenance.
Materialized views maintain precomputed summaries to accelerate repeated analytic queries. However, this alone does not show that the plan's row estimates and elapsed time improve after appropriate statistics maintenance.
V-Order organizes Parquet layout to favor supported Fabric analytic readers. However, this alone does not show that the plan's row estimates and elapsed time improve after appropriate statistics maintenance.
Early source-side filtering reduces data that the dataflow engine must move and transform. However, this alone does not show that the plan's row estimates and elapsed time improve after appropriate statistics maintenance.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
