18 real Relationships questions from the EF Core bank, as asked in Indian campus drives and tech interviews. Every question has a verified answer and an AI-tutor explanation on placd — free to start.
1. What is one-to-many?
Junior
A.a reference or collection member on an entity that lets code traverse to related entities in object form
B.an association, supported directly since version 5, where rows on both sides relate to multiple rows on the other through an implicit join table
C.an association where a single principal row is referenced by many dependent rows, the most common relationship cardinality
D.the behavior where removing a principal row automatically removes the dependent rows that require it
A.one-to-many — the behavior where removing a principal row automatically removes the dependent rows that require it
B.one-to-many — an association where a single principal row is referenced by many dependent rows, the most common relationship cardinality
C.one-to-many — the two roles in an association where one end owns the key the other end refers to
D.one-to-many — an association, supported directly since version 5, where rows on both sides relate to multiple rows on the other through an implicit join table
5. Which term means: "an association, supported directly since version 5, where rows on both sides relate to multiple rows on the other through an implicit join table"?
A.many-to-many — the behavior where removing a principal row automatically removes the dependent rows that require it
B.many-to-many — an association, supported directly since version 5, where rows on both sides relate to multiple rows on the other through an implicit join table
C.many-to-many — an association where a single principal row is referenced by many dependent rows, the most common relationship cardinality
D.many-to-many — the two roles in an association where one end owns the key the other end refers to
A.navigation property — an association where a single principal row is referenced by many dependent rows, the most common relationship cardinality
B.navigation property — a reference or collection member on an entity that lets code traverse to related entities in object form
C.navigation property — an association, supported directly since version 5, where rows on both sides relate to multiple rows on the other through an implicit join table
D.navigation property — the two roles in an association where one end owns the key the other end refers to
A.principal and dependent — a reference or collection member on an entity that lets code traverse to related entities in object form
B.principal and dependent — the behavior where removing a principal row automatically removes the dependent rows that require it
C.principal and dependent — the two roles in an association where one end owns the key the other end refers to
D.principal and dependent — an association, supported directly since version 5, where rows on both sides relate to multiple rows on the other through an implicit join table
A.cascade delete — an association, supported directly since version 5, where rows on both sides relate to multiple rows on the other through an implicit join table
B.cascade delete — the behavior where removing a principal row automatically removes the dependent rows that require it
C.cascade delete — an association where a single principal row is referenced by many dependent rows, the most common relationship cardinality
D.cascade delete — the dependent-side property holding the value that points back to the primary key of the principal row
Answers, AI explanations, and a scored voice mock interview
Sign up free to check your answers with explanations, ask the AI tutor anything on any question, and take one full AI mock interview — scored like a real panel.