Microsoft PL-300 Calculated Tables Calculated Columns And Calculation Groups Practice Test

 

Skills 2.2 • 25 original questions

This Microsoft PL-300 Power BI Data Analyst practice test focuses on calculated tables calculated columns and calculation groups through original scenario-based questions aligned to the skills measured as of April 20, 2026. Use the full ExamSnap PL-300 collection for broader practice across all current skill areas. For broader exam preparation, review the Microsoft PL-300 Exam Dumps page.

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

Question 1

During a executive reporting rollout at Fourth Coffee, the data analyst must materialize a DAX-derived table or row-level value in the semantic model. Which action most directly satisfies the requirement for the executive report, analysis cycle 1?

  1. Use basic statistical DAX functions to calculate values such as median, percentile, variance, or standard deviation when required
  2. Use CALCULATE to evaluate an expression under modified filter context
  3. Create a DAX calculated table or calculated column when the result must be materialized during model refresh
  4. Create an explicit measure for a single aggregation such as SUM, COUNT, AVERAGE, MIN, or MAX
  5. Build time-intelligence measures against a suitable date table

Correct answer: C

Why: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. This directly addresses the stated requirement: materialize a DAX-derived table or row-level value in the semantic model.

Option review:

A: DAX includes statistical functions that summarize distributions beyond simple totals and averages. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

B: CALCULATE changes the filter context for an expression and is central to many DAX business calculations. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

C: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. This directly addresses the stated requirement: materialize a DAX-derived table or row-level value in the semantic model.

D: Measures calculate at query time in the current filter context and are the normal way to define reusable business aggregations. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

E: Time-intelligence patterns compare or aggregate values across periods such as prior year, year to date, or rolling windows. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

Learning point: Create a DAX calculated table or calculated column when the result must be materialized during model refresh

Question 2

Fabrikam Manufacturing is revising its analytics solution during a sales analytics project. The team needs to reduce many repetitive measure variants by applying reusable calculation logic to existing measures. Which Power BI action should the report author choose for the sales model, analysis cycle 1?

  1. Use Quick measures to generate a supported calculation pattern and inspect or adapt the resulting DAX
  2. Create a DAX calculated table or calculated column when the result must be materialized during model refresh
  3. Create an explicit measure for a single aggregation such as SUM, COUNT, AVERAGE, MIN, or MAX
  4. Build time-intelligence measures against a suitable date table
  5. Create a calculation group to apply reusable calculation items to existing explicit measures

Correct answer: E

Why: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. This directly addresses the stated requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

Option review:

A: Quick measures create DAX for common analytical patterns and can accelerate authoring when the built-in pattern matches the need. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

B: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

C: Measures calculate at query time in the current filter context and are the normal way to define reusable business aggregations. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

D: Time-intelligence patterns compare or aggregate values across periods such as prior year, year to date, or rolling windows. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

E: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. This directly addresses the stated requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

Learning point: Create a calculation group to apply reusable calculation items to existing explicit measures

Question 3

A design review for the finance semantic model, analysis cycle 2 at Adventure Works identifies one required capability: materialize a DAX-derived table or row-level value in the semantic model. Which implementation is the strongest fit?

  1. Use Quick measures to generate a supported calculation pattern and inspect or adapt the resulting DAX
  2. Build time-intelligence measures against a suitable date table
  3. Create a DAX calculated table or calculated column when the result must be materialized during model refresh
  4. Create a calculation group to apply reusable calculation items to existing explicit measures
  5. Create a semi-additive measure that aggregates differently across time than across other dimensions

Correct answer: C

Why: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. This directly addresses the stated requirement: materialize a DAX-derived table or row-level value in the semantic model.

Option review:

A: Quick measures create DAX for common analytical patterns and can accelerate authoring when the built-in pattern matches the need. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

B: Time-intelligence patterns compare or aggregate values across periods such as prior year, year to date, or rolling windows. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

C: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. This directly addresses the stated requirement: materialize a DAX-derived table or row-level value in the semantic model.

D: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

E: Balances and snapshots often add across entities but require last-value, first-value, or another special rule across dates. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

Learning point: Create a DAX calculated table or calculated column when the result must be materialized during model refresh

Question 4

For the operations dashboard, analysis cycle 2, Proseware Services wants the least indirect way to reduce many repetitive measure variants by applying reusable calculation logic to existing measures. Which Power BI feature or action should the BI developer select?

  1. Create a semi-additive measure that aggregates differently across time than across other dimensions
  2. Use Quick measures to generate a supported calculation pattern and inspect or adapt the resulting DAX
  3. Create an explicit measure for a single aggregation such as SUM, COUNT, AVERAGE, MIN, or MAX
  4. Create a calculation group to apply reusable calculation items to existing explicit measures
  5. Create a DAX calculated table or calculated column when the result must be materialized during model refresh

Correct answer: D

Why: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. This directly addresses the stated requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

Option review:

A: Balances and snapshots often add across entities but require last-value, first-value, or another special rule across dates. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

B: Quick measures create DAX for common analytical patterns and can accelerate authoring when the built-in pattern matches the need. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

C: Measures calculate at query time in the current filter context and are the normal way to define reusable business aggregations. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

D: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. This directly addresses the stated requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

E: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

Learning point: Create a calculation group to apply reusable calculation items to existing explicit measures

Question 5

The Power BI data analyst at Fourth Coffee is comparing several approaches for a regional reporting consolidation. The chosen approach must materialize a DAX-derived table or row-level value in the semantic model. Which option best meets that condition?

  1. Create a semi-additive measure that aggregates differently across time than across other dimensions
  2. Create a calculation group to apply reusable calculation items to existing explicit measures
  3. Create a DAX calculated table or calculated column when the result must be materialized during model refresh
  4. Use CALCULATE to evaluate an expression under modified filter context
  5. Create an explicit measure for a single aggregation such as SUM, COUNT, AVERAGE, MIN, or MAX

Correct answer: C

Why: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. This directly addresses the stated requirement: materialize a DAX-derived table or row-level value in the semantic model.

Option review:

A: Balances and snapshots often add across entities but require last-value, first-value, or another special rule across dates. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

B: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

C: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. This directly addresses the stated requirement: materialize a DAX-derived table or row-level value in the semantic model.

D: CALCULATE changes the filter context for an expression and is central to many DAX business calculations. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

E: Measures calculate at query time in the current filter context and are the normal way to define reusable business aggregations. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

Learning point: Create a DAX calculated table or calculated column when the result must be materialized during model refresh

Question 6

A support escalation at Fabrikam Manufacturing has been narrowed to one requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures. Which configuration should be investigated first for the regional workspace, analysis cycle 3?

  1. Use basic statistical DAX functions to calculate values such as median, percentile, variance, or standard deviation when required
  2. Use Quick measures to generate a supported calculation pattern and inspect or adapt the resulting DAX
  3. Create a DAX calculated table or calculated column when the result must be materialized during model refresh
  4. Use CALCULATE to evaluate an expression under modified filter context
  5. Create a calculation group to apply reusable calculation items to existing explicit measures

Correct answer: E

Why: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. This directly addresses the stated requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

Option review:

A: DAX includes statistical functions that summarize distributions beyond simple totals and averages. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

B: Quick measures create DAX for common analytical patterns and can accelerate authoring when the built-in pattern matches the need. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

C: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

D: CALCULATE changes the filter context for an expression and is central to many DAX business calculations. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

E: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. This directly addresses the stated requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

Learning point: Create a calculation group to apply reusable calculation items to existing explicit measures

Question 7

An analytics governance review at Adventure Works asks the data analyst to materialize a DAX-derived table or row-level value in the semantic model. Which action aligns most directly with that requirement?

  1. Create a calculation group to apply reusable calculation items to existing explicit measures
  2. Create a DAX calculated table or calculated column when the result must be materialized during model refresh
  3. Create an explicit measure for a single aggregation such as SUM, COUNT, AVERAGE, MIN, or MAX
  4. Use Quick measures to generate a supported calculation pattern and inspect or adapt the resulting DAX
  5. Use CALCULATE to evaluate an expression under modified filter context

Correct answer: B

Why: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. This directly addresses the stated requirement: materialize a DAX-derived table or row-level value in the semantic model.

Option review:

A: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

B: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. This directly addresses the stated requirement: materialize a DAX-derived table or row-level value in the semantic model.

C: Measures calculate at query time in the current filter context and are the normal way to define reusable business aggregations. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

D: Quick measures create DAX for common analytical patterns and can accelerate authoring when the built-in pattern matches the need. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

E: CALCULATE changes the filter context for an expression and is central to many DAX business calculations. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

Learning point: Create a DAX calculated table or calculated column when the result must be materialized during model refresh

Question 8

Before the service-level dashboard, analysis cycle 4 is released, the analytics team must reduce many repetitive measure variants by applying reusable calculation logic to existing measures. Which Power BI implementation should be added?

  1. Create a semi-additive measure that aggregates differently across time than across other dimensions
  2. Create an explicit measure for a single aggregation such as SUM, COUNT, AVERAGE, MIN, or MAX
  3. Use basic statistical DAX functions to calculate values such as median, percentile, variance, or standard deviation when required
  4. Create a calculation group to apply reusable calculation items to existing explicit measures
  5. Use Quick measures to generate a supported calculation pattern and inspect or adapt the resulting DAX

Correct answer: D

Why: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. This directly addresses the stated requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

Option review:

A: Balances and snapshots often add across entities but require last-value, first-value, or another special rule across dates. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

B: Measures calculate at query time in the current filter context and are the normal way to define reusable business aggregations. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

C: DAX includes statistical functions that summarize distributions beyond simple totals and averages. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

D: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. This directly addresses the stated requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

E: Quick measures create DAX for common analytical patterns and can accelerate authoring when the built-in pattern matches the need. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

Learning point: Create a calculation group to apply reusable calculation items to existing explicit measures

Question 9

Fourth Coffee is replacing a manual analytics process. The replacement must reliably materialize a DAX-derived table or row-level value in the semantic model. Which choice should be implemented for the forecast report, analysis cycle 5?

  1. Create a calculation group to apply reusable calculation items to existing explicit measures
  2. Create a DAX calculated table or calculated column when the result must be materialized during model refresh
  3. Create an explicit measure for a single aggregation such as SUM, COUNT, AVERAGE, MIN, or MAX
  4. Use basic statistical DAX functions to calculate values such as median, percentile, variance, or standard deviation when required
  5. Build time-intelligence measures against a suitable date table

Correct answer: B

Why: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. This directly addresses the stated requirement: materialize a DAX-derived table or row-level value in the semantic model.

Option review:

A: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

B: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. This directly addresses the stated requirement: materialize a DAX-derived table or row-level value in the semantic model.

C: Measures calculate at query time in the current filter context and are the normal way to define reusable business aggregations. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

D: DAX includes statistical functions that summarize distributions beyond simple totals and averages. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

E: Time-intelligence patterns compare or aggregate values across periods such as prior year, year to date, or rolling windows. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

Learning point: Create a DAX calculated table or calculated column when the result must be materialized during model refresh

Question 10

Which Power BI action best matches this technical purpose for the mobile report, analysis cycle 5: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures.

  1. Create a DAX calculated table or calculated column when the result must be materialized during model refresh
  2. Create a semi-additive measure that aggregates differently across time than across other dimensions
  3. Create a calculation group to apply reusable calculation items to existing explicit measures
  4. Use Quick measures to generate a supported calculation pattern and inspect or adapt the resulting DAX
  5. Use basic statistical DAX functions to calculate values such as median, percentile, variance, or standard deviation when required

Correct answer: C

Why: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. This directly addresses the stated requirement: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures..

Option review:

A: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures..

B: Balances and snapshots often add across entities but require last-value, first-value, or another special rule across dates. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures..

C: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. This directly addresses the stated requirement: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures..

D: Quick measures create DAX for common analytical patterns and can accelerate authoring when the built-in pattern matches the need. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures..

E: DAX includes statistical functions that summarize distributions beyond simple totals and averages. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures..

Learning point: Create a calculation group to apply reusable calculation items to existing explicit measures

Question 11

A runbook for the executive report, analysis cycle 6 contains this description: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. Which Power BI feature or action belongs in the runbook?

  1. Use basic statistical DAX functions to calculate values such as median, percentile, variance, or standard deviation when required
  2. Create an explicit measure for a single aggregation such as SUM, COUNT, AVERAGE, MIN, or MAX
  3. Build time-intelligence measures against a suitable date table
  4. Create a DAX calculated table or calculated column when the result must be materialized during model refresh
  5. Create a calculation group to apply reusable calculation items to existing explicit measures

Correct answer: D

Why: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. This directly addresses the stated requirement: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist..

Option review:

A: DAX includes statistical functions that summarize distributions beyond simple totals and averages. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist..

B: Measures calculate at query time in the current filter context and are the normal way to define reusable business aggregations. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist..

C: Time-intelligence patterns compare or aggregate values across periods such as prior year, year to date, or rolling windows. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist..

D: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. This directly addresses the stated requirement: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist..

E: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist..

Learning point: Create a DAX calculated table or calculated column when the result must be materialized during model refresh

Question 12

During validation of the sales model, analysis cycle 6, the self-service BI administrator needs a capability that behaves as follows: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. Which choice is correct?

  1. Create an explicit measure for a single aggregation such as SUM, COUNT, AVERAGE, MIN, or MAX
  2. Create a DAX calculated table or calculated column when the result must be materialized during model refresh
  3. Use Quick measures to generate a supported calculation pattern and inspect or adapt the resulting DAX
  4. Create a calculation group to apply reusable calculation items to existing explicit measures
  5. Build time-intelligence measures against a suitable date table

Correct answer: D

Why: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. This directly addresses the stated requirement: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures..

Option review:

A: Measures calculate at query time in the current filter context and are the normal way to define reusable business aggregations. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures..

B: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures..

C: Quick measures create DAX for common analytical patterns and can accelerate authoring when the built-in pattern matches the need. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures..

D: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. This directly addresses the stated requirement: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures..

E: Time-intelligence patterns compare or aggregate values across periods such as prior year, year to date, or rolling windows. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures..

Learning point: Create a calculation group to apply reusable calculation items to existing explicit measures

Question 13

A stakeholder asks why a particular Power BI feature should be used for the finance semantic model, analysis cycle 7. The required behavior is: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. Which action provides that behavior?

  1. Create a semi-additive measure that aggregates differently across time than across other dimensions
  2. Use basic statistical DAX functions to calculate values such as median, percentile, variance, or standard deviation when required
  3. Create a DAX calculated table or calculated column when the result must be materialized during model refresh
  4. Build time-intelligence measures against a suitable date table
  5. Use Quick measures to generate a supported calculation pattern and inspect or adapt the resulting DAX

Correct answer: C

Why: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. This directly addresses the stated requirement: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist..

Option review:

A: Balances and snapshots often add across entities but require last-value, first-value, or another special rule across dates. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist..

B: DAX includes statistical functions that summarize distributions beyond simple totals and averages. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist..

C: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. This directly addresses the stated requirement: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist..

D: Time-intelligence patterns compare or aggregate values across periods such as prior year, year to date, or rolling windows. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist..

E: Quick measures create DAX for common analytical patterns and can accelerate authoring when the built-in pattern matches the need. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist..

Learning point: Create a DAX calculated table or calculated column when the result must be materialized during model refresh

Question 14

The operations dashboard, analysis cycle 7 is moving to production at Fabrikam Manufacturing. Which action should be approved when the goal is to reduce many repetitive measure variants by applying reusable calculation logic to existing measures?

  1. Use Quick measures to generate a supported calculation pattern and inspect or adapt the resulting DAX
  2. Use basic statistical DAX functions to calculate values such as median, percentile, variance, or standard deviation when required
  3. Create a DAX calculated table or calculated column when the result must be materialized during model refresh
  4. Create a calculation group to apply reusable calculation items to existing explicit measures
  5. Create an explicit measure for a single aggregation such as SUM, COUNT, AVERAGE, MIN, or MAX

Correct answer: D

Why: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. This directly addresses the stated requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

Option review:

A: Quick measures create DAX for common analytical patterns and can accelerate authoring when the built-in pattern matches the need. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

B: DAX includes statistical functions that summarize distributions beyond simple totals and averages. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

C: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

D: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. This directly addresses the stated requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

E: Measures calculate at query time in the current filter context and are the normal way to define reusable business aggregations. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

Learning point: Create a calculation group to apply reusable calculation items to existing explicit measures

Question 15

A data analyst at Adventure Works must satisfy this acceptance criterion for the customer report, analysis cycle 8: materialize a DAX-derived table or row-level value in the semantic model. Which implementation is most appropriate?

  1. Create a semi-additive measure that aggregates differently across time than across other dimensions
  2. Create a DAX calculated table or calculated column when the result must be materialized during model refresh
  3. Create an explicit measure for a single aggregation such as SUM, COUNT, AVERAGE, MIN, or MAX
  4. Use Quick measures to generate a supported calculation pattern and inspect or adapt the resulting DAX
  5. Create a calculation group to apply reusable calculation items to existing explicit measures

Correct answer: B

Why: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. This directly addresses the stated requirement: materialize a DAX-derived table or row-level value in the semantic model.

Option review:

A: Balances and snapshots often add across entities but require last-value, first-value, or another special rule across dates. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

B: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. This directly addresses the stated requirement: materialize a DAX-derived table or row-level value in the semantic model.

C: Measures calculate at query time in the current filter context and are the normal way to define reusable business aggregations. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

D: Quick measures create DAX for common analytical patterns and can accelerate authoring when the built-in pattern matches the need. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

E: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

Learning point: Create a DAX calculated table or calculated column when the result must be materialized during model refresh

Question 16

A data-quality remediation at Proseware Services can proceed only after the team can reduce many repetitive measure variants by applying reusable calculation logic to existing measures. What should the BI developer configure?

  1. Use Quick measures to generate a supported calculation pattern and inspect or adapt the resulting DAX
  2. Create a semi-additive measure that aggregates differently across time than across other dimensions
  3. Use basic statistical DAX functions to calculate values such as median, percentile, variance, or standard deviation when required
  4. Create a DAX calculated table or calculated column when the result must be materialized during model refresh
  5. Create a calculation group to apply reusable calculation items to existing explicit measures

Correct answer: E

Why: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. This directly addresses the stated requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

Option review:

A: Quick measures create DAX for common analytical patterns and can accelerate authoring when the built-in pattern matches the need. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

B: Balances and snapshots often add across entities but require last-value, first-value, or another special rule across dates. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

C: DAX includes statistical functions that summarize distributions beyond simple totals and averages. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

D: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

E: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. This directly addresses the stated requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

Learning point: Create a calculation group to apply reusable calculation items to existing explicit measures

Question 17

The analytics team at Fourth Coffee has ruled out unrelated redesign work. Which action directly enables the team to materialize a DAX-derived table or row-level value in the semantic model for the inventory model, analysis cycle 9?

  1. Create a semi-additive measure that aggregates differently across time than across other dimensions
  2. Use Quick measures to generate a supported calculation pattern and inspect or adapt the resulting DAX
  3. Create a DAX calculated table or calculated column when the result must be materialized during model refresh
  4. Use CALCULATE to evaluate an expression under modified filter context
  5. Create a calculation group to apply reusable calculation items to existing explicit measures

Correct answer: C

Why: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. This directly addresses the stated requirement: materialize a DAX-derived table or row-level value in the semantic model.

Option review:

A: Balances and snapshots often add across entities but require last-value, first-value, or another special rule across dates. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

B: Quick measures create DAX for common analytical patterns and can accelerate authoring when the built-in pattern matches the need. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

C: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. This directly addresses the stated requirement: materialize a DAX-derived table or row-level value in the semantic model.

D: CALCULATE changes the filter context for an expression and is central to many DAX business calculations. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

E: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

Learning point: Create a DAX calculated table or calculated column when the result must be materialized during model refresh

Question 18

An audit finding for the service-level dashboard, analysis cycle 9 says the current design cannot reduce many repetitive measure variants by applying reusable calculation logic to existing measures. Which Power BI action most directly closes the gap?

  1. Use basic statistical DAX functions to calculate values such as median, percentile, variance, or standard deviation when required
  2. Create a calculation group to apply reusable calculation items to existing explicit measures
  3. Create a semi-additive measure that aggregates differently across time than across other dimensions
  4. Use CALCULATE to evaluate an expression under modified filter context
  5. Use Quick measures to generate a supported calculation pattern and inspect or adapt the resulting DAX

Correct answer: B

Why: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. This directly addresses the stated requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

Option review:

A: DAX includes statistical functions that summarize distributions beyond simple totals and averages. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

B: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. This directly addresses the stated requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

C: Balances and snapshots often add across entities but require last-value, first-value, or another special rule across dates. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

D: CALCULATE changes the filter context for an expression and is central to many DAX business calculations. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

E: Quick measures create DAX for common analytical patterns and can accelerate authoring when the built-in pattern matches the need. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

Learning point: Create a calculation group to apply reusable calculation items to existing explicit measures

Question 19

For the forecast report, analysis cycle 10, the data analyst needs a repeatable solution that will materialize a DAX-derived table or row-level value in the semantic model. Which option should replace the current ad hoc process?

  1. Use basic statistical DAX functions to calculate values such as median, percentile, variance, or standard deviation when required
  2. Build time-intelligence measures against a suitable date table
  3. Use Quick measures to generate a supported calculation pattern and inspect or adapt the resulting DAX
  4. Create a DAX calculated table or calculated column when the result must be materialized during model refresh
  5. Use CALCULATE to evaluate an expression under modified filter context

Correct answer: D

Why: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. This directly addresses the stated requirement: materialize a DAX-derived table or row-level value in the semantic model.

Option review:

A: DAX includes statistical functions that summarize distributions beyond simple totals and averages. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

B: Time-intelligence patterns compare or aggregate values across periods such as prior year, year to date, or rolling windows. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

C: Quick measures create DAX for common analytical patterns and can accelerate authoring when the built-in pattern matches the need. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

D: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. This directly addresses the stated requirement: materialize a DAX-derived table or row-level value in the semantic model.

E: CALCULATE changes the filter context for an expression and is central to many DAX business calculations. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

Learning point: Create a DAX calculated table or calculated column when the result must be materialized during model refresh

Question 20

During a monthly KPI review, Proseware Services defines the desired outcome as follows: reduce many repetitive measure variants by applying reusable calculation logic to existing measures. Which Power BI capability should the team use?

  1. Create a semi-additive measure that aggregates differently across time than across other dimensions
  2. Create a DAX calculated table or calculated column when the result must be materialized during model refresh
  3. Create a calculation group to apply reusable calculation items to existing explicit measures
  4. Use CALCULATE to evaluate an expression under modified filter context
  5. Use basic statistical DAX functions to calculate values such as median, percentile, variance, or standard deviation when required

Correct answer: C

Why: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. This directly addresses the stated requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

Option review:

A: Balances and snapshots often add across entities but require last-value, first-value, or another special rule across dates. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

B: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

C: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. This directly addresses the stated requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

D: CALCULATE changes the filter context for an expression and is central to many DAX business calculations. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

E: DAX includes statistical functions that summarize distributions beyond simple totals and averages. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

Learning point: Create a calculation group to apply reusable calculation items to existing explicit measures

Question 21

A new requirement is added to the executive report, analysis cycle 11: materialize a DAX-derived table or row-level value in the semantic model. Which action should the analytics lead take?

  1. Use basic statistical DAX functions to calculate values such as median, percentile, variance, or standard deviation when required
  2. Create a DAX calculated table or calculated column when the result must be materialized during model refresh
  3. Use Quick measures to generate a supported calculation pattern and inspect or adapt the resulting DAX
  4. Create an explicit measure for a single aggregation such as SUM, COUNT, AVERAGE, MIN, or MAX
  5. Build time-intelligence measures against a suitable date table

Correct answer: B

Why: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. This directly addresses the stated requirement: materialize a DAX-derived table or row-level value in the semantic model.

Option review:

A: DAX includes statistical functions that summarize distributions beyond simple totals and averages. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

B: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. This directly addresses the stated requirement: materialize a DAX-derived table or row-level value in the semantic model.

C: Quick measures create DAX for common analytical patterns and can accelerate authoring when the built-in pattern matches the need. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

D: Measures calculate at query time in the current filter context and are the normal way to define reusable business aggregations. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

E: Time-intelligence patterns compare or aggregate values across periods such as prior year, year to date, or rolling windows. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

Learning point: Create a DAX calculated table or calculated column when the result must be materialized during model refresh

Question 22

Fabrikam Manufacturing is troubleshooting an unexpected reporting result. The decisive requirement is to reduce many repetitive measure variants by applying reusable calculation logic to existing measures. Which feature or configuration is most relevant?

  1. Create a calculation group to apply reusable calculation items to existing explicit measures
  2. Use basic statistical DAX functions to calculate values such as median, percentile, variance, or standard deviation when required
  3. Build time-intelligence measures against a suitable date table
  4. Create an explicit measure for a single aggregation such as SUM, COUNT, AVERAGE, MIN, or MAX
  5. Create a semi-additive measure that aggregates differently across time than across other dimensions

Correct answer: A

Why: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. This directly addresses the stated requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

Option review:

A: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. This directly addresses the stated requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

B: DAX includes statistical functions that summarize distributions beyond simple totals and averages. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

C: Time-intelligence patterns compare or aggregate values across periods such as prior year, year to date, or rolling windows. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

D: Measures calculate at query time in the current filter context and are the normal way to define reusable business aggregations. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

E: Balances and snapshots often add across entities but require last-value, first-value, or another special rule across dates. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: reduce many repetitive measure variants by applying reusable calculation logic to existing measures.

Learning point: Create a calculation group to apply reusable calculation items to existing explicit measures

Question 23

A technical workshop for the finance semantic model, analysis cycle 12 documents this behavior: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. Which Power BI choice is being described?

  1. Build time-intelligence measures against a suitable date table
  2. Create a calculation group to apply reusable calculation items to existing explicit measures
  3. Create a DAX calculated table or calculated column when the result must be materialized during model refresh
  4. Use basic statistical DAX functions to calculate values such as median, percentile, variance, or standard deviation when required
  5. Use CALCULATE to evaluate an expression under modified filter context

Correct answer: C

Why: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. This directly addresses the stated requirement: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist..

Option review:

A: Time-intelligence patterns compare or aggregate values across periods such as prior year, year to date, or rolling windows. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist..

B: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist..

C: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. This directly addresses the stated requirement: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist..

D: DAX includes statistical functions that summarize distributions beyond simple totals and averages. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist..

E: CALCULATE changes the filter context for an expression and is central to many DAX business calculations. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist..

Learning point: Create a DAX calculated table or calculated column when the result must be materialized during model refresh

Question 24

The self-service BI administrator must identify the Power BI capability that provides this function: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. Which answer is correct for the operations dashboard, analysis cycle 12?

  1. Use Quick measures to generate a supported calculation pattern and inspect or adapt the resulting DAX
  2. Create a calculation group to apply reusable calculation items to existing explicit measures
  3. Use basic statistical DAX functions to calculate values such as median, percentile, variance, or standard deviation when required
  4. Use CALCULATE to evaluate an expression under modified filter context
  5. Create a semi-additive measure that aggregates differently across time than across other dimensions

Correct answer: B

Why: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. This directly addresses the stated requirement: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures..

Option review:

A: Quick measures create DAX for common analytical patterns and can accelerate authoring when the built-in pattern matches the need. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures..

B: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. This directly addresses the stated requirement: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures..

C: DAX includes statistical functions that summarize distributions beyond simple totals and averages. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures..

D: CALCULATE changes the filter context for an expression and is central to many DAX business calculations. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures..

E: Balances and snapshots often add across entities but require last-value, first-value, or another special rule across dates. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures..

Learning point: Create a calculation group to apply reusable calculation items to existing explicit measures

Question 25

A modernization plan for the customer report, analysis cycle 13 requires the team to materialize a DAX-derived table or row-level value in the semantic model. Which Power BI action is the clearest fit?

  1. Create a calculation group to apply reusable calculation items to existing explicit measures
  2. Create a semi-additive measure that aggregates differently across time than across other dimensions
  3. Create a DAX calculated table or calculated column when the result must be materialized during model refresh
  4. Build time-intelligence measures against a suitable date table
  5. Use CALCULATE to evaluate an expression under modified filter context

Correct answer: C

Why: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. This directly addresses the stated requirement: materialize a DAX-derived table or row-level value in the semantic model.

Option review:

A: Calculation groups reduce repetitive measures by applying DAX calculation items, such as time transformations, to selected measures. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

B: Balances and snapshots often add across entities but require last-value, first-value, or another special rule across dates. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

C: Calculated tables and columns are stored model objects created from DAX and are appropriate when row-level or table-level results must persist. This directly addresses the stated requirement: materialize a DAX-derived table or row-level value in the semantic model.

D: Time-intelligence patterns compare or aggregate values across periods such as prior year, year to date, or rolling windows. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

E: CALCULATE changes the filter context for an expression and is central to many DAX business calculations. It is useful in another Power BI scenario, but it does not most directly satisfy this requirement: materialize a DAX-derived table or row-level value in the semantic model.

Learning point: Create a DAX calculated table or calculated column when the result must be materialized during model refresh

Popular posts

img