Need Help Question 9 (4 points) D HAPPY INSURANCE Observe the HAPPY INSURANCE DA

Question

Need Help

Question 9 (4 points) D HAPPY INSURANCE Observe the HAPPY INSURANCE DATABASE: CLIENT ClientiD ClientName ClientAgent ClientSpouseName C111 Tom A1 Jenny C222 Karin A1 Bilf C333 Cole A2 Amy C444 Dorothy A2 C555 Andy A3 Amy C666 Tina A3 Matt C777 Christina A4 Mike AGENT AgentiD AgentName AgentArea AgentRating AgentYearOfHire SupervisedBy A1 Kate 1 101 1990 A2 Amy 2 92 2009 A1 A3 Luke 3 100 1992 A4 James 3 90 2010 A3 AREA ArealD AreaNameAreaHQ 1 East Boston 2 West San Francisco 3 Central Chicago This database will be used for the following question citing tables from the HAPPY INSURANCE database. If a DBMS enforces an UPDATE SET-TO-NULL option on the referential integrity constraint between CLIENT and AGENT in the HAPPY INSURANCE database, what will be the outcome after a user tries to change the AgentID value in the last record to A5? Value A4 appears once in column AgentlD in AGENT, and value A4 appears once in column ClientAgent in table CLIENT Value A5 appears once in column AgentID in AGENT, and value A5 appears once in column ClientAgent in table CLIENT Value A5 appears once in column AgentID in AGENT, and value A5 does not appear in column ClientAgent in table CLIENT Value A5 does not appear in column AgentID in AGENT, and value A5appears once in column ClientAgent in table CLIENT

Explanation / Answer

As per the refrential integrity constraint UPDATE SET-TO-NULL, if the primary key is updated, all the foreign key refrences will be set to NULL. Hence, the answer is the option 3 (or C): Value A5 appears once in a column AgentID in AGENT, and value A5 does not appear in column ClientAgent in table CLIENT.

Related Questions

Navigate

• Browse (All)
• Browse N
• Subjects

---

---

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.