You need to configure a one-to-many relationship between ACME_ORDER and ACME_ORDER_ITEM. What is a valid method for configuring this relationship in the database?

You need to configure a one-to-many relationship between ACME_ORDER and ACME_ORDER_ITEM. What is a valid method for configuring this relationship in the database?

• A. Add a new field "ORDER_ID" on the ACME_ORDER_ITEM table and set the field as a foreign key to the ACME_ORDER entry.
• B. Add a new field "ORDER_ID" on the ACME_ORDER table and set the field as a foreign key to the ACME_ORDER entry.
• C. Create a link table
• D. Use data sync

Answer: (B)

In a one-to-many relationship, the link is established by the child table holding the reference to its parent. For ACME_ORDER and ACME_ORDER_ITEM, that means adding a foreign key column in the child table (the many side) that points to the parent table’s primary key. So you would create a field like ORDER_ID on ACME_ORDER_ITEM and define it as a foreign key to ACME_ORDER. This ensures each order item is linked to exactly one order, while a single order can have many order items, which is exactly what a 1:N relationship represents. The foreign key constraint enforces referential integrity, so every order item must reference a valid order.

In a one-to-many relationship, the link is established by the child table holding the reference to its parent. For ACME_ORDER and ACME_ORDER_ITEM, that means adding a foreign key column in the child table (the many side) that points to the parent table’s primary key. So you would create a field like ORDER_ID on ACME_ORDER_ITEM and define it as a foreign key to ACME_ORDER. This ensures each order item is linked to exactly one order, while a single order can have many order items, which is exactly what a 1:N relationship represents. The foreign key constraint enforces referential integrity, so every order item must reference a valid order.