FC0-U71 Data and Database Fundamentals Practice Question
A help desk technician is creating a spreadsheet to track support tickets. They want each ticket to have a unique identifier that is automatically generated when a new row is added, and they want the value to never repeat even if rows are deleted. Which spreadsheet feature should they use?
⚠ Common exam trap
The trap here is assuming that any column can be made unique by formatting or validating it, when only an automatic ID feature generates new unique values for each record.
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
✓
Use an AutoNumber or automatic row ID feature
An automatic row ID or AutoNumber feature is designed to produce a unique value for every new record without user intervention. It continues to generate new values even after records are deleted, so duplicates do not occur. Data validation, text formatting, and sorting do not automatically create or guarantee unique identifiers.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Use an AutoNumber or automatic row ID feature
Why this is correct
AutoNumber fields, sometimes called automatic row IDs, generate a unique sequential or random value whenever a new record is created. They continue incrementing even if earlier rows are deleted, so the identifier never repeats. This directly meets the requirement for a unique ticket identifier that is created automatically for each new support ticket.
- ✗
Apply a data validation rule to the ticket ID column
Why it's wrong here
Data validation restricts what a user can type into a cell, such as limiting entries to a list or a number range. It does not generate unique values automatically, nor does it prevent duplicates after rows are deleted. It is useful for controlling input, but it does not satisfy the requirement for an automatically generated, never-repeating identifier.
- ✗
Format the ticket ID column as text
Why it's wrong here
Formatting a column as text only changes how values are displayed and stored; it does not create new identifiers or enforce uniqueness. A user could still type the same ticket ID twice. This option addresses appearance and data type, not the need for automatic, unique identification of each support ticket.
- ✗
Sort the ticket ID column in ascending order
Why it's wrong here
Sorting rearranges existing rows but does not create or enforce unique identifiers. If two tickets already have the same ID, sorting will not fix that. This option is about organizing data for viewing, not about generating a guaranteed unique value for each new support ticket record.
Go deeper
Related to this question
About these practice questions
One of 988 original FC0-U71 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
This FC0-U71 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-U71 exam.