- A
INDEX
Why wrong: An index speeds up queries but does not enforce data integrity rules.
- B
FOREIGN KEY
Why wrong: A foreign key references another table; not applicable to email.
- C
PRIMARY KEY
Why wrong: A primary key is often an ID column, not the email, though it could be used, but it's not typical for email.
- D
UNIQUE and NOT NULL
These constraints ensure email is mandatory and distinct.
Quick Answer
The correct answer is to apply both the UNIQUE and NOT NULL constraints to the email column. This is because the UNIQUE constraint ensures that no two customers can share the same email address, preventing duplicate entries, while the NOT NULL constraint guarantees that the email field must always contain a value, satisfying the requirement that an email is always provided. On the CompTIA ITF+ FC0-U61 exam, this scenario tests your understanding of how SQL constraints enforce data integrity at the column level; a common trap is assuming that a PRIMARY KEY alone would suffice, but since the email is not necessarily the table’s primary identifier, the combination of UNIQUE and NOT NULL is the precise tool for a mandatory, distinct column. Remember the mnemonic “UNN” for UNique and Not Null—think of it as a double lock ensuring both uniqueness and completeness.
FC0-U61 IT Concepts and Terminology Practice Question
This FC0-U61 practice question tests your understanding of it concepts and terminology. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A database manager is designing a new table to store customer information for a retail company. The table needs to store a unique identifier for each customer, the customer's first and last name, email address, phone number, and date of birth. The manager also wants to ensure that the email address is always provided and that no two customers have the same email. Which of the following SQL constraints should be applied to the email column?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"first"Why it matters: Order matters here. You are being tested on which action comes before the others — not which action is generally useful.
Clue:
"always"Why it matters: Absolute qualifier. An answer using 'always' is only correct if there are genuinely no exceptions — absolute statements are often wrong in networking.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
UNIQUE and NOT NULL
The email column must be both unique (to prevent duplicate email addresses) and NOT NULL (to ensure an email is always provided). The UNIQUE constraint enforces that no two rows have the same value, and NOT NULL guarantees that the column cannot be left empty. Together, they satisfy the requirement that every customer has a distinct, mandatory email address.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
INDEX
Why it's wrong here
An index speeds up queries but does not enforce data integrity rules.
- ✗
FOREIGN KEY
Why it's wrong here
A foreign key references another table; not applicable to email.
- ✗
PRIMARY KEY
Why it's wrong here
A primary key is often an ID column, not the email, though it could be used, but it's not typical for email.
- ✓
UNIQUE and NOT NULL
Why this is correct
These constraints ensure email is mandatory and distinct.
Clue confirmation
The clue words "first", "always" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse PRIMARY KEY with UNIQUE+NOT NULL, not realizing that a table can have only one primary key and that email is often a natural key requiring both uniqueness and mandatory presence, but not necessarily the table's primary identifier.
Detailed technical explanation
How to think about this question
Under the hood, a UNIQUE constraint creates a unique index (typically a B-tree) to enforce uniqueness, while NOT NULL is a column-level constraint stored in the table metadata. In SQL, a table can have multiple UNIQUE constraints but only one PRIMARY KEY; combining UNIQUE and NOT NULL on a column effectively makes it a candidate key, which is a common pattern for natural keys like email addresses. In real-world retail systems, this ensures that login or communication systems can rely on email as a stable, non-repeating identifier.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the FC0-U61 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
IT Concepts and Terminology — study guide chapter
Learn the concepts, then practise the questions
- →
IT Concepts and Terminology practice questions
Targeted practice on this topic area only
- →
All FC0-U61 questions
512 questions across all exam domains
- →
CompTIA ITF+ FC0-U61 study guide
Full concept coverage aligned to exam objectives
- →
FC0-U61 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related FC0-U61 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
IT Concepts and Terminology practice questions
Practise FC0-U61 questions linked to IT Concepts and Terminology.
Infrastructure practice questions
Practise FC0-U61 questions linked to Infrastructure.
Applications and Software practice questions
Practise FC0-U61 questions linked to Applications and Software.
Software Development Concepts practice questions
Practise FC0-U61 questions linked to Software Development Concepts.
Security practice questions
Practise FC0-U61 questions linked to Security.
Database Fundamentals practice questions
Practise FC0-U61 questions linked to Database Fundamentals.
FC0-U61 fundamentals practice questions
Practise FC0-U61 questions linked to FC0-U61 fundamentals.
FC0-U61 scenario practice questions
Practise FC0-U61 questions linked to FC0-U61 scenario.
FC0-U61 troubleshooting practice questions
Practise FC0-U61 questions linked to FC0-U61 troubleshooting.
Practice this exam
Start a free FC0-U61 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this FC0-U61 question test?
IT Concepts and Terminology — This question tests IT Concepts and Terminology — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: UNIQUE and NOT NULL — The email column must be both unique (to prevent duplicate email addresses) and NOT NULL (to ensure an email is always provided). The UNIQUE constraint enforces that no two rows have the same value, and NOT NULL guarantees that the column cannot be left empty. Together, they satisfy the requirement that every customer has a distinct, mandatory email address.
What should I do if I get this FC0-U61 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "first", "always". Order matters here. You are being tested on which action comes before the others — not which action is generally useful.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 25, 2026
This FC0-U61 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the FC0-U61 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.