MENU
A table is defined as below. Select the most suitable description about the foreign key constraint. CREATE TABLE master (id INTEGER PRIMARY KEY, name TEXT); CREATE TABLE record (id INTEGER REFERENCES master (id), count INTEGER);
Suggested Answer: A
Get Premium PGCES-02 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
34 comments · newest first
ME
Mendy
11 months ago
B is too strict; you can still update master if record has an id.
DA
Dan
11 months ago
Wait, are these SQL statements really valid? Seems off to me.
RI
Rikki
12 months ago
D is not true, record can have duplicates unless specified otherwise.
JO
Jolene
12 months ago
I disagree, A is misleading. Changes can still be made to master.
MA
Mabel
12 months ago
C is correct! You can't delete from master if record has that id.
IR
Irving
1 year ago
I feel like option D is about uniqueness in the 'record' table, but I don't think that's what the foreign key constraint is about. I might be confused on this one!
LE
Leonida
1 year ago
I'm not entirely sure, but I remember something about foreign keys preventing changes to the parent table if there are dependent rows. Could that relate to option A or C?
DA
Daren
1 year ago
I think the foreign key constraint means that if there's a related row in the 'record' table, you can't delete the corresponding row in 'master'. So maybe it's option C?
MI
Micah
1 year ago
I practiced a similar question, and I think the foreign key allows for updates in 'master' as long as there are no dependent rows in 'record'. So, I might lean towards option C.
TA
Tawna
1 year ago
This is a good example of the kind of question I need to watch out for. It seems simple, but you have to really think about the privacy and security requirements. I'm going to mark this one as False.
MA
Marylyn
1 year ago
This seems simple enough. I'll just follow the instructions and double-check my work before submitting.
AM
Amber
1 year ago
This question seems a bit tricky. I'll need to carefully consider the differences between the production and non-production environments to determine the license cost.
DO
Domonique
1 year ago
"External area" doesn't seem right at all, but I'm confused between "Multiple areas" and the others. It's been a while since we reviewed these concepts!
VA
Valda
1 year ago
I'm just impressed they managed to fit all this into a single exam question. That's some serious database compression right there!
RO
Royal
1 year ago
D) The 'record' table cannot have duplicate 'id's.
DO
Domonique
1 year ago
C) If the 'record' table contains a row with an 'id', the corresponding 'id' row in the 'master' table cannot be deleted.
TY
Ty
1 year ago
B) If the 'record' table contains a row with an 'id', no change can be made at all to the corresponding 'id' row in the 'master' table.
CA
Carri
1 year ago
C) If the 'record' table contains a row with an 'id', the corresponding 'id' row in the 'master' table cannot be deleted.
LE
Leah
1 year ago
B) If the 'record' table contains a row with an 'id', no change can be made at all to the corresponding 'id' row in the 'master' table.
JU
Julie
1 year ago
A) If any row exists in the 'record' table, no change can be made to the 'master' table.
KA
Karma
1 year ago
A) If any row exists in the 'record' table, no change can be made to the 'master' table.
CA
Cammy
1 year ago
Exactly, it's a way to link the two tables together and prevent any inconsistencies.
TA
Tanesha
1 year ago
So, basically, the foreign key constraint ensures that you can't delete a record in the 'master' table if it's being referenced in the 'record' table.
LA
Latonia
1 year ago
I agree, that sounds right. It's all about maintaining data integrity.
FA
Fanny
1 year ago
I think the answer is C) If the 'record' table contains a row with an 'id', the corresponding 'id' row in the 'master' table cannot be deleted.
VE
Verdell
1 year ago
Option E? Really? These are perfectly valid SQL statements. Someone needs to brush up on their database knowledge.
AV
Avery
1 year ago
Haha, good thing the 'record' table doesn't have a column called 'count_of_beers'. That would be a whole different kind of foreign key constraint!
DO
Dominic
1 year ago
C) If the 'record' table contains a row with an 'id', the corresponding 'id' row in the 'master' table cannot be deleted.
NI
Nickole
1 year ago
A) If any row exists in the 'record' table, no change can be made to the 'master' table.
DI
Dion
1 year ago
I agree with Stephane. This is a classic example of a foreign key constraint, which prevents orphaned records in the dependent table.
ST
Stephane
2 years ago
Option C is the correct answer. The foreign key constraint ensures that the corresponding row in the master table cannot be deleted if there is a reference to it in the record table.
GI
Gilbert
2 years ago
Hmm, that makes sense too. It's important to understand the implications of foreign key constraints in database design.
LE
Leonida
2 years ago
I disagree, I believe the answer is A. The foreign key constraint prevents any changes to the master table if a row exists in the record table.
GI
Gilbert
2 years ago
I think the answer is C. The foreign key constraint ensures that the corresponding row in the master table cannot be deleted.