Dataford
Interview QuestionsInterview GuidesExperiencesMock InterviewsPricing
Get started
Dataford
Popular roles
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Browse
Browse All RolesEvery role hub, from analyst to MLBrowse All CompaniesCompany-specific interview loopsAll Interview GuidesThe full guide library
Top questions by role
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Top questions by skill
SQLPythonStatisticsMachine LearningA/B TestingSystem DesignGenerative AIProduct SenseMetricsBehavioral
Browse all questions →Try a mock interview
Experiences
Practice
Mock InterviewsTimed interview simulations with feedbackSuccess PathYour 6-week structured planModulesCurated lessons by topicWebinarsTalks from ex-Big Tech data leadsPlaygroundA free-form scratch editor
Learn
BlogInterview strategy and career adviceTech Job Market ReportHiring trends across data and AI rolesFor UniversitiesDataford for career centersAbout DatafordWho we are and how we build
Pricing
Build my plan

Key Constraints in Relational Databases

EasySQL & Data Manipulation00:00
Practice interviewer
In session
5 left
00:00

Your question is Key Constraints in Relational Databases. Take a moment with it on the right.

Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).

You need to log in / sign up to chat or submit.

Problem

Context

Key constraints are basic but important database concepts because they control how rows are identified and how tables relate to each other. In a QA setting, understanding them helps you reason about duplicate data, broken references, and schema validation.

Question

You are asked to explain the difference between a primary key, a foreign key, and a unique key in a relational database. Describe what each constraint enforces, how they differ in purpose, and how they work together in a normalized schema. If helpful, use a simple example such as Telus Digital QA test runs and test cases.

Scope guidance

The interviewer is looking for a clear conceptual explanation, not a long theory lecture. You should cover uniqueness, nullability, referential integrity, and whether a table can have one or multiple instances of each constraint type.