A00-260 · Question #40
In SAS Data Integration Studio, where must the columns included in a business key exist?
The correct answer is B. in the source and dimension tables. Option B is correct because a business key in SAS Data Integration Studio is used to uniquely identify and match records between incoming data and the dimension table - so the key columns must exist in both the source (to supply the identifying values) and the dimension table…
Question
In SAS Data Integration Studio, where must the columns included in a business key exist?
Options
- Ain the source and standardization tables
- Bin the source and dimension tables
- Cin the target and fact tables
- Din the source, dimension and standardization tables
How the community answered
(24 responses)- B96% (23)
- C4% (1)
Explanation
Option B is correct because a business key in SAS Data Integration Studio is used to uniquely identify and match records between incoming data and the dimension table - so the key columns must exist in both the source (to supply the identifying values) and the dimension table (to perform the lookup and determine whether to insert or update a record).
Option A is wrong because standardization tables are intermediate processing structures; the key matching logic operates between source and dimension, not between source and a standardization table. Option C is wrong because fact tables store measures and foreign keys, not the entity-level identifiers that business keys represent - business keys belong to the dimension layer. Option D is wrong because it includes standardization tables alongside the correct source and dimension tables; adding standardization as a requirement overcomplicates the rule and doesn't reflect how DI Studio enforces business key placement.
Memory tip: Think of the letters Source → Dimension as "SD card" - just like an SD card stores and retrieves data, the business key stores unique identity in the dimension and retrieves matches from the source. Source + Dimension = SD, nothing more.
Topics
Community Discussion
No community discussion yet for this question.