You save $69.98
DP-600 Premium Bundle
- Premium File 250 Questions & Answers
- Last Update: Nov 9, 2026
- Training Course 69 Lectures
- Study Guide 506 Pages
You save $69.98
A Fabric lakehouse contains billions of curated Delta rows, and BI users want fast analysis without full Import refreshes. The team plans to implement this change: Choose Direct Lake storage mode over supported OneLake Delta tables when capacity and security fit. Which result best verifies the intended outcome?
Direct Lake loads required Delta-backed columns into VertiPaq as queries demand rather than making a full Import replica. This evidence exercises the actual success condition rather than only confirming that a resource exists.
That observation would verify a different goal: The combined model responds correctly to filters spanning the imported lookup and Direct Lake fact. It does not demonstrate the specific required result: Visuals return the expected aggregates while performance traces show the intended Direct Lake path.
That observation would verify a different goal: A restricted test user cannot read protected rows through the Direct Lake on OneLake model. It does not demonstrate the specific required result: Visuals return the expected aggregates while performance traces show the intended Direct Lake path.
That observation would verify a different goal: After materialization the affected query uses Direct Lake instead of the slower fallback. It does not demonstrate the specific required result: Visuals return the expected aggregates while performance traces show the intended Direct Lake path.
A Direct Lake model uses a SQL endpoint view and suddenly shifts to slow backend queries. Which implementation decision best addresses the stated requirement?
Direct Lake on SQL falls back to DirectQuery for certain unsupported sources such as unmaterialized SQL views. The proposed action directly targets the problem described in the scenario.
Investigate Direct Lake fallback diagnostics and compact Delta files with supported maintenance where useful. is an approach for a different requirement: File and row-group guardrails and memory can affect whether Direct Lake queries stay in memory mode. In the present case, direct Lake on SQL falls back to DirectQuery for certain unsupported sources such as unmaterialized SQL views.
Treat Direct Lake refresh as metadata framing, not a full Import-mode data copy. is an approach for a different requirement: Framing updates the model's referenced Delta table version and files rather than duplicating the full source. In the present case, direct Lake on SQL falls back to DirectQuery for certain unsupported sources such as unmaterialized SQL views.
Inspect query folding and move a compatible RangeStart/RangeEnd filter toward the source. is an approach for a different requirement: Query folding can push incremental partition filtering to the data source and reduce transferred data. In the present case, direct Lake on SQL falls back to DirectQuery for certain unsupported sources such as unmaterialized SQL views.
An executive report currently displays an exception or infinity for zero-denominator growth rates. The team plans to implement this change: Use DIVIDE with an appropriate alternate result instead of raw division. Which result best verifies the intended outcome?
DIVIDE handles zero and blank denominators consistently in DAX measures. This evidence exercises the actual success condition rather than only confirming that a resource exists.
That observation would verify a different goal: The scorecard shows the selected category for one choice and the fallback for multiple. It does not demonstrate the specific required result: The report returns the configured fallback for zero history and a correct percent otherwise.
That observation would verify a different goal: Only active history versions contribute to the resulting customer count. It does not demonstrate the specific required result: The report returns the configured fallback for zero history and a correct percent otherwise.
That observation would verify a different goal: The refactored measure returns identical KPI values with fewer repeated expensive operations. It does not demonstrate the specific required result: The report returns the configured fallback for zero history and a correct percent otherwise.
A sales manager needs to know which customer keys are currently filtered by slicers before applying special KPI logic. The team plans to implement this change: Use an information/filter-context function such as HASONEVALUE or ISFILTERED where suitable. Which result best verifies the intended outcome?
Context-inspection functions detect the state of user or visual filters for conditional calculations. This evidence exercises the actual success condition rather than only confirming that a resource exists.
That observation would verify a different goal: One customer with three transactions contributes one to the person count. It does not demonstrate the specific required result: Single-customer and multi-customer slicer selections follow the intended branches.
That observation would verify a different goal: Only active history versions contribute to the resulting customer count. It does not demonstrate the specific required result: Single-customer and multi-customer slicer selections follow the intended branches.
That observation would verify a different goal: The highest revenue product receives rank one under the selected period. It does not demonstrate the specific required result: Single-customer and multi-customer slicer selections follow the intended branches.
A measure produces the wrong result because it assumes only one selected customer when many are in context. The team plans to implement this change: Use an information/filter-context function such as HASONEVALUE or ISFILTERED where suitable. Which result best verifies the intended outcome?
Context-inspection functions detect the state of user or visual filters for conditional calculations. This evidence exercises the actual success condition rather than only confirming that a resource exists.
That observation would verify a different goal: One customer with three transactions contributes one to the person count. It does not demonstrate the specific required result: Single-customer and multi-customer slicer selections follow the intended branches.
That observation would verify a different goal: Only active history versions contribute to the resulting customer count. It does not demonstrate the specific required result: Single-customer and multi-customer slicer selections follow the intended branches.
That observation would verify a different goal: The highest revenue product receives rank one under the selected period. It does not demonstrate the specific required result: Single-customer and multi-customer slicer selections follow the intended branches.
A Fabric lakehouse contains billions of curated Delta rows, and BI users want fast analysis without full Import refreshes. Which implementation decision best addresses the stated requirement?
Direct Lake loads required Delta-backed columns into VertiPaq as queries demand rather than making a full Import replica. The proposed action directly targets the problem described in the scenario.
Design a supported composite model combining Import and DirectQuery tables. is an approach for a different requirement: Composite models can mix storage modes when the design and relationships support it. In the present case, direct Lake loads required Delta-backed columns into VertiPaq as queries demand rather than making a full Import replica.
Trigger or allow a successful Direct Lake framing refresh after creation or schema changes. is an approach for a different requirement: A framing operation updates references to current Delta files without performing a full Import load. In the present case, direct Lake loads required Delta-backed columns into VertiPaq as queries demand rather than making a full Import replica.
Apply appropriate OneLake or semantic-model security instead of relying on SQL endpoint RLS for that path. is an approach for a different requirement: Direct Lake on OneLake bypasses the SQL analytics endpoint and does not inherit its SQL RLS. In the present case, direct Lake loads required Delta-backed columns into VertiPaq as queries demand rather than making a full Import replica.
A report must combine an infrequently changing reference set and a live SQL fact source. The team plans to implement this change: Design a supported composite model combining Import and DirectQuery tables. Which result best verifies the intended outcome?
Composite models can mix storage modes when the design and relationships support it. This evidence exercises the actual success condition rather than only confirming that a resource exists.
That observation would verify a different goal: A new committed source transaction appears in the report without an Import processing cycle. It does not demonstrate the specific required result: A report combines both sources and updates to the DirectQuery fact are visible promptly.
That observation would verify a different goal: A query executes in Direct Lake mode or reports an error rather than silently switching to DirectQuery. It does not demonstrate the specific required result: A report combines both sources and updates to the DirectQuery fact are visible promptly.
That observation would verify a different goal: A refresh captures new source rows and subsequent report queries run from the imported model. It does not demonstrate the specific required result: A report combines both sources and updates to the DirectQuery fact are visible promptly.
A developer tries SUM(Quantity)*SUM(UnitPrice), which yields inflated revenue. The team plans to implement this change: Use a DAX SUMX iterator over sales rows to sum the row-level product. Which result best verifies the intended outcome?
SUMX evaluates an expression per row and then aggregates the results. This evidence exercises the actual success condition rather than only confirming that a resource exists.
That observation would verify a different goal: Paid-only average matches known test rows even in an unfiltered visual. It does not demonstrate the specific required result: Two test rows with differing prices yield the correct sum of line extensions.
That observation would verify a different goal: The report returns the configured fallback for zero history and a correct percent otherwise. It does not demonstrate the specific required result: Two test rows with differing prices yield the correct sum of line extensions.
That observation would verify a different goal: The refactored measure returns identical KPI values with fewer repeated expensive operations. It does not demonstrate the specific required result: Two test rows with differing prices yield the correct sum of line extensions.
A financial system publishes live values in an external SQL database, and users cannot wait for scheduled Import refresh. Which implementation decision best addresses the stated requirement?
DirectQuery sends requests to the source instead of relying solely on a cached imported copy. The proposed action directly targets the problem described in the scenario.
Design a supported composite model combining Import and DirectQuery tables. is an approach for a different requirement: Composite models can mix storage modes when the design and relationships support it. In the present case, directQuery sends requests to the source instead of relying solely on a cached imported copy.
Use Direct Lake on OneLake and check its supported security requirements. is an approach for a different requirement: Direct Lake on OneLake executes without SQL endpoint DirectQuery fallback. In the present case, directQuery sends requests to the source instead of relying solely on a cached imported copy.
Materialize the view to an appropriate Delta table, or knowingly accept DirectQuery fallback. is an approach for a different requirement: Unmaterialized SQL views in Direct Lake on SQL can trigger DirectQuery fallback with different performance. In the present case, directQuery sends requests to the source instead of relying solely on a cached imported copy.
A calculation group produces different numeric result types and requires context-sensitive display formats. The team plans to implement this change: Configure a dynamic format string for the relevant measure or calculation group item. Which result best verifies the intended outcome?
Dynamic format strings change presentation format while preserving the underlying numeric value. This evidence exercises the actual success condition rather than only confirming that a resource exists.
That observation would verify a different goal: A time calculation selection changes both Sales and Margin measures using the same group logic. It does not demonstrate the specific required result: Currency displays with a symbol and percentage measures display as percentages without text conversion.
That observation would verify a different goal: The combined period-and-currency measure matches an independently calculated expected value. It does not demonstrate the specific required result: Currency displays with a symbol and percentage measures display as percentages without text conversion.
That observation would verify a different goal: Choosing Units instead of Revenue changes the measure on the same chart. It does not demonstrate the specific required result: Currency displays with a symbol and percentage measures display as percentages without text conversion.
The team wants a development setting that surfaces unsupported Direct Lake patterns instead of hiding them. Which implementation decision best addresses the stated requirement?
DirectLakeOnly fails when conditions for Direct Lake aren't met, rather than silently falling back. The proposed action directly targets the problem described in the scenario.
Use Direct Lake on OneLake and check its supported security requirements. is an approach for a different requirement: Direct Lake on OneLake executes without SQL endpoint DirectQuery fallback. In the present case, directLakeOnly fails when conditions for Direct Lake aren't met, rather than silently falling back.
Design a supported composite model combining Import and DirectQuery tables. is an approach for a different requirement: Composite models can mix storage modes when the design and relationships support it. In the present case, directLakeOnly fails when conditions for Direct Lake aren't met, rather than silently falling back.
Use a supported composite design based on Direct Lake on OneLake plus Import tables. is an approach for a different requirement: Direct Lake on OneLake supports composite modeling where its rules permit additional modes. In the present case, directLakeOnly fails when conditions for Direct Lake aren't met, rather than silently falling back.
Please check your mailbox for a message from support@examlabs.com and follow the directions.