Microsoft Fabric Analytics Engineer DP-600 Semantic Model Design DAX And Composite Models Practice Test

 

Skill 3.1 – 98 original questions

This Microsoft DP-600 practice test focuses on semantic model design dax and composite models through original scenario-based questions aligned to the active DP-600 skills measured as of July 21, 2026. Use the complete ExamSnap DP-600 collection for broader practice across Microsoft Fabric analytics lifecycle, data preparation, querying, and semantic modeling. For broader exam preparation, review the Microsoft DP-600 Exam Dumps page.

Instructions: Select the best answer for each question. Review the explanation after answering; each option includes a reason it is or is not the strongest choice for the scenario.

Question 1

Woodgrove Bank is troubleshooting a design decision in the marketing semantic model. The desired end state is to maximize interactive performance for a moderate dataset that can be refreshed on a schedule; the change must be easy to audit later. Which change should the BI platform team make? Existing users should keep their current access.

  1. Apply the RangeStart and RangeEnd filters in a foldable transformation
  2. Use Import storage mode
  3. Choose Direct Lake on OneLake
  4. Use direct column filters or more efficient set-based DAX where semantics allow
  5. Enable large semantic model storage format for the model

Correct answer: B

Why: Import loads data into the VertiPaq in-memory engine and generally provides the fastest query performance when refresh latency is acceptable. This directly matches the stated requirement.

Option review:

A: Query folding lets the source execute the partition predicates efficiently, which is important for scalable incremental refresh. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

B: Import loads data into the VertiPaq in-memory engine and generally provides the fastest query performance when refresh latency is acceptable. This directly matches the stated requirement.

C: Direct Lake on OneLake uses OneLake directly and operates without DirectQuery fallback. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

D: Avoiding expensive iterator patterns over large tables can reduce formula-engine work and improve query performance. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

E: Large semantic model storage format is designed for supported capacities and models that need to exceed standard size limits. This can be valid for ‘Identify use cases for and configure large semantic model storage format’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

Learning point: Use Import storage mode

Question 2

For the supply-chain lakehouse, Coho Winery has documented a business requirement to query a supported source at request time because the model must avoid storing an imported copy. The security analytics team must meet it in a way where the implementation should be easy to troubleshoot. What is the best choice? Existing users should keep their current access.

  1. Use direct column filters or more efficient set-based DAX where semantics allow
  2. Use DirectQuery storage mode
  3. Create both relationships and use an inactive relationship for the secondary date when appropriate
  4. Use DAX Studio or equivalent server-timing diagnostics to profile the measure
  5. Configure an incremental refresh policy with RangeStart and RangeEnd parameters

Correct answer: B

Why: DirectQuery leaves data in the source and sends queries at report time, trading source dependency for fresher access without a full import. This directly matches the stated requirement.

Option review:

A: Avoiding expensive iterator patterns over large tables can reduce formula-engine work and improve query performance. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

B: DirectQuery leaves data in the source and sends queries at report time, trading source dependency for fresher access without a full import. This directly matches the stated requirement.

C: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This can be valid for ‘Implement relationships, such as bridge tables and many-to-many relationships’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

D: Server timings and query plans help identify whether a DAX expression is spending time in formula-engine iteration or storage-engine scans. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

E: Incremental refresh partitions the table so scheduled refresh can process only the required recent range instead of reloading all history. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

Learning point: Use DirectQuery storage mode

Question 3

A governance review of Adventure Works’s IoT telemetry solution asks for evidence that the solution can analyze OneLake Delta data at scale without a traditional import refresh. Because the solution should avoid unnecessary custom code, which action should be approved? Existing users should keep their current access.

  1. Use Direct Lake storage mode
  2. Use the appropriate DAX window function with an explicit ordering definition
  3. Model a fact table surrounded by dimension tables with clear one-to-many relationships
  4. Configure an incremental refresh policy with RangeStart and RangeEnd parameters
  5. Create a calculation group

Correct answer: A

Why: Direct Lake reads OneLake-backed Delta data for semantic-model queries without a conventional import copy. This directly matches the stated requirement.

Option review:

A: Direct Lake reads OneLake-backed Delta data for semantic-model queries without a conventional import copy. This directly matches the stated requirement.

B: DAX window functions support ordered row-window calculations without manually reconstructing the entire sequence logic. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

C: A star schema gives the semantic model a predictable analytical structure and simplifies filter propagation. This can be valid for ‘Implement a star schema for a semantic model’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

D: Incremental refresh partitions the table so scheduled refresh can process only the required recent range instead of reloading all history. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

E: Calculation groups centralize reusable calculation logic and reduce measure proliferation. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

Learning point: Use Direct Lake storage mode

Question 4

Before expanding the finance reporting platform, the customer insights team at Tailspin Toys must optimize a shared dimension in a composite model so it can behave efficiently with both imported and DirectQuery facts. The rollout plan says that the design must preserve a clear development lifecycle. Which option most directly addresses the requirement? Existing users should keep their current access.

  1. Configure an incremental refresh policy with RangeStart and RangeEnd parameters
  2. Use a semantic-model star schema with dimensions filtering the fact table
  3. Use Dual storage mode for the compatible dimension
  4. Use a supported composite model with Direct Lake on OneLake plus Import
  5. Model a fact table surrounded by dimension tables with clear one-to-many relationships

Correct answer: C

Why: Dual can act as Import or DirectQuery depending on the query path and can improve composite-model dimension behavior. This directly matches the stated requirement.

Option review:

A: Incremental refresh partitions the table so scheduled refresh can process only the required recent range instead of reloading all history. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

B: Dimension-to-fact filtering aligns the model with common analytical patterns and reduces relationship ambiguity. This can be valid for ‘Implement a star schema for a semantic model’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

C: Dual can act as Import or DirectQuery depending on the query path and can improve composite-model dimension behavior. This directly matches the stated requirement.

D: Direct Lake on OneLake supports composite modeling with other compatible storage modes in supported scenarios. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

E: A star schema gives the semantic model a predictable analytical structure and simplifies filter propagation. This can be valid for ‘Implement a star schema for a semantic model’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

Learning point: Use Dual storage mode for the compatible dimension

Question 5

Fourth Coffee is redesigning its retail performance dashboard. The retail insights team must maximize interactive performance for a moderate dataset that can be refreshed on a schedule. In addition, the team must avoid granting broader access than required. Which action is the best fit? No unrelated workspace or model permissions should be changed.

  1. Use Import storage mode
  2. Configure the model for DirectLakeOnly behavior where supported
  3. Use direct column filters or more efficient set-based DAX where semantics allow
  4. Choose Direct Lake on the SQL analytics endpoint
  5. Check whether the query is falling back to DirectQuery and remove the condition that triggers fallback

Correct answer: A

Why: Import loads data into the VertiPaq in-memory engine and generally provides the fastest query performance when refresh latency is acceptable. This directly matches the stated requirement.

Option review:

A: Import loads data into the VertiPaq in-memory engine and generally provides the fastest query performance when refresh latency is acceptable. This directly matches the stated requirement.

B: DirectLakeOnly prevents DirectQuery fallback, causing unsupported queries to fail instead of silently using DirectQuery. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

C: Avoiding expensive iterator patterns over large tables can reduce formula-engine work and improve query performance. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

D: Direct Lake on SQL is the choice when the model must depend on supported SQL analytics endpoint security semantics. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

E: Direct Lake on SQL can fall back to DirectQuery for unsupported scenarios, which can materially change query performance. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

Learning point: Use Import storage mode

Question 6

During a design review for Wide World Importers’s marketing semantic model, one requirement is non-negotiable: query a supported source at request time because the model must avoid storing an imported copy. Because the change must be easy to audit later, what should the BI platform team implement? No unrelated workspace or model permissions should be changed.

  1. Use DirectQuery storage mode
  2. Configure the model for DirectLakeOnly behavior where supported
  3. Use an iterator such as SUMX over the required table expression
  4. Use the supported Direct Lake refresh or framing operation
  5. Use a dynamic format string

Correct answer: A

Why: DirectQuery leaves data in the source and sends queries at report time, trading source dependency for fresher access without a full import. This directly matches the stated requirement.

Option review:

A: DirectQuery leaves data in the source and sends queries at report time, trading source dependency for fresher access without a full import. This directly matches the stated requirement.

B: DirectLakeOnly prevents DirectQuery fallback, causing unsupported queries to fail instead of silently using DirectQuery. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

C: Iterator functions evaluate an expression for each row and then aggregate the results. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

D: Direct Lake refresh or framing updates the model view of OneLake data rather than loading a conventional imported copy. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

E: Dynamic format strings change presentation without converting the measure result to text. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

Learning point: Use DirectQuery storage mode

Question 7

The security analytics team at Northwind Traders is preparing the next release of its supply-chain lakehouse. They need to analyze OneLake Delta data at scale without a traditional import refresh; the implementation should be easy to troubleshoot. Which choice most directly satisfies the requirement? No unrelated workspace or model permissions should be changed.

  1. Use the appropriate DAX window function with an explicit ordering definition
  2. Create a field parameter
  3. Create a composite model over the remote semantic model and the local data
  4. Use Direct Lake storage mode
  5. Choose Direct Lake on the SQL analytics endpoint

Correct answer: D

Why: Direct Lake reads OneLake-backed Delta data for semantic-model queries without a conventional import copy. This directly matches the stated requirement.

Option review:

A: DAX window functions support ordered row-window calculations without manually reconstructing the entire sequence logic. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

B: Field parameters let consumers dynamically choose which modeled fields a visual uses. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

C: Composite models can extend a remote semantic model with additional local model objects when supported. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

D: Direct Lake reads OneLake-backed Delta data for semantic-model queries without a conventional import copy. This directly matches the stated requirement.

E: Direct Lake on SQL is the choice when the model must depend on supported SQL analytics endpoint security semantics. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

Learning point: Use Direct Lake storage mode

Question 8

A production readiness review at Trey Research found a gap in the IoT telemetry solution. The remediation must optimize a shared dimension in a composite model so it can behave efficiently with both imported and DirectQuery facts, and the solution should avoid unnecessary custom code. What is the most appropriate action? No unrelated workspace or model permissions should be changed.

  1. Use incremental refresh and define a shorter refresh window than the historical retention window
  2. Use Dual storage mode for the compatible dimension
  3. Enable large semantic model storage format for the model
  4. Configure the model for DirectLakeOnly behavior where supported
  5. Create a field parameter

Correct answer: B

Why: Dual can act as Import or DirectQuery depending on the query path and can improve composite-model dimension behavior. This directly matches the stated requirement.

Option review:

A: The policy can retain a long history while refreshing only the recent period that is still subject to change. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

B: Dual can act as Import or DirectQuery depending on the query path and can improve composite-model dimension behavior. This directly matches the stated requirement.

C: Large semantic model storage format is designed for supported capacities and models that need to exceed standard size limits. This can be valid for ‘Identify use cases for and configure large semantic model storage format’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

D: DirectLakeOnly prevents DirectQuery fallback, causing unsupported queries to fail instead of silently using DirectQuery. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

E: Field parameters let consumers dynamically choose which modeled fields a visual uses. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

Learning point: Use Dual storage mode for the compatible dimension

Question 9

For a new phase of the finance reporting platform, Alpine Ski House asks the customer insights team to maximize interactive performance for a moderate dataset that can be refreshed on a schedule. The architecture decision record also states that the design must preserve a clear development lifecycle. Which approach should be selected? The team will validate the change first in a nonproduction environment.

  1. Use direct column filters or more efficient set-based DAX where semantics allow
  2. Use the appropriate DAX window function with an explicit ordering definition
  3. Model a fact table surrounded by dimension tables with clear one-to-many relationships
  4. Use Import storage mode
  5. Configure an incremental refresh policy with RangeStart and RangeEnd parameters

Correct answer: D

Why: Import loads data into the VertiPaq in-memory engine and generally provides the fastest query performance when refresh latency is acceptable. This directly matches the stated requirement.

Option review:

A: Avoiding expensive iterator patterns over large tables can reduce formula-engine work and improve query performance. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

B: DAX window functions support ordered row-window calculations without manually reconstructing the entire sequence logic. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

C: A star schema gives the semantic model a predictable analytical structure and simplifies filter propagation. This can be valid for ‘Implement a star schema for a semantic model’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

D: Import loads data into the VertiPaq in-memory engine and generally provides the fastest query performance when refresh latency is acceptable. This directly matches the stated requirement.

E: Incremental refresh partitions the table so scheduled refresh can process only the required recent range instead of reloading all history. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

Learning point: Use Import storage mode

Question 10

Contoso is standardizing how the retail performance dashboard is managed. The immediate goal is to query a supported source at request time because the model must avoid storing an imported copy. Given that the team must avoid granting broader access than required, which option should the retail insights team choose? The team will validate the change first in a nonproduction environment.

  1. Use DirectQuery storage mode
  2. Use CALCULATE with an appropriate FILTER table expression
  3. Model a fact table surrounded by dimension tables with clear one-to-many relationships
  4. Apply the RangeStart and RangeEnd filters in a foldable transformation
  5. Create both relationships and use an inactive relationship for the secondary date when appropriate

Correct answer: A

Why: DirectQuery leaves data in the source and sends queries at report time, trading source dependency for fresher access without a full import. This directly matches the stated requirement.

Option review:

A: DirectQuery leaves data in the source and sends queries at report time, trading source dependency for fresher access without a full import. This directly matches the stated requirement.

B: FILTER can construct the row set while CALCULATE evaluates the measure under the resulting filter context. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

C: A star schema gives the semantic model a predictable analytical structure and simplifies filter propagation. This can be valid for ‘Implement a star schema for a semantic model’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

D: Query folding lets the source execute the partition predicates efficiently, which is important for scalable incremental refresh. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

E: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This can be valid for ‘Implement relationships, such as bridge tables and many-to-many relationships’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

Learning point: Use DirectQuery storage mode

Question 11

An internal audit of Wingtip Toys’s marketing semantic model identifies this requirement: analyze OneLake Delta data at scale without a traditional import refresh. The BI platform team also notes that the change must be easy to audit later. What should they do? The team will validate the change first in a nonproduction environment.

  1. Build a composite model that uses the appropriate storage mode for each table
  2. Use an iterator such as SUMX over the required table expression
  3. Use a supported composite model with Direct Lake on OneLake plus Import
  4. Use Direct Lake storage mode
  5. Create a calculation group

Correct answer: D

Why: Direct Lake reads OneLake-backed Delta data for semantic-model queries without a conventional import copy. This directly matches the stated requirement.

Option review:

A: Composite models can combine tables that use different storage modes so each part of the model matches its latency and performance needs. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

B: Iterator functions evaluate an expression for each row and then aggregate the results. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

C: Direct Lake on OneLake supports composite modeling with other compatible storage modes in supported scenarios. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

D: Direct Lake reads OneLake-backed Delta data for semantic-model queries without a conventional import copy. This directly matches the stated requirement.

E: Calculation groups centralize reusable calculation logic and reduce measure proliferation. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

Learning point: Use Direct Lake storage mode

Question 12

The supply-chain lakehouse at Proseware is moving from proof of concept to production. Before rollout, the security analytics team must optimize a shared dimension in a composite model so it can behave efficiently with both imported and DirectQuery facts, while ensuring that the implementation should be easy to troubleshoot. Which action best meets both needs? The team will validate the change first in a nonproduction environment.

  1. Use a supported composite model with Direct Lake on OneLake plus Import
  2. Create both relationships and use an inactive relationship for the secondary date when appropriate
  3. Reduce unnecessary visuals or interactions and lower the amount of data each visual requests
  4. Check whether the query is falling back to DirectQuery and remove the condition that triggers fallback
  5. Use Dual storage mode for the compatible dimension

Correct answer: E

Why: Dual can act as Import or DirectQuery depending on the query path and can improve composite-model dimension behavior. This directly matches the stated requirement.

Option review:

A: Direct Lake on OneLake supports composite modeling with other compatible storage modes in supported scenarios. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

B: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This can be valid for ‘Implement relationships, such as bridge tables and many-to-many relationships’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

C: Fewer, more focused visual queries reduce rendering and query workload, especially on high-cardinality pages. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

D: Direct Lake on SQL can fall back to DirectQuery for unsupported scenarios, which can materially change query performance. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

E: Dual can act as Import or DirectQuery depending on the query path and can improve composite-model dimension behavior. This directly matches the stated requirement.

Learning point: Use Dual storage mode for the compatible dimension

Question 13

Blue Yonder Airlines has a change request for the IoT telemetry solution: maximize interactive performance for a moderate dataset that can be refreshed on a schedule. The Fabric center of excellence wants a solution where the solution should avoid unnecessary custom code. Which implementation is most suitable? The solution must work with the current Fabric architecture rather than a parallel custom platform.

  1. Use an iterator such as SUMX over the required table expression
  2. Build a composite model that uses the appropriate storage mode for each table
  3. Create a composite model over the remote semantic model and the local data
  4. Use Import storage mode
  5. Configure the model for DirectLakeOnly behavior where supported

Correct answer: D

Why: Import loads data into the VertiPaq in-memory engine and generally provides the fastest query performance when refresh latency is acceptable. This directly matches the stated requirement.

Option review:

A: Iterator functions evaluate an expression for each row and then aggregate the results. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

B: Composite models can combine tables that use different storage modes so each part of the model matches its latency and performance needs. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

C: Composite models can extend a remote semantic model with additional local model objects when supported. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

D: Import loads data into the VertiPaq in-memory engine and generally provides the fastest query performance when refresh latency is acceptable. This directly matches the stated requirement.

E: DirectLakeOnly prevents DirectQuery fallback, causing unsupported queries to fail instead of silently using DirectQuery. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

Learning point: Use Import storage mode

Question 14

A solution architect reviewing Fabrikam’s finance reporting platform asks the customer insights team to query a supported source at request time because the model must avoid storing an imported copy. Since the design must preserve a clear development lifecycle, which recommendation is strongest? The solution must work with the current Fabric architecture rather than a parallel custom platform.

  1. Use DirectQuery storage mode
  2. Introduce a bridge table at the customer-segment membership grain
  3. Store the intermediate expression in a DAX VAR and reference the variable
  4. Use Power BI Performance Analyzer to capture and compare visual query durations
  5. Choose Direct Lake on the SQL analytics endpoint

Correct answer: A

Why: DirectQuery leaves data in the source and sends queries at report time, trading source dependency for fresher access without a full import. This directly matches the stated requirement.

Option review:

A: DirectQuery leaves data in the source and sends queries at report time, trading source dependency for fresher access without a full import. This directly matches the stated requirement.

B: A bridge table resolves a many-to-many business relationship into controlled one-to-many relationships for filtering and measures. This can be valid for ‘Implement relationships, such as bridge tables and many-to-many relationships’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

C: Variables reduce repeated expressions and make complex DAX easier to read and maintain. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

D: Performance Analyzer provides per-visual timing information that helps isolate slow visuals and DAX queries. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

E: Direct Lake on SQL uses the SQL analytics endpoint for metadata and can fall back to DirectQuery in supported scenarios. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Choose a storage mode’.

Learning point: Use DirectQuery storage mode

Question 15

Tailspin Toys is troubleshooting a design decision in the supply-chain lakehouse. The desired end state is to make measures easy to reason about by separating transactions from descriptive business attributes; the choice should use a native Fabric capability. Which change should the BI platform team make? Existing users should keep their current access.

  1. Optimize the model toward a clear star schema and efficient relationships
  2. Model a fact table surrounded by dimension tables with clear one-to-many relationships
  3. Use Import storage mode
  4. Compute the expression once in a DAX variable and reuse it
  5. Reduce unnecessary visuals or interactions and lower the amount of data each visual requests

Correct answer: B

Why: A star schema gives the semantic model a predictable analytical structure and simplifies filter propagation. This directly matches the stated requirement.

Option review:

A: A well-designed star schema reduces relationship complexity and helps the engine resolve filters efficiently. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

B: A star schema gives the semantic model a predictable analytical structure and simplifies filter propagation. This directly matches the stated requirement.

C: Import loads data into the VertiPaq in-memory engine and generally provides the fastest query performance when refresh latency is acceptable. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

D: Variables can reduce repeated evaluation and also make the measure easier to optimize. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

E: Fewer, more focused visual queries reduce rendering and query workload, especially on high-cardinality pages. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

Learning point: Model a fact table surrounded by dimension tables with clear one-to-many relationships

Question 16

For the IoT telemetry solution, Fourth Coffee has documented a business requirement to avoid ambiguous filters by placing descriptive attributes in dimensions and numeric events at a declared grain. The security analytics team must meet it in a way where the design should minimize duplicated data. What is the best choice? Existing users should keep their current access.

  1. Use Dual storage mode for the compatible dimension
  2. Use a semantic-model star schema with dimensions filtering the fact table
  3. Use CALCULATE with an appropriate FILTER table expression
  4. Use incremental refresh and define a shorter refresh window than the historical retention window
  5. Use DAX Studio or equivalent server-timing diagnostics to profile the measure

Correct answer: B

Why: Dimension-to-fact filtering aligns the model with common analytical patterns and reduces relationship ambiguity. This directly matches the stated requirement.

Option review:

A: Dual can act as Import or DirectQuery depending on the query path and can improve composite-model dimension behavior. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

B: Dimension-to-fact filtering aligns the model with common analytical patterns and reduces relationship ambiguity. This directly matches the stated requirement.

C: FILTER can construct the row set while CALCULATE evaluates the measure under the resulting filter context. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

D: The policy can retain a long history while refreshing only the recent period that is still subject to change. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

E: Server timings and query plans help identify whether a DAX expression is spending time in formula-engine iteration or storage-engine scans. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

Learning point: Use a semantic-model star schema with dimensions filtering the fact table

Question 17

A governance review of Wide World Importers’s finance reporting platform asks for evidence that the solution can make measures easy to reason about by separating transactions from descriptive business attributes. Because least privilege must be preserved, which action should be approved? No unrelated workspace or model permissions should be changed.

  1. Build a composite model that uses the appropriate storage mode for each table
  2. Create both relationships and use an inactive relationship for the secondary date when appropriate
  3. Model a fact table surrounded by dimension tables with clear one-to-many relationships
  4. Store the intermediate expression in a DAX VAR and reference the variable
  5. Use a supported composite model with Direct Lake on OneLake plus Import

Correct answer: C

Why: A star schema gives the semantic model a predictable analytical structure and simplifies filter propagation. This directly matches the stated requirement.

Option review:

A: Composite models can combine tables that use different storage modes so each part of the model matches its latency and performance needs. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

B: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This can be valid for ‘Implement relationships, such as bridge tables and many-to-many relationships’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

C: A star schema gives the semantic model a predictable analytical structure and simplifies filter propagation. This directly matches the stated requirement.

D: Variables reduce repeated expressions and make complex DAX easier to read and maintain. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

E: Direct Lake on OneLake supports composite modeling with other compatible storage modes in supported scenarios. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

Learning point: Model a fact table surrounded by dimension tables with clear one-to-many relationships

Question 18

Before expanding the retail performance dashboard, the customer insights team at Northwind Traders must avoid ambiguous filters by placing descriptive attributes in dimensions and numeric events at a declared grain. The rollout plan says that the rollout must support controlled validation. Which option most directly addresses the requirement? No unrelated workspace or model permissions should be changed.

  1. Apply the RangeStart and RangeEnd filters in a foldable transformation
  2. Use Power BI Performance Analyzer to capture and compare visual query durations
  3. Use a supported composite model with Direct Lake on OneLake plus Import
  4. Build a composite model that uses the appropriate storage mode for each table
  5. Use a semantic-model star schema with dimensions filtering the fact table

Correct answer: E

Why: Dimension-to-fact filtering aligns the model with common analytical patterns and reduces relationship ambiguity. This directly matches the stated requirement.

Option review:

A: Query folding lets the source execute the partition predicates efficiently, which is important for scalable incremental refresh. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

B: Performance Analyzer provides per-visual timing information that helps isolate slow visuals and DAX queries. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

C: Direct Lake on OneLake supports composite modeling with other compatible storage modes in supported scenarios. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

D: Composite models can combine tables that use different storage modes so each part of the model matches its latency and performance needs. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

E: Dimension-to-fact filtering aligns the model with common analytical patterns and reduces relationship ambiguity. This directly matches the stated requirement.

Learning point: Use a semantic-model star schema with dimensions filtering the fact table

Question 19

Trey Research is redesigning its marketing semantic model. The retail insights team must make measures easy to reason about by separating transactions from descriptive business attributes. In addition, the team wants predictable performance and behavior. Which action is the best fit? The team will validate the change first in a nonproduction environment.

  1. Optimize the model toward a clear star schema and efficient relationships
  2. Create a field parameter
  3. Configure the semantic model to use large semantic model storage format
  4. Use direct column filters or more efficient set-based DAX where semantics allow
  5. Model a fact table surrounded by dimension tables with clear one-to-many relationships

Correct answer: E

Why: A star schema gives the semantic model a predictable analytical structure and simplifies filter propagation. This directly matches the stated requirement.

Option review:

A: A well-designed star schema reduces relationship complexity and helps the engine resolve filters efficiently. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

B: Field parameters let consumers dynamically choose which modeled fields a visual uses. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

C: The large storage format supports enterprise-scale models and related management operations on supported capacity. This can be valid for ‘Identify use cases for and configure large semantic model storage format’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

D: Avoiding expensive iterator patterns over large tables can reduce formula-engine work and improve query performance. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

E: A star schema gives the semantic model a predictable analytical structure and simplifies filter propagation. This directly matches the stated requirement.

Learning point: Model a fact table surrounded by dimension tables with clear one-to-many relationships

Question 20

During a design review for Alpine Ski House’s supply-chain lakehouse, one requirement is non-negotiable: avoid ambiguous filters by placing descriptive attributes in dimensions and numeric events at a declared grain. Because the choice should use a native Fabric capability, what should the BI platform team implement? The team will validate the change first in a nonproduction environment.

  1. Use incremental refresh and define a shorter refresh window than the historical retention window
  2. Use Direct Lake storage mode
  3. Use a semantic-model star schema with dimensions filtering the fact table
  4. Create both relationships and use an inactive relationship for the secondary date when appropriate
  5. Create a composite model over the remote semantic model and the local data

Correct answer: C

Why: Dimension-to-fact filtering aligns the model with common analytical patterns and reduces relationship ambiguity. This directly matches the stated requirement.

Option review:

A: The policy can retain a long history while refreshing only the recent period that is still subject to change. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

B: Direct Lake reads OneLake-backed Delta data for semantic-model queries without a conventional import copy. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

C: Dimension-to-fact filtering aligns the model with common analytical patterns and reduces relationship ambiguity. This directly matches the stated requirement.

D: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This can be valid for ‘Implement relationships, such as bridge tables and many-to-many relationships’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

E: Composite models can extend a remote semantic model with additional local model objects when supported. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

Learning point: Use a semantic-model star schema with dimensions filtering the fact table

Question 21

The security analytics team at Contoso is preparing the next release of its IoT telemetry solution. They need to make measures easy to reason about by separating transactions from descriptive business attributes; the design should minimize duplicated data. Which choice most directly satisfies the requirement? The solution must work with the current Fabric architecture rather than a parallel custom platform.

  1. Configure the semantic model to use large semantic model storage format
  2. Use Import storage mode
  3. Model a fact table surrounded by dimension tables with clear one-to-many relationships
  4. Choose Direct Lake on the SQL analytics endpoint
  5. Use Power BI Performance Analyzer to capture and compare visual query durations

Correct answer: C

Why: A star schema gives the semantic model a predictable analytical structure and simplifies filter propagation. This directly matches the stated requirement.

Option review:

A: The large storage format supports enterprise-scale models and related management operations on supported capacity. This can be valid for ‘Identify use cases for and configure large semantic model storage format’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

B: Import loads data into the VertiPaq in-memory engine and generally provides the fastest query performance when refresh latency is acceptable. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

C: A star schema gives the semantic model a predictable analytical structure and simplifies filter propagation. This directly matches the stated requirement.

D: Direct Lake on SQL is the choice when the model must depend on supported SQL analytics endpoint security semantics. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

E: Performance Analyzer provides per-visual timing information that helps isolate slow visuals and DAX queries. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

Learning point: Model a fact table surrounded by dimension tables with clear one-to-many relationships

Question 22

A production readiness review at Wingtip Toys found a gap in the finance reporting platform. The remediation must avoid ambiguous filters by placing descriptive attributes in dimensions and numeric events at a declared grain, and least privilege must be preserved. What is the most appropriate action? The solution must work with the current Fabric architecture rather than a parallel custom platform.

  1. Use DirectQuery storage mode
  2. Configure an incremental refresh policy with RangeStart and RangeEnd parameters
  3. Use a semantic-model star schema with dimensions filtering the fact table
  4. Choose Direct Lake on the SQL analytics endpoint
  5. Introduce a bridge table at the customer-segment membership grain

Correct answer: C

Why: Dimension-to-fact filtering aligns the model with common analytical patterns and reduces relationship ambiguity. This directly matches the stated requirement.

Option review:

A: DirectQuery leaves data in the source and sends queries at report time, trading source dependency for fresher access without a full import. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

B: Incremental refresh partitions the table so scheduled refresh can process only the required recent range instead of reloading all history. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

C: Dimension-to-fact filtering aligns the model with common analytical patterns and reduces relationship ambiguity. This directly matches the stated requirement.

D: Direct Lake on SQL is the choice when the model must depend on supported SQL analytics endpoint security semantics. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

E: A bridge table resolves a many-to-many business relationship into controlled one-to-many relationships for filtering and measures. This can be valid for ‘Implement relationships, such as bridge tables and many-to-many relationships’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

Learning point: Use a semantic-model star schema with dimensions filtering the fact table

Question 23

For a new phase of the retail performance dashboard, Proseware asks the customer insights team to make measures easy to reason about by separating transactions from descriptive business attributes. The architecture decision record also states that the rollout must support controlled validation. Which approach should be selected? The design decision will be reviewed by both data engineering and BI owners.

  1. Configure the semantic model to use large semantic model storage format
  2. Use a supported composite model with Direct Lake on OneLake plus Import
  3. Use incremental refresh and define a shorter refresh window than the historical retention window
  4. Model a fact table surrounded by dimension tables with clear one-to-many relationships
  5. Use DirectQuery storage mode

Correct answer: D

Why: A star schema gives the semantic model a predictable analytical structure and simplifies filter propagation. This directly matches the stated requirement.

Option review:

A: The large storage format supports enterprise-scale models and related management operations on supported capacity. This can be valid for ‘Identify use cases for and configure large semantic model storage format’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

B: Direct Lake on OneLake supports composite modeling with other compatible storage modes in supported scenarios. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

C: The policy can retain a long history while refreshing only the recent period that is still subject to change. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

D: A star schema gives the semantic model a predictable analytical structure and simplifies filter propagation. This directly matches the stated requirement.

E: DirectQuery leaves data in the source and sends queries at report time, trading source dependency for fresher access without a full import. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

Learning point: Model a fact table surrounded by dimension tables with clear one-to-many relationships

Question 24

Blue Yonder Airlines is standardizing how the marketing semantic model is managed. The immediate goal is to avoid ambiguous filters by placing descriptive attributes in dimensions and numeric events at a declared grain. Given that the team wants predictable performance and behavior, which option should the retail insights team choose? The design decision will be reviewed by both data engineering and BI owners.

  1. Enable large semantic model storage format for the model
  2. Use a dynamic format string
  3. Configure an incremental refresh policy with RangeStart and RangeEnd parameters
  4. Use a semantic-model star schema with dimensions filtering the fact table
  5. Create a field parameter

Correct answer: D

Why: Dimension-to-fact filtering aligns the model with common analytical patterns and reduces relationship ambiguity. This directly matches the stated requirement.

Option review:

A: Large semantic model storage format is designed for supported capacities and models that need to exceed standard size limits. This can be valid for ‘Identify use cases for and configure large semantic model storage format’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

B: Dynamic format strings change presentation without converting the measure result to text. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

C: Incremental refresh partitions the table so scheduled refresh can process only the required recent range instead of reloading all history. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

D: Dimension-to-fact filtering aligns the model with common analytical patterns and reduces relationship ambiguity. This directly matches the stated requirement.

E: Field parameters let consumers dynamically choose which modeled fields a visual uses. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

Learning point: Use a semantic-model star schema with dimensions filtering the fact table

Question 25

An internal audit of Fabrikam’s supply-chain lakehouse identifies this requirement: make measures easy to reason about by separating transactions from descriptive business attributes. The BI platform team also notes that the choice should use a native Fabric capability. What should they do? Existing users should keep their current access.

  1. Model a fact table surrounded by dimension tables with clear one-to-many relationships
  2. Use Direct Lake storage mode
  3. Use Dual storage mode for the compatible dimension
  4. Use the supported Direct Lake refresh or framing operation
  5. Create both relationships and use an inactive relationship for the secondary date when appropriate

Correct answer: A

Why: A star schema gives the semantic model a predictable analytical structure and simplifies filter propagation. This directly matches the stated requirement.

Option review:

A: A star schema gives the semantic model a predictable analytical structure and simplifies filter propagation. This directly matches the stated requirement.

B: Direct Lake reads OneLake-backed Delta data for semantic-model queries without a conventional import copy. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

C: Dual can act as Import or DirectQuery depending on the query path and can improve composite-model dimension behavior. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

D: Direct Lake refresh or framing updates the model view of OneLake data rather than loading a conventional imported copy. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

E: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This can be valid for ‘Implement relationships, such as bridge tables and many-to-many relationships’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

Learning point: Model a fact table surrounded by dimension tables with clear one-to-many relationships

Question 26

The IoT telemetry solution at Litware is moving from proof of concept to production. Before rollout, the security analytics team must avoid ambiguous filters by placing descriptive attributes in dimensions and numeric events at a declared grain, while ensuring that the design should minimize duplicated data. Which action best meets both needs? Existing users should keep their current access.

  1. Create a composite model over the remote semantic model and the local data
  2. Configure the model for DirectLakeOnly behavior where supported
  3. Create a field parameter
  4. Use Dual storage mode for the compatible dimension
  5. Use a semantic-model star schema with dimensions filtering the fact table

Correct answer: E

Why: Dimension-to-fact filtering aligns the model with common analytical patterns and reduces relationship ambiguity. This directly matches the stated requirement.

Option review:

A: Composite models can extend a remote semantic model with additional local model objects when supported. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

B: DirectLakeOnly prevents DirectQuery fallback, causing unsupported queries to fail instead of silently using DirectQuery. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

C: Field parameters let consumers dynamically choose which modeled fields a visual uses. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

D: Dual can act as Import or DirectQuery depending on the query path and can improve composite-model dimension behavior. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

E: Dimension-to-fact filtering aligns the model with common analytical patterns and reduces relationship ambiguity. This directly matches the stated requirement.

Learning point: Use a semantic-model star schema with dimensions filtering the fact table

Question 27

Woodgrove Bank has a change request for the finance reporting platform: make measures easy to reason about by separating transactions from descriptive business attributes. The Fabric center of excellence wants a solution where least privilege must be preserved. Which implementation is most suitable? No unrelated workspace or model permissions should be changed.

  1. Model a fact table surrounded by dimension tables with clear one-to-many relationships
  2. Choose Direct Lake on the SQL analytics endpoint
  3. Use direct column filters or more efficient set-based DAX where semantics allow
  4. Optimize the model toward a clear star schema and efficient relationships
  5. Use CALCULATE with an appropriate FILTER table expression

Correct answer: A

Why: A star schema gives the semantic model a predictable analytical structure and simplifies filter propagation. This directly matches the stated requirement.

Option review:

A: A star schema gives the semantic model a predictable analytical structure and simplifies filter propagation. This directly matches the stated requirement.

B: Direct Lake on SQL is the choice when the model must depend on supported SQL analytics endpoint security semantics. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

C: Avoiding expensive iterator patterns over large tables can reduce formula-engine work and improve query performance. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

D: A well-designed star schema reduces relationship complexity and helps the engine resolve filters efficiently. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

E: FILTER can construct the row set while CALCULATE evaluates the measure under the resulting filter context. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

Learning point: Model a fact table surrounded by dimension tables with clear one-to-many relationships

Question 28

A solution architect reviewing Coho Winery’s retail performance dashboard asks the customer insights team to avoid ambiguous filters by placing descriptive attributes in dimensions and numeric events at a declared grain. Since the rollout must support controlled validation, which recommendation is strongest? No unrelated workspace or model permissions should be changed.

  1. Create a composite model over the remote semantic model and the local data
  2. Use Import storage mode
  3. Store the intermediate expression in a DAX VAR and reference the variable
  4. Use a semantic-model star schema with dimensions filtering the fact table
  5. Use direct column filters or more efficient set-based DAX where semantics allow

Correct answer: D

Why: Dimension-to-fact filtering aligns the model with common analytical patterns and reduces relationship ambiguity. This directly matches the stated requirement.

Option review:

A: Composite models can extend a remote semantic model with additional local model objects when supported. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

B: Import loads data into the VertiPaq in-memory engine and generally provides the fastest query performance when refresh latency is acceptable. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

C: Variables reduce repeated expressions and make complex DAX easier to read and maintain. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

D: Dimension-to-fact filtering aligns the model with common analytical patterns and reduces relationship ambiguity. This directly matches the stated requirement.

E: Avoiding expensive iterator patterns over large tables can reduce formula-engine work and improve query performance. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Implement a star schema for a semantic model’.

Learning point: Use a semantic-model star schema with dimensions filtering the fact table

Question 29

Northwind Traders is troubleshooting a design decision in the IoT telemetry solution. The desired end state is to model customers that can belong to multiple segments while each segment can contain multiple customers; the approach should remain understandable to future maintainers. Which change should the BI platform team make? Existing users should keep their current access.

  1. Use a supported composite model with Direct Lake on OneLake plus Import
  2. Use DirectQuery storage mode
  3. Choose Direct Lake on the SQL analytics endpoint
  4. Configure the semantic model to use large semantic model storage format
  5. Introduce a bridge table at the customer-segment membership grain

Correct answer: E

Why: A bridge table resolves a many-to-many business relationship into controlled one-to-many relationships for filtering and measures. This directly matches the stated requirement.

Option review:

A: Direct Lake on OneLake supports composite modeling with other compatible storage modes in supported scenarios. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

B: DirectQuery leaves data in the source and sends queries at report time, trading source dependency for fresher access without a full import. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

C: Direct Lake on SQL is the choice when the model must depend on supported SQL analytics endpoint security semantics. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

D: The large storage format supports enterprise-scale models and related management operations on supported capacity. This can be valid for ‘Identify use cases for and configure large semantic model storage format’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

E: A bridge table resolves a many-to-many business relationship into controlled one-to-many relationships for filtering and measures. This directly matches the stated requirement.

Learning point: Introduce a bridge table at the customer-segment membership grain

Question 30

For the finance reporting platform, Trey Research has documented a business requirement to use one date dimension for Order Date and Ship Date while keeping one relationship active by default. The security analytics team must meet it in a way where the implementation should reduce operational overhead. What is the best choice? Existing users should keep their current access.

  1. Choose Direct Lake on OneLake
  2. Use Import storage mode
  3. Create both relationships and use an inactive relationship for the secondary date when appropriate
  4. Reduce unnecessary visuals or interactions and lower the amount of data each visual requests
  5. Use direct column filters or more efficient set-based DAX where semantics allow

Correct answer: C

Why: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This directly matches the stated requirement.

Option review:

A: Direct Lake on OneLake uses OneLake directly and operates without DirectQuery fallback. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

B: Import loads data into the VertiPaq in-memory engine and generally provides the fastest query performance when refresh latency is acceptable. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

C: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This directly matches the stated requirement.

D: Fewer, more focused visual queries reduce rendering and query workload, especially on high-cardinality pages. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

E: Avoiding expensive iterator patterns over large tables can reduce formula-engine work and improve query performance. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

Learning point: Create both relationships and use an inactive relationship for the secondary date when appropriate

Question 31

A governance review of Alpine Ski House’s retail performance dashboard asks for evidence that the solution can model customers that can belong to multiple segments while each segment can contain multiple customers. Because the solution must remain maintainable as usage grows, which action should be approved? No unrelated workspace or model permissions should be changed.

  1. Compute the expression once in a DAX variable and reuse it
  2. Use DAX Studio or equivalent server-timing diagnostics to profile the measure
  3. Introduce a bridge table at the customer-segment membership grain
  4. Use the supported Direct Lake refresh or framing operation
  5. Use the appropriate DAX window function with an explicit ordering definition

Correct answer: C

Why: A bridge table resolves a many-to-many business relationship into controlled one-to-many relationships for filtering and measures. This directly matches the stated requirement.

Option review:

A: Variables can reduce repeated evaluation and also make the measure easier to optimize. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

B: Server timings and query plans help identify whether a DAX expression is spending time in formula-engine iteration or storage-engine scans. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

C: A bridge table resolves a many-to-many business relationship into controlled one-to-many relationships for filtering and measures. This directly matches the stated requirement.

D: Direct Lake refresh or framing updates the model view of OneLake data rather than loading a conventional imported copy. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

E: DAX window functions support ordered row-window calculations without manually reconstructing the entire sequence logic. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

Learning point: Introduce a bridge table at the customer-segment membership grain

Question 32

Before expanding the marketing semantic model, the customer insights team at Contoso must use one date dimension for Order Date and Ship Date while keeping one relationship active by default. The rollout plan says that the team wants the smallest administrative blast radius. Which option most directly addresses the requirement? No unrelated workspace or model permissions should be changed.

  1. Use Power BI Performance Analyzer to capture and compare visual query durations
  2. Use the supported Direct Lake refresh or framing operation
  3. Create both relationships and use an inactive relationship for the secondary date when appropriate
  4. Reduce unnecessary visuals or interactions and lower the amount of data each visual requests
  5. Create a field parameter

Correct answer: C

Why: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This directly matches the stated requirement.

Option review:

A: Performance Analyzer provides per-visual timing information that helps isolate slow visuals and DAX queries. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

B: Direct Lake refresh or framing updates the model view of OneLake data rather than loading a conventional imported copy. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

C: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This directly matches the stated requirement.

D: Fewer, more focused visual queries reduce rendering and query workload, especially on high-cardinality pages. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

E: Field parameters let consumers dynamically choose which modeled fields a visual uses. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

Learning point: Create both relationships and use an inactive relationship for the secondary date when appropriate

Question 33

Wingtip Toys is redesigning its supply-chain lakehouse. The retail insights team must model customers that can belong to multiple segments while each segment can contain multiple customers. In addition, the team wants to keep governance centralized. Which action is the best fit? The team will validate the change first in a nonproduction environment.

  1. Create a composite model over the remote semantic model and the local data
  2. Introduce a bridge table at the customer-segment membership grain
  3. Use Import storage mode
  4. Use Direct Lake storage mode
  5. Configure the model for DirectLakeOnly behavior where supported

Correct answer: B

Why: A bridge table resolves a many-to-many business relationship into controlled one-to-many relationships for filtering and measures. This directly matches the stated requirement.

Option review:

A: Composite models can extend a remote semantic model with additional local model objects when supported. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

B: A bridge table resolves a many-to-many business relationship into controlled one-to-many relationships for filtering and measures. This directly matches the stated requirement.

C: Import loads data into the VertiPaq in-memory engine and generally provides the fastest query performance when refresh latency is acceptable. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

D: Direct Lake reads OneLake-backed Delta data for semantic-model queries without a conventional import copy. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

E: DirectLakeOnly prevents DirectQuery fallback, causing unsupported queries to fail instead of silently using DirectQuery. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

Learning point: Introduce a bridge table at the customer-segment membership grain

Question 34

During a design review for Proseware’s IoT telemetry solution, one requirement is non-negotiable: use one date dimension for Order Date and Ship Date while keeping one relationship active by default. Because the approach should remain understandable to future maintainers, what should the BI platform team implement? The team will validate the change first in a nonproduction environment.

  1. Create both relationships and use an inactive relationship for the secondary date when appropriate
  2. Model a fact table surrounded by dimension tables with clear one-to-many relationships
  3. Use direct column filters or more efficient set-based DAX where semantics allow
  4. Enable large semantic model storage format for the model
  5. Compute the expression once in a DAX variable and reuse it

Correct answer: A

Why: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This directly matches the stated requirement.

Option review:

A: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This directly matches the stated requirement.

B: A star schema gives the semantic model a predictable analytical structure and simplifies filter propagation. This can be valid for ‘Implement a star schema for a semantic model’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

C: Avoiding expensive iterator patterns over large tables can reduce formula-engine work and improve query performance. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

D: Large semantic model storage format is designed for supported capacities and models that need to exceed standard size limits. This can be valid for ‘Identify use cases for and configure large semantic model storage format’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

E: Variables can reduce repeated evaluation and also make the measure easier to optimize. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

Learning point: Create both relationships and use an inactive relationship for the secondary date when appropriate

Question 35

The security analytics team at Blue Yonder Airlines is preparing the next release of its finance reporting platform. They need to model customers that can belong to multiple segments while each segment can contain multiple customers; the implementation should reduce operational overhead. Which choice most directly satisfies the requirement? The solution must work with the current Fabric architecture rather than a parallel custom platform.

  1. Use the appropriate DAX window function with an explicit ordering definition
  2. Choose Direct Lake on the SQL analytics endpoint
  3. Create a field parameter
  4. Apply the RangeStart and RangeEnd filters in a foldable transformation
  5. Introduce a bridge table at the customer-segment membership grain

Correct answer: E

Why: A bridge table resolves a many-to-many business relationship into controlled one-to-many relationships for filtering and measures. This directly matches the stated requirement.

Option review:

A: DAX window functions support ordered row-window calculations without manually reconstructing the entire sequence logic. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

B: Direct Lake on SQL is the choice when the model must depend on supported SQL analytics endpoint security semantics. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

C: Field parameters let consumers dynamically choose which modeled fields a visual uses. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

D: Query folding lets the source execute the partition predicates efficiently, which is important for scalable incremental refresh. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

E: A bridge table resolves a many-to-many business relationship into controlled one-to-many relationships for filtering and measures. This directly matches the stated requirement.

Learning point: Introduce a bridge table at the customer-segment membership grain

Question 36

A production readiness review at Fabrikam found a gap in the retail performance dashboard. The remediation must use one date dimension for Order Date and Ship Date while keeping one relationship active by default, and the solution must remain maintainable as usage grows. What is the most appropriate action? The solution must work with the current Fabric architecture rather than a parallel custom platform.

  1. Use an iterator such as SUMX over the required table expression
  2. Configure the semantic model to use large semantic model storage format
  3. Use DAX Studio or equivalent server-timing diagnostics to profile the measure
  4. Create both relationships and use an inactive relationship for the secondary date when appropriate
  5. Apply the RangeStart and RangeEnd filters in a foldable transformation

Correct answer: D

Why: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This directly matches the stated requirement.

Option review:

A: Iterator functions evaluate an expression for each row and then aggregate the results. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

B: The large storage format supports enterprise-scale models and related management operations on supported capacity. This can be valid for ‘Identify use cases for and configure large semantic model storage format’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

C: Server timings and query plans help identify whether a DAX expression is spending time in formula-engine iteration or storage-engine scans. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

D: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This directly matches the stated requirement.

E: Query folding lets the source execute the partition predicates efficiently, which is important for scalable incremental refresh. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

Learning point: Create both relationships and use an inactive relationship for the secondary date when appropriate

Question 37

For a new phase of the marketing semantic model, Litware asks the customer insights team to model customers that can belong to multiple segments while each segment can contain multiple customers. The architecture decision record also states that the team wants the smallest administrative blast radius. Which approach should be selected? The design decision will be reviewed by both data engineering and BI owners.

  1. Create a field parameter
  2. Introduce a bridge table at the customer-segment membership grain
  3. Reduce unnecessary visuals or interactions and lower the amount of data each visual requests
  4. Configure the semantic model to use large semantic model storage format
  5. Use direct column filters or more efficient set-based DAX where semantics allow

Correct answer: B

Why: A bridge table resolves a many-to-many business relationship into controlled one-to-many relationships for filtering and measures. This directly matches the stated requirement.

Option review:

A: Field parameters let consumers dynamically choose which modeled fields a visual uses. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

B: A bridge table resolves a many-to-many business relationship into controlled one-to-many relationships for filtering and measures. This directly matches the stated requirement.

C: Fewer, more focused visual queries reduce rendering and query workload, especially on high-cardinality pages. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

D: The large storage format supports enterprise-scale models and related management operations on supported capacity. This can be valid for ‘Identify use cases for and configure large semantic model storage format’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

E: Avoiding expensive iterator patterns over large tables can reduce formula-engine work and improve query performance. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

Learning point: Introduce a bridge table at the customer-segment membership grain

Question 38

Woodgrove Bank is standardizing how the supply-chain lakehouse is managed. The immediate goal is to use one date dimension for Order Date and Ship Date while keeping one relationship active by default. Given that the team wants to keep governance centralized, which option should the retail insights team choose? The design decision will be reviewed by both data engineering and BI owners.

  1. Use Import storage mode
  2. Create both relationships and use an inactive relationship for the secondary date when appropriate
  3. Use Direct Lake storage mode
  4. Choose Direct Lake on the SQL analytics endpoint
  5. Reduce unnecessary visuals or interactions and lower the amount of data each visual requests

Correct answer: B

Why: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This directly matches the stated requirement.

Option review:

A: Import loads data into the VertiPaq in-memory engine and generally provides the fastest query performance when refresh latency is acceptable. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

B: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This directly matches the stated requirement.

C: Direct Lake reads OneLake-backed Delta data for semantic-model queries without a conventional import copy. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

D: Direct Lake on SQL is the choice when the model must depend on supported SQL analytics endpoint security semantics. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

E: Fewer, more focused visual queries reduce rendering and query workload, especially on high-cardinality pages. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

Learning point: Create both relationships and use an inactive relationship for the secondary date when appropriate

Question 39

An internal audit of Coho Winery’s IoT telemetry solution identifies this requirement: model customers that can belong to multiple segments while each segment can contain multiple customers. The BI platform team also notes that the approach should remain understandable to future maintainers. What should they do? Existing users should keep their current access.

  1. Store the intermediate expression in a DAX VAR and reference the variable
  2. Use Direct Lake storage mode
  3. Use Dual storage mode for the compatible dimension
  4. Introduce a bridge table at the customer-segment membership grain
  5. Use Power BI Performance Analyzer to capture and compare visual query durations

Correct answer: D

Why: A bridge table resolves a many-to-many business relationship into controlled one-to-many relationships for filtering and measures. This directly matches the stated requirement.

Option review:

A: Variables reduce repeated expressions and make complex DAX easier to read and maintain. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

B: Direct Lake reads OneLake-backed Delta data for semantic-model queries without a conventional import copy. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

C: Dual can act as Import or DirectQuery depending on the query path and can improve composite-model dimension behavior. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

D: A bridge table resolves a many-to-many business relationship into controlled one-to-many relationships for filtering and measures. This directly matches the stated requirement.

E: Performance Analyzer provides per-visual timing information that helps isolate slow visuals and DAX queries. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

Learning point: Introduce a bridge table at the customer-segment membership grain

Question 40

The finance reporting platform at Adventure Works is moving from proof of concept to production. Before rollout, the security analytics team must use one date dimension for Order Date and Ship Date while keeping one relationship active by default, while ensuring that the implementation should reduce operational overhead. Which action best meets both needs? Existing users should keep their current access.

  1. Reduce unnecessary visuals or interactions and lower the amount of data each visual requests
  2. Create a composite model over the remote semantic model and the local data
  3. Use Import storage mode
  4. Create both relationships and use an inactive relationship for the secondary date when appropriate
  5. Use a semantic-model star schema with dimensions filtering the fact table

Correct answer: D

Why: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This directly matches the stated requirement.

Option review:

A: Fewer, more focused visual queries reduce rendering and query workload, especially on high-cardinality pages. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

B: Composite models can extend a remote semantic model with additional local model objects when supported. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

C: Import loads data into the VertiPaq in-memory engine and generally provides the fastest query performance when refresh latency is acceptable. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

D: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This directly matches the stated requirement.

E: Dimension-to-fact filtering aligns the model with common analytical patterns and reduces relationship ambiguity. This can be valid for ‘Implement a star schema for a semantic model’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

Learning point: Create both relationships and use an inactive relationship for the secondary date when appropriate

Question 41

Tailspin Toys has a change request for the retail performance dashboard: model customers that can belong to multiple segments while each segment can contain multiple customers. The Fabric center of excellence wants a solution where the solution must remain maintainable as usage grows. Which implementation is most suitable? No unrelated workspace or model permissions should be changed.

  1. Use Dual storage mode for the compatible dimension
  2. Use DirectQuery storage mode
  3. Introduce a bridge table at the customer-segment membership grain
  4. Create a composite model over the remote semantic model and the local data
  5. Use direct column filters or more efficient set-based DAX where semantics allow

Correct answer: C

Why: A bridge table resolves a many-to-many business relationship into controlled one-to-many relationships for filtering and measures. This directly matches the stated requirement.

Option review:

A: Dual can act as Import or DirectQuery depending on the query path and can improve composite-model dimension behavior. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

B: DirectQuery leaves data in the source and sends queries at report time, trading source dependency for fresher access without a full import. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

C: A bridge table resolves a many-to-many business relationship into controlled one-to-many relationships for filtering and measures. This directly matches the stated requirement.

D: Composite models can extend a remote semantic model with additional local model objects when supported. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

E: Avoiding expensive iterator patterns over large tables can reduce formula-engine work and improve query performance. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

Learning point: Introduce a bridge table at the customer-segment membership grain

Question 42

A solution architect reviewing Fourth Coffee’s marketing semantic model asks the customer insights team to use one date dimension for Order Date and Ship Date while keeping one relationship active by default. Since the team wants the smallest administrative blast radius, which recommendation is strongest? No unrelated workspace or model permissions should be changed.

  1. Create a calculation group
  2. Create both relationships and use an inactive relationship for the secondary date when appropriate
  3. Compute the expression once in a DAX variable and reuse it
  4. Use CALCULATE with an appropriate FILTER table expression
  5. Build a composite model that uses the appropriate storage mode for each table

Correct answer: B

Why: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This directly matches the stated requirement.

Option review:

A: Calculation groups centralize reusable calculation logic and reduce measure proliferation. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

B: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This directly matches the stated requirement.

C: Variables can reduce repeated evaluation and also make the measure easier to optimize. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

D: FILTER can construct the row set while CALCULATE evaluates the measure under the resulting filter context. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

E: Composite models can combine tables that use different storage modes so each part of the model matches its latency and performance needs. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement relationships, such as bridge tables and many-to-many relationships’.

Learning point: Create both relationships and use an inactive relationship for the secondary date when appropriate

Question 43

Contoso is troubleshooting a design decision in the finance reporting platform. The desired end state is to reuse an intermediate result several times in one measure and improve readability; the implementation should be easy to troubleshoot. Which change should the BI platform team make? Existing users should keep their current access.

  1. Model a fact table surrounded by dimension tables with clear one-to-many relationships
  2. Apply the RangeStart and RangeEnd filters in a foldable transformation
  3. Create a field parameter
  4. Reduce unnecessary visuals or interactions and lower the amount of data each visual requests
  5. Store the intermediate expression in a DAX VAR and reference the variable

Correct answer: E

Why: Variables reduce repeated expressions and make complex DAX easier to read and maintain. This directly matches the stated requirement.

Option review:

A: A star schema gives the semantic model a predictable analytical structure and simplifies filter propagation. This can be valid for ‘Implement a star schema for a semantic model’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

B: Query folding lets the source execute the partition predicates efficiently, which is important for scalable incremental refresh. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

C: Field parameters let consumers dynamically choose which modeled fields a visual uses. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

D: Fewer, more focused visual queries reduce rendering and query workload, especially on high-cardinality pages. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

E: Variables reduce repeated expressions and make complex DAX easier to read and maintain. This directly matches the stated requirement.

Learning point: Store the intermediate expression in a DAX VAR and reference the variable

Question 44

For the retail performance dashboard, Wingtip Toys has documented a business requirement to calculate row-by-row extended amount before summing the result. The security analytics team must meet it in a way where the solution should avoid unnecessary custom code. What is the best choice? Existing users should keep their current access.

  1. Use Direct Lake storage mode
  2. Use an iterator such as SUMX over the required table expression
  3. Create a calculation group
  4. Configure an incremental refresh policy with RangeStart and RangeEnd parameters
  5. Use a dynamic format string

Correct answer: B

Why: Iterator functions evaluate an expression for each row and then aggregate the results. This directly matches the stated requirement.

Option review:

A: Direct Lake reads OneLake-backed Delta data for semantic-model queries without a conventional import copy. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

B: Iterator functions evaluate an expression for each row and then aggregate the results. This directly matches the stated requirement.

C: Calculation groups centralize reusable calculation logic and reduce measure proliferation. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

D: Incremental refresh partitions the table so scheduled refresh can process only the required recent range instead of reloading all history. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

E: Dynamic format strings change presentation without converting the measure result to text. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

Learning point: Use an iterator such as SUMX over the required table expression

Question 45

A governance review of Proseware’s marketing semantic model asks for evidence that the solution can calculate a measure over only rows that satisfy a dynamic table condition. Because the design must preserve a clear development lifecycle, which action should be approved? Existing users should keep their current access.

  1. Use the supported Direct Lake refresh or framing operation
  2. Enable large semantic model storage format for the model
  3. Create both relationships and use an inactive relationship for the secondary date when appropriate
  4. Use CALCULATE with an appropriate FILTER table expression
  5. Optimize the model toward a clear star schema and efficient relationships

Correct answer: D

Why: FILTER can construct the row set while CALCULATE evaluates the measure under the resulting filter context. This directly matches the stated requirement.

Option review:

A: Direct Lake refresh or framing updates the model view of OneLake data rather than loading a conventional imported copy. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

B: Large semantic model storage format is designed for supported capacities and models that need to exceed standard size limits. This can be valid for ‘Identify use cases for and configure large semantic model storage format’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

C: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This can be valid for ‘Implement relationships, such as bridge tables and many-to-many relationships’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

D: FILTER can construct the row set while CALCULATE evaluates the measure under the resulting filter context. This directly matches the stated requirement.

E: A well-designed star schema reduces relationship complexity and helps the engine resolve filters efficiently. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

Learning point: Use CALCULATE with an appropriate FILTER table expression

Question 46

Before expanding the supply-chain lakehouse, the customer insights team at Blue Yonder Airlines must compare a value with neighboring rows in an ordered analytical window. The rollout plan says that the team must avoid granting broader access than required. Which option most directly addresses the requirement? Existing users should keep their current access.

  1. Choose Direct Lake on the SQL analytics endpoint
  2. Configure the model for DirectLakeOnly behavior where supported
  3. Use the appropriate DAX window function with an explicit ordering definition
  4. Use the supported Direct Lake refresh or framing operation
  5. Reduce unnecessary visuals or interactions and lower the amount of data each visual requests

Correct answer: C

Why: DAX window functions support ordered row-window calculations without manually reconstructing the entire sequence logic. This directly matches the stated requirement.

Option review:

A: Direct Lake on SQL is the choice when the model must depend on supported SQL analytics endpoint security semantics. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

B: DirectLakeOnly prevents DirectQuery fallback, causing unsupported queries to fail instead of silently using DirectQuery. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

C: DAX window functions support ordered row-window calculations without manually reconstructing the entire sequence logic. This directly matches the stated requirement.

D: Direct Lake refresh or framing updates the model view of OneLake data rather than loading a conventional imported copy. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

E: Fewer, more focused visual queries reduce rendering and query workload, especially on high-cardinality pages. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

Learning point: Use the appropriate DAX window function with an explicit ordering definition

Question 47

Fabrikam is redesigning its IoT telemetry solution. The retail insights team must reuse an intermediate result several times in one measure and improve readability. In addition, the change must be easy to audit later. Which action is the best fit? No unrelated workspace or model permissions should be changed.

  1. Create a composite model over the remote semantic model and the local data
  2. Configure the semantic model to use large semantic model storage format
  3. Store the intermediate expression in a DAX VAR and reference the variable
  4. Reduce unnecessary visuals or interactions and lower the amount of data each visual requests
  5. Check whether the query is falling back to DirectQuery and remove the condition that triggers fallback

Correct answer: C

Why: Variables reduce repeated expressions and make complex DAX easier to read and maintain. This directly matches the stated requirement.

Option review:

A: Composite models can extend a remote semantic model with additional local model objects when supported. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

B: The large storage format supports enterprise-scale models and related management operations on supported capacity. This can be valid for ‘Identify use cases for and configure large semantic model storage format’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

C: Variables reduce repeated expressions and make complex DAX easier to read and maintain. This directly matches the stated requirement.

D: Fewer, more focused visual queries reduce rendering and query workload, especially on high-cardinality pages. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

E: Direct Lake on SQL can fall back to DirectQuery for unsupported scenarios, which can materially change query performance. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

Learning point: Store the intermediate expression in a DAX VAR and reference the variable

Question 48

During a design review for Litware’s finance reporting platform, one requirement is non-negotiable: calculate row-by-row extended amount before summing the result. Because the implementation should be easy to troubleshoot, what should the BI platform team implement? No unrelated workspace or model permissions should be changed.

  1. Use the supported Direct Lake refresh or framing operation
  2. Use a semantic-model star schema with dimensions filtering the fact table
  3. Use DirectQuery storage mode
  4. Use a dynamic format string
  5. Use an iterator such as SUMX over the required table expression

Correct answer: E

Why: Iterator functions evaluate an expression for each row and then aggregate the results. This directly matches the stated requirement.

Option review:

A: Direct Lake refresh or framing updates the model view of OneLake data rather than loading a conventional imported copy. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

B: Dimension-to-fact filtering aligns the model with common analytical patterns and reduces relationship ambiguity. This can be valid for ‘Implement a star schema for a semantic model’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

C: DirectQuery leaves data in the source and sends queries at report time, trading source dependency for fresher access without a full import. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

D: Dynamic format strings change presentation without converting the measure result to text. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

E: Iterator functions evaluate an expression for each row and then aggregate the results. This directly matches the stated requirement.

Learning point: Use an iterator such as SUMX over the required table expression

Question 49

The security analytics team at Woodgrove Bank is preparing the next release of its retail performance dashboard. They need to calculate a measure over only rows that satisfy a dynamic table condition; the solution should avoid unnecessary custom code. Which choice most directly satisfies the requirement? No unrelated workspace or model permissions should be changed.

  1. Use direct column filters or more efficient set-based DAX where semantics allow
  2. Configure an incremental refresh policy with RangeStart and RangeEnd parameters
  3. Use CALCULATE with an appropriate FILTER table expression
  4. Enable large semantic model storage format for the model
  5. Optimize the model toward a clear star schema and efficient relationships

Correct answer: C

Why: FILTER can construct the row set while CALCULATE evaluates the measure under the resulting filter context. This directly matches the stated requirement.

Option review:

A: Avoiding expensive iterator patterns over large tables can reduce formula-engine work and improve query performance. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

B: Incremental refresh partitions the table so scheduled refresh can process only the required recent range instead of reloading all history. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

C: FILTER can construct the row set while CALCULATE evaluates the measure under the resulting filter context. This directly matches the stated requirement.

D: Large semantic model storage format is designed for supported capacities and models that need to exceed standard size limits. This can be valid for ‘Identify use cases for and configure large semantic model storage format’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

E: A well-designed star schema reduces relationship complexity and helps the engine resolve filters efficiently. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

Learning point: Use CALCULATE with an appropriate FILTER table expression

Question 50

A production readiness review at Coho Winery found a gap in the marketing semantic model. The remediation must compare a value with neighboring rows in an ordered analytical window, and the design must preserve a clear development lifecycle. What is the most appropriate action? No unrelated workspace or model permissions should be changed.

  1. Use Direct Lake storage mode
  2. Use a semantic-model star schema with dimensions filtering the fact table
  3. Use a supported composite model with Direct Lake on OneLake plus Import
  4. Use DirectQuery storage mode
  5. Use the appropriate DAX window function with an explicit ordering definition

Correct answer: E

Why: DAX window functions support ordered row-window calculations without manually reconstructing the entire sequence logic. This directly matches the stated requirement.

Option review:

A: Direct Lake reads OneLake-backed Delta data for semantic-model queries without a conventional import copy. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

B: Dimension-to-fact filtering aligns the model with common analytical patterns and reduces relationship ambiguity. This can be valid for ‘Implement a star schema for a semantic model’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

C: Direct Lake on OneLake supports composite modeling with other compatible storage modes in supported scenarios. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

D: DirectQuery leaves data in the source and sends queries at report time, trading source dependency for fresher access without a full import. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

E: DAX window functions support ordered row-window calculations without manually reconstructing the entire sequence logic. This directly matches the stated requirement.

Learning point: Use the appropriate DAX window function with an explicit ordering definition

Question 51

For a new phase of the supply-chain lakehouse, Adventure Works asks the customer insights team to reuse an intermediate result several times in one measure and improve readability. The architecture decision record also states that the team must avoid granting broader access than required. Which approach should be selected? The team will validate the change first in a nonproduction environment.

  1. Configure the model for DirectLakeOnly behavior where supported
  2. Enable large semantic model storage format for the model
  3. Create a calculation group
  4. Store the intermediate expression in a DAX VAR and reference the variable
  5. Use the supported Direct Lake refresh or framing operation

Correct answer: D

Why: Variables reduce repeated expressions and make complex DAX easier to read and maintain. This directly matches the stated requirement.

Option review:

A: DirectLakeOnly prevents DirectQuery fallback, causing unsupported queries to fail instead of silently using DirectQuery. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

B: Large semantic model storage format is designed for supported capacities and models that need to exceed standard size limits. This can be valid for ‘Identify use cases for and configure large semantic model storage format’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

C: Calculation groups centralize reusable calculation logic and reduce measure proliferation. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

D: Variables reduce repeated expressions and make complex DAX easier to read and maintain. This directly matches the stated requirement.

E: Direct Lake refresh or framing updates the model view of OneLake data rather than loading a conventional imported copy. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

Learning point: Store the intermediate expression in a DAX VAR and reference the variable

Question 52

Tailspin Toys is standardizing how the IoT telemetry solution is managed. The immediate goal is to calculate row-by-row extended amount before summing the result. Given that the change must be easy to audit later, which option should the retail insights team choose? The team will validate the change first in a nonproduction environment.

  1. Use DAX Studio or equivalent server-timing diagnostics to profile the measure
  2. Use a dynamic format string
  3. Use an iterator such as SUMX over the required table expression
  4. Choose Direct Lake on the SQL analytics endpoint
  5. Create a composite model over the remote semantic model and the local data

Correct answer: C

Why: Iterator functions evaluate an expression for each row and then aggregate the results. This directly matches the stated requirement.

Option review:

A: Server timings and query plans help identify whether a DAX expression is spending time in formula-engine iteration or storage-engine scans. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

B: Dynamic format strings change presentation without converting the measure result to text. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

C: Iterator functions evaluate an expression for each row and then aggregate the results. This directly matches the stated requirement.

D: Direct Lake on SQL is the choice when the model must depend on supported SQL analytics endpoint security semantics. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

E: Composite models can extend a remote semantic model with additional local model objects when supported. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

Learning point: Use an iterator such as SUMX over the required table expression

Question 53

An internal audit of Fourth Coffee’s finance reporting platform identifies this requirement: calculate a measure over only rows that satisfy a dynamic table condition. The BI platform team also notes that the implementation should be easy to troubleshoot. What should they do? The team will validate the change first in a nonproduction environment.

  1. Use direct column filters or more efficient set-based DAX where semantics allow
  2. Reduce unnecessary visuals or interactions and lower the amount of data each visual requests
  3. Use CALCULATE with an appropriate FILTER table expression
  4. Use DAX Studio or equivalent server-timing diagnostics to profile the measure
  5. Optimize the model toward a clear star schema and efficient relationships

Correct answer: C

Why: FILTER can construct the row set while CALCULATE evaluates the measure under the resulting filter context. This directly matches the stated requirement.

Option review:

A: Avoiding expensive iterator patterns over large tables can reduce formula-engine work and improve query performance. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

B: Fewer, more focused visual queries reduce rendering and query workload, especially on high-cardinality pages. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

C: FILTER can construct the row set while CALCULATE evaluates the measure under the resulting filter context. This directly matches the stated requirement.

D: Server timings and query plans help identify whether a DAX expression is spending time in formula-engine iteration or storage-engine scans. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

E: A well-designed star schema reduces relationship complexity and helps the engine resolve filters efficiently. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

Learning point: Use CALCULATE with an appropriate FILTER table expression

Question 54

The retail performance dashboard at Wide World Importers is moving from proof of concept to production. Before rollout, the security analytics team must compare a value with neighboring rows in an ordered analytical window, while ensuring that the solution should avoid unnecessary custom code. Which action best meets both needs? The team will validate the change first in a nonproduction environment.

  1. Use Direct Lake storage mode
  2. Use DirectQuery storage mode
  3. Create a composite model over the remote semantic model and the local data
  4. Create a field parameter
  5. Use the appropriate DAX window function with an explicit ordering definition

Correct answer: E

Why: DAX window functions support ordered row-window calculations without manually reconstructing the entire sequence logic. This directly matches the stated requirement.

Option review:

A: Direct Lake reads OneLake-backed Delta data for semantic-model queries without a conventional import copy. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

B: DirectQuery leaves data in the source and sends queries at report time, trading source dependency for fresher access without a full import. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

C: Composite models can extend a remote semantic model with additional local model objects when supported. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

D: Field parameters let consumers dynamically choose which modeled fields a visual uses. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

E: DAX window functions support ordered row-window calculations without manually reconstructing the entire sequence logic. This directly matches the stated requirement.

Learning point: Use the appropriate DAX window function with an explicit ordering definition

Question 55

Northwind Traders has a change request for the marketing semantic model: reuse an intermediate result several times in one measure and improve readability. The Fabric center of excellence wants a solution where the design must preserve a clear development lifecycle. Which implementation is most suitable? The solution must work with the current Fabric architecture rather than a parallel custom platform.

  1. Store the intermediate expression in a DAX VAR and reference the variable
  2. Compute the expression once in a DAX variable and reuse it
  3. Create a calculation group
  4. Use Import storage mode
  5. Use a semantic-model star schema with dimensions filtering the fact table

Correct answer: A

Why: Variables reduce repeated expressions and make complex DAX easier to read and maintain. This directly matches the stated requirement.

Option review:

A: Variables reduce repeated expressions and make complex DAX easier to read and maintain. This directly matches the stated requirement.

B: Variables can reduce repeated evaluation and also make the measure easier to optimize. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

C: Calculation groups centralize reusable calculation logic and reduce measure proliferation. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

D: Import loads data into the VertiPaq in-memory engine and generally provides the fastest query performance when refresh latency is acceptable. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

E: Dimension-to-fact filtering aligns the model with common analytical patterns and reduces relationship ambiguity. This can be valid for ‘Implement a star schema for a semantic model’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

Learning point: Store the intermediate expression in a DAX VAR and reference the variable

Question 56

A solution architect reviewing Trey Research’s supply-chain lakehouse asks the customer insights team to calculate row-by-row extended amount before summing the result. Since the team must avoid granting broader access than required, which recommendation is strongest? The solution must work with the current Fabric architecture rather than a parallel custom platform.

  1. Choose Direct Lake on OneLake
  2. Use an iterator such as SUMX over the required table expression
  3. Use Power BI Performance Analyzer to capture and compare visual query durations
  4. Use a semantic-model star schema with dimensions filtering the fact table
  5. Create a field parameter

Correct answer: B

Why: Iterator functions evaluate an expression for each row and then aggregate the results. This directly matches the stated requirement.

Option review:

A: Direct Lake on OneLake uses OneLake directly and operates without DirectQuery fallback. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

B: Iterator functions evaluate an expression for each row and then aggregate the results. This directly matches the stated requirement.

C: Performance Analyzer provides per-visual timing information that helps isolate slow visuals and DAX queries. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

D: Dimension-to-fact filtering aligns the model with common analytical patterns and reduces relationship ambiguity. This can be valid for ‘Implement a star schema for a semantic model’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

E: Field parameters let consumers dynamically choose which modeled fields a visual uses. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’.

Learning point: Use an iterator such as SUMX over the required table expression

Question 57

Blue Yonder Airlines is troubleshooting a design decision in the retail performance dashboard. The desired end state is to apply the same time-intelligence transformations to many measures without creating a separate measure for every combination; the design should minimize duplicated data. Which change should the BI platform team make? Existing users should keep their current access.

  1. Use the supported Direct Lake refresh or framing operation
  2. Create a calculation group
  3. Choose Direct Lake on the SQL analytics endpoint
  4. Configure the model for DirectLakeOnly behavior where supported
  5. Use direct column filters or more efficient set-based DAX where semantics allow

Correct answer: B

Why: Calculation groups centralize reusable calculation logic and reduce measure proliferation. This directly matches the stated requirement.

Option review:

A: Direct Lake refresh or framing updates the model view of OneLake data rather than loading a conventional imported copy. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

B: Calculation groups centralize reusable calculation logic and reduce measure proliferation. This directly matches the stated requirement.

C: Direct Lake on SQL is the choice when the model must depend on supported SQL analytics endpoint security semantics. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

D: DirectLakeOnly prevents DirectQuery fallback, causing unsupported queries to fail instead of silently using DirectQuery. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

E: Avoiding expensive iterator patterns over large tables can reduce formula-engine work and improve query performance. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

Learning point: Create a calculation group

Question 58

For the marketing semantic model, Fabrikam has documented a business requirement to display one measure as currency or percentage depending on calculation context while keeping the value numeric. The security analytics team must meet it in a way where least privilege must be preserved. What is the best choice? Existing users should keep their current access.

  1. Use a dynamic format string
  2. Use a supported composite model with Direct Lake on OneLake plus Import
  3. Choose Direct Lake on the SQL analytics endpoint
  4. Configure the semantic model to use large semantic model storage format
  5. Use incremental refresh and define a shorter refresh window than the historical retention window

Correct answer: A

Why: Dynamic format strings change presentation without converting the measure result to text. This directly matches the stated requirement.

Option review:

A: Dynamic format strings change presentation without converting the measure result to text. This directly matches the stated requirement.

B: Direct Lake on OneLake supports composite modeling with other compatible storage modes in supported scenarios. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

C: Direct Lake on SQL uses the SQL analytics endpoint for metadata and can fall back to DirectQuery in supported scenarios. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

D: The large storage format supports enterprise-scale models and related management operations on supported capacity. This can be valid for ‘Identify use cases for and configure large semantic model storage format’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

E: The policy can retain a long history while refreshing only the recent period that is still subject to change. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

Learning point: Use a dynamic format string

Question 59

A governance review of Litware’s supply-chain lakehouse asks for evidence that the solution can let report users switch the dimension or measure shown in a visual from a slicer. Because the rollout must support controlled validation, which action should be approved? Existing users should keep their current access.

  1. Reduce unnecessary visuals or interactions and lower the amount of data each visual requests
  2. Choose Direct Lake on the SQL analytics endpoint
  3. Choose Direct Lake on OneLake
  4. Create a field parameter
  5. Use Import storage mode

Correct answer: D

Why: Field parameters let consumers dynamically choose which modeled fields a visual uses. This directly matches the stated requirement.

Option review:

A: Fewer, more focused visual queries reduce rendering and query workload, especially on high-cardinality pages. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

B: Direct Lake on SQL is the choice when the model must depend on supported SQL analytics endpoint security semantics. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

C: Direct Lake on OneLake uses OneLake directly and operates without DirectQuery fallback. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

D: Field parameters let consumers dynamically choose which modeled fields a visual uses. This directly matches the stated requirement.

E: Import loads data into the VertiPaq in-memory engine and generally provides the fastest query performance when refresh latency is acceptable. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

Learning point: Create a field parameter

Question 60

Before expanding the IoT telemetry solution, the customer insights team at Woodgrove Bank must apply the same time-intelligence transformations to many measures without creating a separate measure for every combination. The rollout plan says that the team wants predictable performance and behavior. Which option most directly addresses the requirement? No unrelated workspace or model permissions should be changed.

  1. Use the supported Direct Lake refresh or framing operation
  2. Check whether the query is falling back to DirectQuery and remove the condition that triggers fallback
  3. Build a composite model that uses the appropriate storage mode for each table
  4. Reduce unnecessary visuals or interactions and lower the amount of data each visual requests
  5. Create a calculation group

Correct answer: E

Why: Calculation groups centralize reusable calculation logic and reduce measure proliferation. This directly matches the stated requirement.

Option review:

A: Direct Lake refresh or framing updates the model view of OneLake data rather than loading a conventional imported copy. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

B: Direct Lake on SQL can fall back to DirectQuery for unsupported scenarios, which can materially change query performance. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

C: Composite models can combine tables that use different storage modes so each part of the model matches its latency and performance needs. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

D: Fewer, more focused visual queries reduce rendering and query workload, especially on high-cardinality pages. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

E: Calculation groups centralize reusable calculation logic and reduce measure proliferation. This directly matches the stated requirement.

Learning point: Create a calculation group

Question 61

Coho Winery is redesigning its finance reporting platform. The retail insights team must display one measure as currency or percentage depending on calculation context while keeping the value numeric. In addition, the choice should use a native Fabric capability. Which action is the best fit? No unrelated workspace or model permissions should be changed.

  1. Use a dynamic format string
  2. Use an iterator such as SUMX over the required table expression
  3. Create both relationships and use an inactive relationship for the secondary date when appropriate
  4. Use the supported Direct Lake refresh or framing operation
  5. Optimize the model toward a clear star schema and efficient relationships

Correct answer: A

Why: Dynamic format strings change presentation without converting the measure result to text. This directly matches the stated requirement.

Option review:

A: Dynamic format strings change presentation without converting the measure result to text. This directly matches the stated requirement.

B: Iterator functions evaluate an expression for each row and then aggregate the results. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

C: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This can be valid for ‘Implement relationships, such as bridge tables and many-to-many relationships’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

D: Direct Lake refresh or framing updates the model view of OneLake data rather than loading a conventional imported copy. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

E: A well-designed star schema reduces relationship complexity and helps the engine resolve filters efficiently. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

Learning point: Use a dynamic format string

Question 62

During a design review for Adventure Works’s retail performance dashboard, one requirement is non-negotiable: let report users switch the dimension or measure shown in a visual from a slicer. Because the design should minimize duplicated data, what should the BI platform team implement? No unrelated workspace or model permissions should be changed.

  1. Introduce a bridge table at the customer-segment membership grain
  2. Create a field parameter
  3. Choose Direct Lake on OneLake
  4. Reduce unnecessary visuals or interactions and lower the amount of data each visual requests
  5. Choose Direct Lake on the SQL analytics endpoint

Correct answer: B

Why: Field parameters let consumers dynamically choose which modeled fields a visual uses. This directly matches the stated requirement.

Option review:

A: A bridge table resolves a many-to-many business relationship into controlled one-to-many relationships for filtering and measures. This can be valid for ‘Implement relationships, such as bridge tables and many-to-many relationships’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

B: Field parameters let consumers dynamically choose which modeled fields a visual uses. This directly matches the stated requirement.

C: Direct Lake on OneLake uses OneLake directly and operates without DirectQuery fallback. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

D: Fewer, more focused visual queries reduce rendering and query workload, especially on high-cardinality pages. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

E: Direct Lake on SQL uses the SQL analytics endpoint for metadata and can fall back to DirectQuery in supported scenarios. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

Learning point: Create a field parameter

Question 63

The security analytics team at Tailspin Toys is preparing the next release of its marketing semantic model. They need to apply the same time-intelligence transformations to many measures without creating a separate measure for every combination; least privilege must be preserved. Which choice most directly satisfies the requirement? The team will validate the change first in a nonproduction environment.

  1. Use a supported composite model with Direct Lake on OneLake plus Import
  2. Use the appropriate DAX window function with an explicit ordering definition
  3. Use incremental refresh and define a shorter refresh window than the historical retention window
  4. Compute the expression once in a DAX variable and reuse it
  5. Create a calculation group

Correct answer: E

Why: Calculation groups centralize reusable calculation logic and reduce measure proliferation. This directly matches the stated requirement.

Option review:

A: Direct Lake on OneLake supports composite modeling with other compatible storage modes in supported scenarios. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

B: DAX window functions support ordered row-window calculations without manually reconstructing the entire sequence logic. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

C: The policy can retain a long history while refreshing only the recent period that is still subject to change. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

D: Variables can reduce repeated evaluation and also make the measure easier to optimize. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

E: Calculation groups centralize reusable calculation logic and reduce measure proliferation. This directly matches the stated requirement.

Learning point: Create a calculation group

Question 64

A production readiness review at Fourth Coffee found a gap in the supply-chain lakehouse. The remediation must display one measure as currency or percentage depending on calculation context while keeping the value numeric, and the rollout must support controlled validation. What is the most appropriate action? The team will validate the change first in a nonproduction environment.

  1. Use direct column filters or more efficient set-based DAX where semantics allow
  2. Use a dynamic format string
  3. Model a fact table surrounded by dimension tables with clear one-to-many relationships
  4. Configure the semantic model to use large semantic model storage format
  5. Enable large semantic model storage format for the model

Correct answer: B

Why: Dynamic format strings change presentation without converting the measure result to text. This directly matches the stated requirement.

Option review:

A: Avoiding expensive iterator patterns over large tables can reduce formula-engine work and improve query performance. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

B: Dynamic format strings change presentation without converting the measure result to text. This directly matches the stated requirement.

C: A star schema gives the semantic model a predictable analytical structure and simplifies filter propagation. This can be valid for ‘Implement a star schema for a semantic model’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

D: The large storage format supports enterprise-scale models and related management operations on supported capacity. This can be valid for ‘Identify use cases for and configure large semantic model storage format’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

E: Large semantic model storage format is designed for supported capacities and models that need to exceed standard size limits. This can be valid for ‘Identify use cases for and configure large semantic model storage format’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

Learning point: Use a dynamic format string

Question 65

For a new phase of the IoT telemetry solution, Wide World Importers asks the customer insights team to let report users switch the dimension or measure shown in a visual from a slicer. The architecture decision record also states that the team wants predictable performance and behavior. Which approach should be selected? The team will validate the change first in a nonproduction environment.

  1. Configure the semantic model to use large semantic model storage format
  2. Enable large semantic model storage format for the model
  3. Choose Direct Lake on OneLake
  4. Create a field parameter
  5. Use Power BI Performance Analyzer to capture and compare visual query durations

Correct answer: D

Why: Field parameters let consumers dynamically choose which modeled fields a visual uses. This directly matches the stated requirement.

Option review:

A: The large storage format supports enterprise-scale models and related management operations on supported capacity. This can be valid for ‘Identify use cases for and configure large semantic model storage format’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

B: Large semantic model storage format is designed for supported capacities and models that need to exceed standard size limits. This can be valid for ‘Identify use cases for and configure large semantic model storage format’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

C: Direct Lake on OneLake uses OneLake directly and operates without DirectQuery fallback. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

D: Field parameters let consumers dynamically choose which modeled fields a visual uses. This directly matches the stated requirement.

E: Performance Analyzer provides per-visual timing information that helps isolate slow visuals and DAX queries. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

Learning point: Create a field parameter

Question 66

Northwind Traders is standardizing how the finance reporting platform is managed. The immediate goal is to apply the same time-intelligence transformations to many measures without creating a separate measure for every combination. Given that the choice should use a native Fabric capability, which option should the retail insights team choose? The solution must work with the current Fabric architecture rather than a parallel custom platform.

  1. Check whether the query is falling back to DirectQuery and remove the condition that triggers fallback
  2. Use the supported Direct Lake refresh or framing operation
  3. Use the appropriate DAX window function with an explicit ordering definition
  4. Use a semantic-model star schema with dimensions filtering the fact table
  5. Create a calculation group

Correct answer: E

Why: Calculation groups centralize reusable calculation logic and reduce measure proliferation. This directly matches the stated requirement.

Option review:

A: Direct Lake on SQL can fall back to DirectQuery for unsupported scenarios, which can materially change query performance. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

B: Direct Lake refresh or framing updates the model view of OneLake data rather than loading a conventional imported copy. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

C: DAX window functions support ordered row-window calculations without manually reconstructing the entire sequence logic. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

D: Dimension-to-fact filtering aligns the model with common analytical patterns and reduces relationship ambiguity. This can be valid for ‘Implement a star schema for a semantic model’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

E: Calculation groups centralize reusable calculation logic and reduce measure proliferation. This directly matches the stated requirement.

Learning point: Create a calculation group

Question 67

An internal audit of Trey Research’s retail performance dashboard identifies this requirement: display one measure as currency or percentage depending on calculation context while keeping the value numeric. The BI platform team also notes that the design should minimize duplicated data. What should they do? The solution must work with the current Fabric architecture rather than a parallel custom platform.

  1. Use a dynamic format string
  2. Build a composite model that uses the appropriate storage mode for each table
  3. Model a fact table surrounded by dimension tables with clear one-to-many relationships
  4. Create both relationships and use an inactive relationship for the secondary date when appropriate
  5. Use incremental refresh and define a shorter refresh window than the historical retention window

Correct answer: A

Why: Dynamic format strings change presentation without converting the measure result to text. This directly matches the stated requirement.

Option review:

A: Dynamic format strings change presentation without converting the measure result to text. This directly matches the stated requirement.

B: Composite models can combine tables that use different storage modes so each part of the model matches its latency and performance needs. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

C: A star schema gives the semantic model a predictable analytical structure and simplifies filter propagation. This can be valid for ‘Implement a star schema for a semantic model’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

D: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This can be valid for ‘Implement relationships, such as bridge tables and many-to-many relationships’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

E: The policy can retain a long history while refreshing only the recent period that is still subject to change. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

Learning point: Use a dynamic format string

Question 68

The marketing semantic model at Alpine Ski House is moving from proof of concept to production. Before rollout, the security analytics team must let report users switch the dimension or measure shown in a visual from a slicer, while ensuring that least privilege must be preserved. Which action best meets both needs? The solution must work with the current Fabric architecture rather than a parallel custom platform.

  1. Model a fact table surrounded by dimension tables with clear one-to-many relationships
  2. Configure an incremental refresh policy with RangeStart and RangeEnd parameters
  3. Configure the model for DirectLakeOnly behavior where supported
  4. Choose Direct Lake on OneLake
  5. Create a field parameter

Correct answer: E

Why: Field parameters let consumers dynamically choose which modeled fields a visual uses. This directly matches the stated requirement.

Option review:

A: A star schema gives the semantic model a predictable analytical structure and simplifies filter propagation. This can be valid for ‘Implement a star schema for a semantic model’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

B: Incremental refresh partitions the table so scheduled refresh can process only the required recent range instead of reloading all history. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

C: DirectLakeOnly prevents DirectQuery fallback, causing unsupported queries to fail instead of silently using DirectQuery. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

D: Direct Lake on OneLake uses OneLake directly and operates without DirectQuery fallback. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

E: Field parameters let consumers dynamically choose which modeled fields a visual uses. This directly matches the stated requirement.

Learning point: Create a field parameter

Question 69

Contoso has a change request for the supply-chain lakehouse: apply the same time-intelligence transformations to many measures without creating a separate measure for every combination. The Fabric center of excellence wants a solution where the rollout must support controlled validation. Which implementation is most suitable? The design decision will be reviewed by both data engineering and BI owners.

  1. Use the supported Direct Lake refresh or framing operation
  2. Enable large semantic model storage format for the model
  3. Use the appropriate DAX window function with an explicit ordering definition
  4. Configure the semantic model to use large semantic model storage format
  5. Create a calculation group

Correct answer: E

Why: Calculation groups centralize reusable calculation logic and reduce measure proliferation. This directly matches the stated requirement.

Option review:

A: Direct Lake refresh or framing updates the model view of OneLake data rather than loading a conventional imported copy. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

B: Large semantic model storage format is designed for supported capacities and models that need to exceed standard size limits. This can be valid for ‘Identify use cases for and configure large semantic model storage format’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

C: DAX window functions support ordered row-window calculations without manually reconstructing the entire sequence logic. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

D: The large storage format supports enterprise-scale models and related management operations on supported capacity. This can be valid for ‘Identify use cases for and configure large semantic model storage format’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

E: Calculation groups centralize reusable calculation logic and reduce measure proliferation. This directly matches the stated requirement.

Learning point: Create a calculation group

Question 70

A solution architect reviewing Wingtip Toys’s IoT telemetry solution asks the customer insights team to display one measure as currency or percentage depending on calculation context while keeping the value numeric. Since the team wants predictable performance and behavior, which recommendation is strongest? The design decision will be reviewed by both data engineering and BI owners.

  1. Use direct column filters or more efficient set-based DAX where semantics allow
  2. Use a dynamic format string
  3. Model a fact table surrounded by dimension tables with clear one-to-many relationships
  4. Introduce a bridge table at the customer-segment membership grain
  5. Use a supported composite model with Direct Lake on OneLake plus Import

Correct answer: B

Why: Dynamic format strings change presentation without converting the measure result to text. This directly matches the stated requirement.

Option review:

A: Avoiding expensive iterator patterns over large tables can reduce formula-engine work and improve query performance. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

B: Dynamic format strings change presentation without converting the measure result to text. This directly matches the stated requirement.

C: A star schema gives the semantic model a predictable analytical structure and simplifies filter propagation. This can be valid for ‘Implement a star schema for a semantic model’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

D: A bridge table resolves a many-to-many business relationship into controlled one-to-many relationships for filtering and measures. This can be valid for ‘Implement relationships, such as bridge tables and many-to-many relationships’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

E: Direct Lake on OneLake supports composite modeling with other compatible storage modes in supported scenarios. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Implement calculation groups, dynamic format strings, and field parameters’.

Learning point: Use a dynamic format string

Question 71

Woodgrove Bank is troubleshooting a design decision in the marketing semantic model. The desired end state is to support a semantic model that is expected to grow beyond standard model-size limits on supported capacity; the implementation should reduce operational overhead. Which change should the BI platform team make? Existing users should keep their current access.

  1. Use the supported Direct Lake refresh or framing operation
  2. Use an iterator such as SUMX over the required table expression
  3. Store the intermediate expression in a DAX VAR and reference the variable
  4. Reduce unnecessary visuals or interactions and lower the amount of data each visual requests
  5. Enable large semantic model storage format for the model

Correct answer: E

Why: Large semantic model storage format is designed for supported capacities and models that need to exceed standard size limits. This directly matches the stated requirement.

Option review:

A: Direct Lake refresh or framing updates the model view of OneLake data rather than loading a conventional imported copy. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

B: Iterator functions evaluate an expression for each row and then aggregate the results. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

C: Variables reduce repeated expressions and make complex DAX easier to read and maintain. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

D: Fewer, more focused visual queries reduce rendering and query workload, especially on high-cardinality pages. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

E: Large semantic model storage format is designed for supported capacities and models that need to exceed standard size limits. This directly matches the stated requirement.

Learning point: Enable large semantic model storage format for the model

Question 72

For the supply-chain lakehouse, Coho Winery has documented a business requirement to prepare a large enterprise model for advanced XMLA management and large-volume storage on supported capacity. The security analytics team must meet it in a way where the solution must remain maintainable as usage grows. What is the best choice? Existing users should keep their current access.

  1. Use a semantic-model star schema with dimensions filtering the fact table
  2. Configure the semantic model to use large semantic model storage format
  3. Choose Direct Lake on OneLake
  4. Use Import storage mode
  5. Introduce a bridge table at the customer-segment membership grain

Correct answer: B

Why: The large storage format supports enterprise-scale models and related management operations on supported capacity. This directly matches the stated requirement.

Option review:

A: Dimension-to-fact filtering aligns the model with common analytical patterns and reduces relationship ambiguity. This can be valid for ‘Implement a star schema for a semantic model’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

B: The large storage format supports enterprise-scale models and related management operations on supported capacity. This directly matches the stated requirement.

C: Direct Lake on OneLake uses OneLake directly and operates without DirectQuery fallback. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

D: Import loads data into the VertiPaq in-memory engine and generally provides the fastest query performance when refresh latency is acceptable. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

E: A bridge table resolves a many-to-many business relationship into controlled one-to-many relationships for filtering and measures. This can be valid for ‘Implement relationships, such as bridge tables and many-to-many relationships’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

Learning point: Configure the semantic model to use large semantic model storage format

Question 73

A governance review of Adventure Works’s IoT telemetry solution asks for evidence that the solution can support a semantic model that is expected to grow beyond standard model-size limits on supported capacity. Because the team wants the smallest administrative blast radius, which action should be approved? No unrelated workspace or model permissions should be changed.

  1. Use a dynamic format string
  2. Use incremental refresh and define a shorter refresh window than the historical retention window
  3. Enable large semantic model storage format for the model
  4. Choose Direct Lake on OneLake
  5. Use CALCULATE with an appropriate FILTER table expression

Correct answer: C

Why: Large semantic model storage format is designed for supported capacities and models that need to exceed standard size limits. This directly matches the stated requirement.

Option review:

A: Dynamic format strings change presentation without converting the measure result to text. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

B: The policy can retain a long history while refreshing only the recent period that is still subject to change. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

C: Large semantic model storage format is designed for supported capacities and models that need to exceed standard size limits. This directly matches the stated requirement.

D: Direct Lake on OneLake uses OneLake directly and operates without DirectQuery fallback. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

E: FILTER can construct the row set while CALCULATE evaluates the measure under the resulting filter context. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

Learning point: Enable large semantic model storage format for the model

Question 74

Before expanding the finance reporting platform, the customer insights team at Tailspin Toys must prepare a large enterprise model for advanced XMLA management and large-volume storage on supported capacity. The rollout plan says that the team wants to keep governance centralized. Which option most directly addresses the requirement? No unrelated workspace or model permissions should be changed.

  1. Check whether the query is falling back to DirectQuery and remove the condition that triggers fallback
  2. Configure the semantic model to use large semantic model storage format
  3. Configure an incremental refresh policy with RangeStart and RangeEnd parameters
  4. Model a fact table surrounded by dimension tables with clear one-to-many relationships
  5. Use Power BI Performance Analyzer to capture and compare visual query durations

Correct answer: B

Why: The large storage format supports enterprise-scale models and related management operations on supported capacity. This directly matches the stated requirement.

Option review:

A: Direct Lake on SQL can fall back to DirectQuery for unsupported scenarios, which can materially change query performance. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

B: The large storage format supports enterprise-scale models and related management operations on supported capacity. This directly matches the stated requirement.

C: Incremental refresh partitions the table so scheduled refresh can process only the required recent range instead of reloading all history. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

D: A star schema gives the semantic model a predictable analytical structure and simplifies filter propagation. This can be valid for ‘Implement a star schema for a semantic model’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

E: Performance Analyzer provides per-visual timing information that helps isolate slow visuals and DAX queries. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

Learning point: Configure the semantic model to use large semantic model storage format

Question 75

Fourth Coffee is redesigning its retail performance dashboard. The retail insights team must support a semantic model that is expected to grow beyond standard model-size limits on supported capacity. In addition, the approach should remain understandable to future maintainers. Which action is the best fit? The team will validate the change first in a nonproduction environment.

  1. Compute the expression once in a DAX variable and reuse it
  2. Enable large semantic model storage format for the model
  3. Configure an incremental refresh policy with RangeStart and RangeEnd parameters
  4. Use CALCULATE with an appropriate FILTER table expression
  5. Optimize the model toward a clear star schema and efficient relationships

Correct answer: B

Why: Large semantic model storage format is designed for supported capacities and models that need to exceed standard size limits. This directly matches the stated requirement.

Option review:

A: Variables can reduce repeated evaluation and also make the measure easier to optimize. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

B: Large semantic model storage format is designed for supported capacities and models that need to exceed standard size limits. This directly matches the stated requirement.

C: Incremental refresh partitions the table so scheduled refresh can process only the required recent range instead of reloading all history. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

D: FILTER can construct the row set while CALCULATE evaluates the measure under the resulting filter context. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

E: A well-designed star schema reduces relationship complexity and helps the engine resolve filters efficiently. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

Learning point: Enable large semantic model storage format for the model

Question 76

During a design review for Wide World Importers’s marketing semantic model, one requirement is non-negotiable: prepare a large enterprise model for advanced XMLA management and large-volume storage on supported capacity. Because the implementation should reduce operational overhead, what should the BI platform team implement? The team will validate the change first in a nonproduction environment.

  1. Use incremental refresh and define a shorter refresh window than the historical retention window
  2. Choose Direct Lake on the SQL analytics endpoint
  3. Introduce a bridge table at the customer-segment membership grain
  4. Create a composite model over the remote semantic model and the local data
  5. Configure the semantic model to use large semantic model storage format

Correct answer: E

Why: The large storage format supports enterprise-scale models and related management operations on supported capacity. This directly matches the stated requirement.

Option review:

A: The policy can retain a long history while refreshing only the recent period that is still subject to change. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

B: Direct Lake on SQL is the choice when the model must depend on supported SQL analytics endpoint security semantics. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

C: A bridge table resolves a many-to-many business relationship into controlled one-to-many relationships for filtering and measures. This can be valid for ‘Implement relationships, such as bridge tables and many-to-many relationships’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

D: Composite models can extend a remote semantic model with additional local model objects when supported. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

E: The large storage format supports enterprise-scale models and related management operations on supported capacity. This directly matches the stated requirement.

Learning point: Configure the semantic model to use large semantic model storage format

Question 77

The security analytics team at Northwind Traders is preparing the next release of its supply-chain lakehouse. They need to support a semantic model that is expected to grow beyond standard model-size limits on supported capacity; the solution must remain maintainable as usage grows. Which choice most directly satisfies the requirement? The solution must work with the current Fabric architecture rather than a parallel custom platform.

  1. Create both relationships and use an inactive relationship for the secondary date when appropriate
  2. Check whether the query is falling back to DirectQuery and remove the condition that triggers fallback
  3. Enable large semantic model storage format for the model
  4. Use the appropriate DAX window function with an explicit ordering definition
  5. Use DirectQuery storage mode

Correct answer: C

Why: Large semantic model storage format is designed for supported capacities and models that need to exceed standard size limits. This directly matches the stated requirement.

Option review:

A: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This can be valid for ‘Implement relationships, such as bridge tables and many-to-many relationships’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

B: Direct Lake on SQL can fall back to DirectQuery for unsupported scenarios, which can materially change query performance. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

C: Large semantic model storage format is designed for supported capacities and models that need to exceed standard size limits. This directly matches the stated requirement.

D: DAX window functions support ordered row-window calculations without manually reconstructing the entire sequence logic. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

E: DirectQuery leaves data in the source and sends queries at report time, trading source dependency for fresher access without a full import. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

Learning point: Enable large semantic model storage format for the model

Question 78

A production readiness review at Trey Research found a gap in the IoT telemetry solution. The remediation must prepare a large enterprise model for advanced XMLA management and large-volume storage on supported capacity, and the team wants the smallest administrative blast radius. What is the most appropriate action? The solution must work with the current Fabric architecture rather than a parallel custom platform.

  1. Use a supported composite model with Direct Lake on OneLake plus Import
  2. Use Power BI Performance Analyzer to capture and compare visual query durations
  3. Check whether the query is falling back to DirectQuery and remove the condition that triggers fallback
  4. Configure the semantic model to use large semantic model storage format
  5. Use the appropriate DAX window function with an explicit ordering definition

Correct answer: D

Why: The large storage format supports enterprise-scale models and related management operations on supported capacity. This directly matches the stated requirement.

Option review:

A: Direct Lake on OneLake supports composite modeling with other compatible storage modes in supported scenarios. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

B: Performance Analyzer provides per-visual timing information that helps isolate slow visuals and DAX queries. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

C: Direct Lake on SQL can fall back to DirectQuery for unsupported scenarios, which can materially change query performance. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

D: The large storage format supports enterprise-scale models and related management operations on supported capacity. This directly matches the stated requirement.

E: DAX window functions support ordered row-window calculations without manually reconstructing the entire sequence logic. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

Learning point: Configure the semantic model to use large semantic model storage format

Question 79

For a new phase of the finance reporting platform, Alpine Ski House asks the customer insights team to support a semantic model that is expected to grow beyond standard model-size limits on supported capacity. The architecture decision record also states that the team wants to keep governance centralized. Which approach should be selected? The design decision will be reviewed by both data engineering and BI owners.

  1. Enable large semantic model storage format for the model
  2. Use DAX Studio or equivalent server-timing diagnostics to profile the measure
  3. Use Import storage mode
  4. Create both relationships and use an inactive relationship for the secondary date when appropriate
  5. Optimize the model toward a clear star schema and efficient relationships

Correct answer: A

Why: Large semantic model storage format is designed for supported capacities and models that need to exceed standard size limits. This directly matches the stated requirement.

Option review:

A: Large semantic model storage format is designed for supported capacities and models that need to exceed standard size limits. This directly matches the stated requirement.

B: Server timings and query plans help identify whether a DAX expression is spending time in formula-engine iteration or storage-engine scans. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

C: Import loads data into the VertiPaq in-memory engine and generally provides the fastest query performance when refresh latency is acceptable. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

D: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This can be valid for ‘Implement relationships, such as bridge tables and many-to-many relationships’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

E: A well-designed star schema reduces relationship complexity and helps the engine resolve filters efficiently. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

Learning point: Enable large semantic model storage format for the model

Question 80

Contoso is standardizing how the retail performance dashboard is managed. The immediate goal is to prepare a large enterprise model for advanced XMLA management and large-volume storage on supported capacity. Given that the approach should remain understandable to future maintainers, which option should the retail insights team choose? The design decision will be reviewed by both data engineering and BI owners.

  1. Create a field parameter
  2. Use the appropriate DAX window function with an explicit ordering definition
  3. Choose Direct Lake on the SQL analytics endpoint
  4. Configure the semantic model to use large semantic model storage format
  5. Model a fact table surrounded by dimension tables with clear one-to-many relationships

Correct answer: D

Why: The large storage format supports enterprise-scale models and related management operations on supported capacity. This directly matches the stated requirement.

Option review:

A: Field parameters let consumers dynamically choose which modeled fields a visual uses. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

B: DAX window functions support ordered row-window calculations without manually reconstructing the entire sequence logic. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

C: Direct Lake on SQL uses the SQL analytics endpoint for metadata and can fall back to DirectQuery in supported scenarios. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

D: The large storage format supports enterprise-scale models and related management operations on supported capacity. This directly matches the stated requirement.

E: A star schema gives the semantic model a predictable analytical structure and simplifies filter propagation. This can be valid for ‘Implement a star schema for a semantic model’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

Learning point: Configure the semantic model to use large semantic model storage format

Question 81

An internal audit of Wingtip Toys’s marketing semantic model identifies this requirement: support a semantic model that is expected to grow beyond standard model-size limits on supported capacity. The BI platform team also notes that the implementation should reduce operational overhead. What should they do? Existing users should keep their current access.

  1. Use DAX Studio or equivalent server-timing diagnostics to profile the measure
  2. Use Dual storage mode for the compatible dimension
  3. Use a supported composite model with Direct Lake on OneLake plus Import
  4. Reduce unnecessary visuals or interactions and lower the amount of data each visual requests
  5. Enable large semantic model storage format for the model

Correct answer: E

Why: Large semantic model storage format is designed for supported capacities and models that need to exceed standard size limits. This directly matches the stated requirement.

Option review:

A: Server timings and query plans help identify whether a DAX expression is spending time in formula-engine iteration or storage-engine scans. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

B: Dual can act as Import or DirectQuery depending on the query path and can improve composite-model dimension behavior. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

C: Direct Lake on OneLake supports composite modeling with other compatible storage modes in supported scenarios. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

D: Fewer, more focused visual queries reduce rendering and query workload, especially on high-cardinality pages. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

E: Large semantic model storage format is designed for supported capacities and models that need to exceed standard size limits. This directly matches the stated requirement.

Learning point: Enable large semantic model storage format for the model

Question 82

The supply-chain lakehouse at Proseware is moving from proof of concept to production. Before rollout, the security analytics team must prepare a large enterprise model for advanced XMLA management and large-volume storage on supported capacity, while ensuring that the solution must remain maintainable as usage grows. Which action best meets both needs? Existing users should keep their current access.

  1. Apply the RangeStart and RangeEnd filters in a foldable transformation
  2. Create a calculation group
  3. Check whether the query is falling back to DirectQuery and remove the condition that triggers fallback
  4. Create a field parameter
  5. Configure the semantic model to use large semantic model storage format

Correct answer: E

Why: The large storage format supports enterprise-scale models and related management operations on supported capacity. This directly matches the stated requirement.

Option review:

A: Query folding lets the source execute the partition predicates efficiently, which is important for scalable incremental refresh. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

B: Calculation groups centralize reusable calculation logic and reduce measure proliferation. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

C: Direct Lake on SQL can fall back to DirectQuery for unsupported scenarios, which can materially change query performance. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

D: Field parameters let consumers dynamically choose which modeled fields a visual uses. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

E: The large storage format supports enterprise-scale models and related management operations on supported capacity. This directly matches the stated requirement.

Learning point: Configure the semantic model to use large semantic model storage format

Question 83

Blue Yonder Airlines has a change request for the IoT telemetry solution: support a semantic model that is expected to grow beyond standard model-size limits on supported capacity. The Fabric center of excellence wants a solution where the team wants the smallest administrative blast radius. Which implementation is most suitable? No unrelated workspace or model permissions should be changed.

  1. Use CALCULATE with an appropriate FILTER table expression
  2. Use an iterator such as SUMX over the required table expression
  3. Use a supported composite model with Direct Lake on OneLake plus Import
  4. Compute the expression once in a DAX variable and reuse it
  5. Enable large semantic model storage format for the model

Correct answer: E

Why: Large semantic model storage format is designed for supported capacities and models that need to exceed standard size limits. This directly matches the stated requirement.

Option review:

A: FILTER can construct the row set while CALCULATE evaluates the measure under the resulting filter context. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

B: Iterator functions evaluate an expression for each row and then aggregate the results. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

C: Direct Lake on OneLake supports composite modeling with other compatible storage modes in supported scenarios. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

D: Variables can reduce repeated evaluation and also make the measure easier to optimize. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

E: Large semantic model storage format is designed for supported capacities and models that need to exceed standard size limits. This directly matches the stated requirement.

Learning point: Enable large semantic model storage format for the model

Question 84

A solution architect reviewing Fabrikam’s finance reporting platform asks the customer insights team to prepare a large enterprise model for advanced XMLA management and large-volume storage on supported capacity. Since the team wants to keep governance centralized, which recommendation is strongest? No unrelated workspace or model permissions should be changed.

  1. Create a field parameter
  2. Create both relationships and use an inactive relationship for the secondary date when appropriate
  3. Optimize the model toward a clear star schema and efficient relationships
  4. Configure the semantic model to use large semantic model storage format
  5. Use a supported composite model with Direct Lake on OneLake plus Import

Correct answer: D

Why: The large storage format supports enterprise-scale models and related management operations on supported capacity. This directly matches the stated requirement.

Option review:

A: Field parameters let consumers dynamically choose which modeled fields a visual uses. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

B: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This can be valid for ‘Implement relationships, such as bridge tables and many-to-many relationships’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

C: A well-designed star schema reduces relationship complexity and helps the engine resolve filters efficiently. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

D: The large storage format supports enterprise-scale models and related management operations on supported capacity. This directly matches the stated requirement.

E: Direct Lake on OneLake supports composite modeling with other compatible storage modes in supported scenarios. This can be valid for ‘Design and build composite models’, but it does not directly satisfy the scenario requirement being tested under ‘Identify use cases for and configure large semantic model storage format’.

Learning point: Configure the semantic model to use large semantic model storage format

Question 85

Tailspin Toys is troubleshooting a design decision in the supply-chain lakehouse. The desired end state is to combine a fast imported historical table with a DirectQuery table that must remain near real time; the solution should avoid unnecessary custom code. Which change should the BI platform team make? Existing users should keep their current access.

  1. Choose Direct Lake on OneLake
  2. Store the intermediate expression in a DAX VAR and reference the variable
  3. Use DAX Studio or equivalent server-timing diagnostics to profile the measure
  4. Build a composite model that uses the appropriate storage mode for each table
  5. Use Dual storage mode for the compatible dimension

Correct answer: D

Why: Composite models can combine tables that use different storage modes so each part of the model matches its latency and performance needs. This directly matches the stated requirement.

Option review:

A: Direct Lake on OneLake uses OneLake directly and operates without DirectQuery fallback. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

B: Variables reduce repeated expressions and make complex DAX easier to read and maintain. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

C: Server timings and query plans help identify whether a DAX expression is spending time in formula-engine iteration or storage-engine scans. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

D: Composite models can combine tables that use different storage modes so each part of the model matches its latency and performance needs. This directly matches the stated requirement.

E: Dual can act as Import or DirectQuery depending on the query path and can improve composite-model dimension behavior. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

Learning point: Build a composite model that uses the appropriate storage mode for each table

Question 86

For the IoT telemetry solution, Fourth Coffee has documented a business requirement to extend an existing governed semantic model with a small local table and additional model logic. The security analytics team must meet it in a way where the design must preserve a clear development lifecycle. What is the best choice? Existing users should keep their current access.

  1. Use DirectQuery storage mode
  2. Store the intermediate expression in a DAX VAR and reference the variable
  3. Use an iterator such as SUMX over the required table expression
  4. Use direct column filters or more efficient set-based DAX where semantics allow
  5. Create a composite model over the remote semantic model and the local data

Correct answer: E

Why: Composite models can extend a remote semantic model with additional local model objects when supported. This directly matches the stated requirement.

Option review:

A: DirectQuery leaves data in the source and sends queries at report time, trading source dependency for fresher access without a full import. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

B: Variables reduce repeated expressions and make complex DAX easier to read and maintain. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

C: Iterator functions evaluate an expression for each row and then aggregate the results. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

D: Avoiding expensive iterator patterns over large tables can reduce formula-engine work and improve query performance. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

E: Composite models can extend a remote semantic model with additional local model objects when supported. This directly matches the stated requirement.

Learning point: Create a composite model over the remote semantic model and the local data

Question 87

A governance review of Wide World Importers’s finance reporting platform asks for evidence that the solution can combine Direct Lake on OneLake tables with a small imported helper table in the same model. Because the team must avoid granting broader access than required, which action should be approved? Existing users should keep their current access.

  1. Use Import storage mode
  2. Use a supported composite model with Direct Lake on OneLake plus Import
  3. Use DirectQuery storage mode
  4. Store the intermediate expression in a DAX VAR and reference the variable
  5. Choose Direct Lake on OneLake

Correct answer: B

Why: Direct Lake on OneLake supports composite modeling with other compatible storage modes in supported scenarios. This directly matches the stated requirement.

Option review:

A: Import loads data into the VertiPaq in-memory engine and generally provides the fastest query performance when refresh latency is acceptable. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

B: Direct Lake on OneLake supports composite modeling with other compatible storage modes in supported scenarios. This directly matches the stated requirement.

C: DirectQuery leaves data in the source and sends queries at report time, trading source dependency for fresher access without a full import. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

D: Variables reduce repeated expressions and make complex DAX easier to read and maintain. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

E: Direct Lake on OneLake uses OneLake directly and operates without DirectQuery fallback. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

Learning point: Use a supported composite model with Direct Lake on OneLake plus Import

Question 88

Before expanding the retail performance dashboard, the customer insights team at Northwind Traders must combine a fast imported historical table with a DirectQuery table that must remain near real time. The rollout plan says that the change must be easy to audit later. Which option most directly addresses the requirement? No unrelated workspace or model permissions should be changed.

  1. Configure an incremental refresh policy with RangeStart and RangeEnd parameters
  2. Create both relationships and use an inactive relationship for the secondary date when appropriate
  3. Use Direct Lake storage mode
  4. Use the appropriate DAX window function with an explicit ordering definition
  5. Build a composite model that uses the appropriate storage mode for each table

Correct answer: E

Why: Composite models can combine tables that use different storage modes so each part of the model matches its latency and performance needs. This directly matches the stated requirement.

Option review:

A: Incremental refresh partitions the table so scheduled refresh can process only the required recent range instead of reloading all history. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

B: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This can be valid for ‘Implement relationships, such as bridge tables and many-to-many relationships’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

C: Direct Lake reads OneLake-backed Delta data for semantic-model queries without a conventional import copy. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

D: DAX window functions support ordered row-window calculations without manually reconstructing the entire sequence logic. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

E: Composite models can combine tables that use different storage modes so each part of the model matches its latency and performance needs. This directly matches the stated requirement.

Learning point: Build a composite model that uses the appropriate storage mode for each table

Question 89

Trey Research is redesigning its marketing semantic model. The retail insights team must extend an existing governed semantic model with a small local table and additional model logic. In addition, the implementation should be easy to troubleshoot. Which action is the best fit? No unrelated workspace or model permissions should be changed.

  1. Model a fact table surrounded by dimension tables with clear one-to-many relationships
  2. Use the supported Direct Lake refresh or framing operation
  3. Use Direct Lake storage mode
  4. Store the intermediate expression in a DAX VAR and reference the variable
  5. Create a composite model over the remote semantic model and the local data

Correct answer: E

Why: Composite models can extend a remote semantic model with additional local model objects when supported. This directly matches the stated requirement.

Option review:

A: A star schema gives the semantic model a predictable analytical structure and simplifies filter propagation. This can be valid for ‘Implement a star schema for a semantic model’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

B: Direct Lake refresh or framing updates the model view of OneLake data rather than loading a conventional imported copy. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

C: Direct Lake reads OneLake-backed Delta data for semantic-model queries without a conventional import copy. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

D: Variables reduce repeated expressions and make complex DAX easier to read and maintain. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

E: Composite models can extend a remote semantic model with additional local model objects when supported. This directly matches the stated requirement.

Learning point: Create a composite model over the remote semantic model and the local data

Question 90

During a design review for Alpine Ski House’s supply-chain lakehouse, one requirement is non-negotiable: combine Direct Lake on OneLake tables with a small imported helper table in the same model. Because the solution should avoid unnecessary custom code, what should the BI platform team implement? No unrelated workspace or model permissions should be changed.

  1. Use a supported composite model with Direct Lake on OneLake plus Import
  2. Use direct column filters or more efficient set-based DAX where semantics allow
  3. Create both relationships and use an inactive relationship for the secondary date when appropriate
  4. Configure an incremental refresh policy with RangeStart and RangeEnd parameters
  5. Choose Direct Lake on the SQL analytics endpoint

Correct answer: A

Why: Direct Lake on OneLake supports composite modeling with other compatible storage modes in supported scenarios. This directly matches the stated requirement.

Option review:

A: Direct Lake on OneLake supports composite modeling with other compatible storage modes in supported scenarios. This directly matches the stated requirement.

B: Avoiding expensive iterator patterns over large tables can reduce formula-engine work and improve query performance. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

C: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This can be valid for ‘Implement relationships, such as bridge tables and many-to-many relationships’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

D: Incremental refresh partitions the table so scheduled refresh can process only the required recent range instead of reloading all history. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

E: Direct Lake on SQL is the choice when the model must depend on supported SQL analytics endpoint security semantics. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

Learning point: Use a supported composite model with Direct Lake on OneLake plus Import

Question 91

The security analytics team at Contoso is preparing the next release of its IoT telemetry solution. They need to combine a fast imported historical table with a DirectQuery table that must remain near real time; the design must preserve a clear development lifecycle. Which choice most directly satisfies the requirement? The team will validate the change first in a nonproduction environment.

  1. Create a calculation group
  2. Build a composite model that uses the appropriate storage mode for each table
  3. Use DirectQuery storage mode
  4. Choose Direct Lake on OneLake
  5. Use the appropriate DAX window function with an explicit ordering definition

Correct answer: B

Why: Composite models can combine tables that use different storage modes so each part of the model matches its latency and performance needs. This directly matches the stated requirement.

Option review:

A: Calculation groups centralize reusable calculation logic and reduce measure proliferation. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

B: Composite models can combine tables that use different storage modes so each part of the model matches its latency and performance needs. This directly matches the stated requirement.

C: DirectQuery leaves data in the source and sends queries at report time, trading source dependency for fresher access without a full import. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

D: Direct Lake on OneLake uses OneLake directly and operates without DirectQuery fallback. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

E: DAX window functions support ordered row-window calculations without manually reconstructing the entire sequence logic. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

Learning point: Build a composite model that uses the appropriate storage mode for each table

Question 92

A production readiness review at Wingtip Toys found a gap in the finance reporting platform. The remediation must extend an existing governed semantic model with a small local table and additional model logic, and the team must avoid granting broader access than required. What is the most appropriate action? The team will validate the change first in a nonproduction environment.

  1. Use Dual storage mode for the compatible dimension
  2. Reduce unnecessary visuals or interactions and lower the amount of data each visual requests
  3. Use DAX Studio or equivalent server-timing diagnostics to profile the measure
  4. Create a composite model over the remote semantic model and the local data
  5. Use CALCULATE with an appropriate FILTER table expression

Correct answer: D

Why: Composite models can extend a remote semantic model with additional local model objects when supported. This directly matches the stated requirement.

Option review:

A: Dual can act as Import or DirectQuery depending on the query path and can improve composite-model dimension behavior. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

B: Fewer, more focused visual queries reduce rendering and query workload, especially on high-cardinality pages. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

C: Server timings and query plans help identify whether a DAX expression is spending time in formula-engine iteration or storage-engine scans. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

D: Composite models can extend a remote semantic model with additional local model objects when supported. This directly matches the stated requirement.

E: FILTER can construct the row set while CALCULATE evaluates the measure under the resulting filter context. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

Learning point: Create a composite model over the remote semantic model and the local data

Question 93

For a new phase of the retail performance dashboard, Proseware asks the customer insights team to combine Direct Lake on OneLake tables with a small imported helper table in the same model. The architecture decision record also states that the change must be easy to audit later. Which approach should be selected? The team will validate the change first in a nonproduction environment.

  1. Use a supported composite model with Direct Lake on OneLake plus Import
  2. Choose Direct Lake on OneLake
  3. Create both relationships and use an inactive relationship for the secondary date when appropriate
  4. Use Dual storage mode for the compatible dimension
  5. Use CALCULATE with an appropriate FILTER table expression

Correct answer: A

Why: Direct Lake on OneLake supports composite modeling with other compatible storage modes in supported scenarios. This directly matches the stated requirement.

Option review:

A: Direct Lake on OneLake supports composite modeling with other compatible storage modes in supported scenarios. This directly matches the stated requirement.

B: Direct Lake on OneLake uses OneLake directly and operates without DirectQuery fallback. This can be valid for ‘Choose between Direct Lake on OneLake and Direct Lake on SQL analytics endpoint’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

C: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This can be valid for ‘Implement relationships, such as bridge tables and many-to-many relationships’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

D: Dual can act as Import or DirectQuery depending on the query path and can improve composite-model dimension behavior. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

E: FILTER can construct the row set while CALCULATE evaluates the measure under the resulting filter context. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

Learning point: Use a supported composite model with Direct Lake on OneLake plus Import

Question 94

Blue Yonder Airlines is standardizing how the marketing semantic model is managed. The immediate goal is to combine a fast imported historical table with a DirectQuery table that must remain near real time. Given that the implementation should be easy to troubleshoot, which option should the retail insights team choose? The solution must work with the current Fabric architecture rather than a parallel custom platform.

  1. Store the intermediate expression in a DAX VAR and reference the variable
  2. Build a composite model that uses the appropriate storage mode for each table
  3. Introduce a bridge table at the customer-segment membership grain
  4. Use a dynamic format string
  5. Use Power BI Performance Analyzer to capture and compare visual query durations

Correct answer: B

Why: Composite models can combine tables that use different storage modes so each part of the model matches its latency and performance needs. This directly matches the stated requirement.

Option review:

A: Variables reduce repeated expressions and make complex DAX easier to read and maintain. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

B: Composite models can combine tables that use different storage modes so each part of the model matches its latency and performance needs. This directly matches the stated requirement.

C: A bridge table resolves a many-to-many business relationship into controlled one-to-many relationships for filtering and measures. This can be valid for ‘Implement relationships, such as bridge tables and many-to-many relationships’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

D: Dynamic format strings change presentation without converting the measure result to text. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

E: Performance Analyzer provides per-visual timing information that helps isolate slow visuals and DAX queries. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

Learning point: Build a composite model that uses the appropriate storage mode for each table

Question 95

An internal audit of Fabrikam’s supply-chain lakehouse identifies this requirement: extend an existing governed semantic model with a small local table and additional model logic. The BI platform team also notes that the solution should avoid unnecessary custom code. What should they do? The solution must work with the current Fabric architecture rather than a parallel custom platform.

  1. Use incremental refresh and define a shorter refresh window than the historical retention window
  2. Configure the semantic model to use large semantic model storage format
  3. Configure the model for DirectLakeOnly behavior where supported
  4. Compute the expression once in a DAX variable and reuse it
  5. Create a composite model over the remote semantic model and the local data

Correct answer: E

Why: Composite models can extend a remote semantic model with additional local model objects when supported. This directly matches the stated requirement.

Option review:

A: The policy can retain a long history while refreshing only the recent period that is still subject to change. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

B: The large storage format supports enterprise-scale models and related management operations on supported capacity. This can be valid for ‘Identify use cases for and configure large semantic model storage format’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

C: DirectLakeOnly prevents DirectQuery fallback, causing unsupported queries to fail instead of silently using DirectQuery. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

D: Variables can reduce repeated evaluation and also make the measure easier to optimize. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

E: Composite models can extend a remote semantic model with additional local model objects when supported. This directly matches the stated requirement.

Learning point: Create a composite model over the remote semantic model and the local data

Question 96

The IoT telemetry solution at Litware is moving from proof of concept to production. Before rollout, the security analytics team must combine Direct Lake on OneLake tables with a small imported helper table in the same model, while ensuring that the design must preserve a clear development lifecycle. Which action best meets both needs? The solution must work with the current Fabric architecture rather than a parallel custom platform.

  1. Optimize the model toward a clear star schema and efficient relationships
  2. Use a dynamic format string
  3. Check whether the query is falling back to DirectQuery and remove the condition that triggers fallback
  4. Use a supported composite model with Direct Lake on OneLake plus Import
  5. Compute the expression once in a DAX variable and reuse it

Correct answer: D

Why: Direct Lake on OneLake supports composite modeling with other compatible storage modes in supported scenarios. This directly matches the stated requirement.

Option review:

A: A well-designed star schema reduces relationship complexity and helps the engine resolve filters efficiently. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

B: Dynamic format strings change presentation without converting the measure result to text. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

C: Direct Lake on SQL can fall back to DirectQuery for unsupported scenarios, which can materially change query performance. This can be valid for ‘Configure Direct Lake, including default fallback and refresh behavior’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

D: Direct Lake on OneLake supports composite modeling with other compatible storage modes in supported scenarios. This directly matches the stated requirement.

E: Variables can reduce repeated evaluation and also make the measure easier to optimize. This can be valid for ‘Improve DAX performance’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

Learning point: Use a supported composite model with Direct Lake on OneLake plus Import

Question 97

Woodgrove Bank has a change request for the finance reporting platform: combine a fast imported historical table with a DirectQuery table that must remain near real time. The Fabric center of excellence wants a solution where the team must avoid granting broader access than required. Which implementation is most suitable? The design decision will be reviewed by both data engineering and BI owners.

  1. Create a calculation group
  2. Use CALCULATE with an appropriate FILTER table expression
  3. Build a composite model that uses the appropriate storage mode for each table
  4. Configure an incremental refresh policy with RangeStart and RangeEnd parameters
  5. Use Power BI Performance Analyzer to capture and compare visual query durations

Correct answer: C

Why: Composite models can combine tables that use different storage modes so each part of the model matches its latency and performance needs. This directly matches the stated requirement.

Option review:

A: Calculation groups centralize reusable calculation logic and reduce measure proliferation. This can be valid for ‘Implement calculation groups, dynamic format strings, and field parameters’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

B: FILTER can construct the row set while CALCULATE evaluates the measure under the resulting filter context. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

C: Composite models can combine tables that use different storage modes so each part of the model matches its latency and performance needs. This directly matches the stated requirement.

D: Incremental refresh partitions the table so scheduled refresh can process only the required recent range instead of reloading all history. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

E: Performance Analyzer provides per-visual timing information that helps isolate slow visuals and DAX queries. This can be valid for ‘Implement performance improvements in queries and report visuals’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

Learning point: Build a composite model that uses the appropriate storage mode for each table

Question 98

A solution architect reviewing Coho Winery’s retail performance dashboard asks the customer insights team to extend an existing governed semantic model with a small local table and additional model logic. Since the change must be easy to audit later, which recommendation is strongest? The design decision will be reviewed by both data engineering and BI owners.

  1. Create a composite model over the remote semantic model and the local data
  2. Use an iterator such as SUMX over the required table expression
  3. Configure an incremental refresh policy with RangeStart and RangeEnd parameters
  4. Use Import storage mode
  5. Create both relationships and use an inactive relationship for the secondary date when appropriate

Correct answer: A

Why: Composite models can extend a remote semantic model with additional local model objects when supported. This directly matches the stated requirement.

Option review:

A: Composite models can extend a remote semantic model with additional local model objects when supported. This directly matches the stated requirement.

B: Iterator functions evaluate an expression for each row and then aggregate the results. This can be valid for ‘Write calculations that use DAX variables and functions, such as iterators, table filtering, windowing, and information functions’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

C: Incremental refresh partitions the table so scheduled refresh can process only the required recent range instead of reloading all history. This can be valid for ‘Implement incremental refresh for semantic models’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

D: Import loads data into the VertiPaq in-memory engine and generally provides the fastest query performance when refresh latency is acceptable. This can be valid for ‘Choose a storage mode’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

E: Role-playing date scenarios commonly use one active relationship and an inactive relationship activated explicitly in DAX when needed. This can be valid for ‘Implement relationships, such as bridge tables and many-to-many relationships’, but it does not directly satisfy the scenario requirement being tested under ‘Design and build composite models’.

Learning point: Create a composite model over the remote semantic model and the local data

img