[03/Santee/04]

What is the purpose of Composite Business Keys in Hubs?

What is an alternative approach to handling different business key structures in hubs?

Why is creating multiple hubs for each key structure considered less efficient?

Composite Business Keys in Hubs allow a concept to have the same business key in different sources and tables.

Same-as-Link (SAL) is the only way to extend the concept of Composite Business Keys in Hubs.

Creating multiple hubs for each key structure is always considered less efficient.

Match the following concepts with their descriptions:

What is the purpose of using Composite Business Keys in Hubs?

Why might a single attribute like an employee ID not be enough to ensure uniqueness in a table storing employee information?

What is the trade-off when using a single hub to cover all business keys?

What is the alternative approach to handling different business key structures in hubs?

What do composite business keys refer to in a database table?

Why might a single attribute like an employee ID not be enough to ensure uniqueness in a table storing employee information?

What is the most efficient design for handling different business key structures?

Composite business keys refer to a combination of two or more attributes within a database table that, together, uniquely identify a record in a database.

In a table that stores information about employees, a single attribute like an employee ID might be enough to ensure uniqueness, especially if employees can work in different departments.

It is possible to adjust the rules in order to generate one hub per business key structure or other designs, but the standard design is considered the most efficient.

Creating multiple hubs for each key structure is always considered less efficient.

Same-as-Link (SAL) is the only way to extend the concept of Composite Business Keys in Hubs.

Composite Business Keys in Hubs allow a concept to have the same business key in different sources and tables.

Using multiple columns or attributes rather than a single attribute to uniquely identify a record within a table is the purpose of using Composite Business Keys in Hubs.

Match the following terms with their descriptions:

Match the following scenarios with their corresponding need for Composite Business Keys:

Match the following design approaches with their descriptions:

Match the following statements with their corresponding implications: