In DBMS software referential integrity ensures that

Question

BlackTom AI · Accepted Answer

Consider the concept being tested: referential integrity in a DBMS.
Option a: 'a value entered into field as a primary key already exists as a foreign key value in a related table.' This is incorrect because referential integrity concerns foreign keys referencing existing primary keys, not the reverse scenario of a primary key appearing as a foreign key.
Option b: 'each foreign key is an autonumber.' This statement is false in general; foreign keys can be user-specified values that reference primary keys in another table, not necessarily autonumbered. Autonumbering is not a defining requirement of referential integrity.
Option c: 'a value entered into field as a foreign key already exists as a primary key value in a related table.' This captures the core idea: any value placed in a foreign key column must exist as a corresponding primary key in the related (referenced) table, ensuring valid references and preventing orphaned records.
Option d: 'each primary key is an autonumber.' This is not a requirement of referential integrity. Primary keys can be natural keys or surrogate keys, and autonumbering is a design choice, not a referential integrity constraint.
Overall, the options describe various aspects of keys and references; only option c aligns with the formal constraint that foreign key values must reference existing primary keys in the related table, which enforces referential integrity.

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

In DBMS software referential integrity ensures that

View Explanation

Log in for full answers

Similar Questions

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

More Practical Tools for Students Powered by AI Study Helper

Homework AI Solver

Stylized AI Paper Writer

Plagiarism Checker Assistant

Citation AI Academic Writing Tool

In-Class Translation Assistant

AI Note Generator

AI Quiz Answers

Past Exam Questions from University Test Bank

Smart Practice Assistant

Adaptive Practice

Making Your Study Simpler