In DBMS software referential integrity ensures that

Question

BlackTom AI · Accepted Answer

In DBMS software referential integrity ensures that
Option a: 'a value entered into field as a primary key already exists as a foreign key value in a related table.' This swaps the typical relationship direction. Referential integrity is about ensuring that a foreign key value corresponds to an existing primary key in the related table, not the other way around. So this option is incorrect because it describes a reversed relationship.
Option b: 'a value entered into field as a foreign key already exists as a primary key value in a related table.' This is the correct description of referential integrity. It ensures that any value placed in a foreign key column must match a primary key value in the related table, maintaining valid references across tables.
Option c: 'each primary key is an autonumber.' This is not a requirement of referential integrity. Autonumbering (automatic generation of primary key values) is a design choice, not a rule that enforces referential links between tables.
Option d: 'each foreign key is an autonumber.' This is incorrect because foreign keys typically reference primary keys; they are not usually autonumbered themselves. Autonumbering a foreign key would undermine the purpose of linking to the related table’s primary key and is not a definition of referential integrity.

MUF0052 ICT Unit 2 - Semester 1, 2025 2.9 Quiz: Relational DBMS

In DBMS software referential integrity ensures that

查看解析

登录即可查看完整答案

类似问题

What types of Referential Integrity constraint can be coded to maintain consistency between the rows of two tables:

Which type of key can enforce rules such as cascading updates or deletions?

Question at position 41 A referential integrity constraint specifies that the existence of an attribute in one table depends upon the existence of a foreign key in the same or another table.TrueFalse

Question at position 50 A referential integrity constraint specifies that the existence of an attribute in one table depends upon the existence of a foreign key in the same or another table.TrueFalse

Question at position 32 Requiring a CustomerID to exist in a Primary table before it can exist in a foreign table is an example of:the Hoffer Principle.referential integrity.key constraints.referential referring.

Question at position 36 A referential integrity constraint specifies that the existence of an attribute in one table depends upon the existence of a foreign key in the same or another table.TrueFalse

Question at position 7 Requiring a CustomerID to exist in a Primary table before it can exist in a foreign table is an example of:referential referring.referential integrity.the Hoffer Principle.key constraints.

Question at position 53 A referential integrity constraint specifies that the existence of an attribute in one table depends upon the existence of a foreign key in the same or another table.TrueFalse

更多留学生实用工具

考试浏览器助手

风格化写作助手

论文查重助手

文献引用助手

课堂转译助手

课堂笔记助手

Quiz搜索助手

学校历年真题

智能刷题助手

智能匹配练习

希望你的学习变得更简单