nerdexam
Microsoft

70-467 · Question #78

You need to choose the appropriate key to use when designing a dimension table based on the Customer table. What should you do?

The correct answer is A. Use a surrogate key. Surrogate keys are the industry-standard primary key for dimension tables in data warehouse design, decoupling the warehouse from source system volatility.

Design a data warehousing solution

Question

You need to choose the appropriate key to use when designing a dimension table based on the Customer table. What should you do?

Options

  • AUse a surrogate key.
  • BUse a natural key.
  • CUse the CustomerNumber column as the key.
  • DConcatenate the CustomerName and CustomerNumber columns and use the concatenated
  • EUse the CustomerName column as the key.

How the community answered

(22 responses)
  • A
    95% (21)
  • E
    5% (1)

Why each option

Surrogate keys are the industry-standard primary key for dimension tables in data warehouse design, decoupling the warehouse from source system volatility.

AUse a surrogate key.Correct

A surrogate key is a system-generated, typically integer-based key that uniquely identifies each row in a dimension table independently of source system values. It enables slowly changing dimension (SCD) tracking by allowing multiple versions of the same entity without impacting fact table foreign keys. Surrogate keys decouple the data warehouse from source system key changes, deletions, or reuse, ensuring long-term referential integrity.

BUse a natural key.

Natural keys from source systems can change, be reused, or contain nulls over time, making them unreliable as stable, permanent dimension identifiers.

CUse the CustomerNumber column as the key.

Using CustomerNumber ties the dimension directly to the source system business key, which cannot support slowly changing dimension scenarios if that value is ever updated or reassigned.

DConcatenate the CustomerName and CustomerNumber columns and use the concatenated

A concatenated key of CustomerName and CustomerNumber is inefficient for joins, grows unnecessarily large, and still inherits the instability problems of both source system natural keys.

EUse the CustomerName column as the key.

CustomerName is not guaranteed to be unique across all customers and can change due to legal name changes or data entry corrections, making it unsuitable as a primary key.

Concept tested: Surrogate key design for dimension tables in star schema

Source: https://learn.microsoft.com/en-us/power-bi/guidance/star-schema

Topics

#surrogate key#dimension design#natural key#data warehousing

Community Discussion

No community discussion yet for this question.

Full 70-467 Practice