A00-260 · Question #11
In SAS Data Integration Studio, primary keys, foreign keys and unique keys can be specified/defined in which location?
The correct answer is C. the Keys tab in the properties of a table metadata object. In SAS Data Integration Studio, primary keys, foreign keys, and unique keys are properties of the data itself, not of any transformation process - so they belong on the Keys tab in the properties of a table metadata object (C). This makes logical sense: a table's key…
Question
In SAS Data Integration Studio, primary keys, foreign keys and unique keys can be specified/defined in which location?
Options
- Athe Keys tab in the properties of a Table Loader transformation
- Bthe Keys tab in the properties for any transformation
- Cthe Keys tab in the properties of a table metadata object
- Dthe Keys tab in the properties of a job metadata object
How the community answered
(30 responses)- A7% (2)
- B3% (1)
- C87% (26)
- D3% (1)
Explanation
In SAS Data Integration Studio, primary keys, foreign keys, and unique keys are properties of the data itself, not of any transformation process - so they belong on the Keys tab in the properties of a table metadata object (C). This makes logical sense: a table's key constraints describe its structure and relationships, which are defined at the metadata level for the table, independent of how data is loaded or transformed.
Why the distractors are wrong:
- A is wrong because the Table Loader transformation handles how data is loaded, not the structural constraints of the table itself.
- B is wrong because transformations in general are about data movement and manipulation - key definitions don't belong in transformation properties at all.
- D is wrong because a job metadata object orchestrates execution flow; it has no role in defining data structure.
Memory tip: Think of it this way - keys describe what the table is, not what a job does to it. Always define structural metadata (keys, columns) on the table object, not on transformations or jobs.
Topics
Community Discussion
No community discussion yet for this question.