Overview
Data and Database Fundamentals is 13% of the CompTIA Tech+ exam and has four objectives: the value of data and information, database concepts and the purpose of a database, comparing database structures, and basic data backup concepts. Together they follow data from collection, through storage and querying, to recovery after loss.
Candidates must be able to explain why a database is preferred over a flat file when many users share data, read a simple table design and identify rows, columns, primary keys and foreign keys, distinguish structured, semi-structured and unstructured data, recognize key/value and document databases, and choose between file and system backups stored locally or in the cloud. The domain builds on Software Development Concepts, where query languages and data types are introduced, and it relies on the storage types covered in Infrastructure.
How it's tested
Questions are mostly identification and BEST-choice items. You may see a small table description and be asked which column is the primary or foreign key, a business need that calls for a database instead of a flat file, a data sample to classify as structured or not, or a recovery requirement that points to a backup type and location.
-
Name the database element
A table layout is described and you identify the schema, record, field, primary key, foreign key or constraint it illustrates.
-
Flat file or database
A growing business shares a spreadsheet among many users, and you identify which database benefit (concurrency, scalability, speed or variety) solves the stated problem.
-
Choose the backup
A recovery goal, such as restoring one deleted folder or rebuilding a whole laptop, determines whether a file or system backup is needed and where it should be stored.
A photographer's laptop drive fails, and she wants the operating system, applications, settings and files back exactly as they were. Two answers look reasonable: restore her photo folders from cloud file backups, or restore a system backup. Only a system backup captures the operating system, installed applications and settings, so it is the answer; file backups would recover the photos but leave a full reinstall.
Objectives 4
Official objectives from the CompTIA outline, in outline order.
5.1 Explain the value of data and information.Data as an asset: capture, correlation, reporting, monetization, analytics and Big Data.
- What it means
- Organizations collect data, correlate it to find relationships, and turn it into meaningful reports that support decisions. Critical data is needed for the business to operate, while non-critical data can be lost with limited impact. Data can be monetized directly or through better targeting, analytics finds patterns and trends, and Big Data describes data sets too large, fast or varied for traditional tools.
- What to understand
- Raw data becomes information once it is processed and given context, such as daily sales figures turned into a trend report. The more critical the data, the more it must be protected and backed up.
- How it shows up
- A scenario describes a company combining purchase history with website visits to recommend products, and asks which concept it shows, such as correlation, analytics or monetization.
- Common confusion
- Candidates use data and information interchangeably. Data is raw facts; information is data processed into something meaningful for a decision.
5.2 Explain database concepts and the purpose of a database.Database uses, flat files vs. databases, records, persistence and availability.
- What it means
- Databases are used to create structures, input or import data, query it and produce reports. Compared with a flat file such as a single spreadsheet or text file, a database supports multiple concurrent users, scales to large volumes, retrieves data faster through queries and indexes, and handles a wider variety of data. Each entry is a record, data persistence means data remains stored after the application closes, and availability depends on cloud vs. local hosting and online vs. offline access.
- What to understand
- A flat file is fine for one person and a small list; once several people must update the same data simultaneously, or volume grows, a database prevents conflicts and slowdowns. Cloud databases can be reached from anywhere with a connection, while local ones keep working without the internet.
- How it shows up
- A growing team keeps overwriting each other's changes in a shared spreadsheet, and you choose the database benefit, or the database, that solves it.
- Common confusion
- Candidates think a database is just a bigger spreadsheet. The difference is managed structure, concurrent access and querying, not size alone.
5.3 Compare and contrast various database structures.Structured, semi-structured and unstructured data; relational and non-relational databases.
- What it means
- Structured data fits a fixed schema of tables, rows and columns; semi-structured data, such as JSON or XML, carries tags or keys but flexible fields; unstructured data, such as images, video and free-form documents, has no predefined model. Relational databases use a schema, tables, rows (records), columns (fields), primary keys, foreign keys and constraints. Non-relational databases include key/value stores and document databases.
- What to understand
- A primary key uniquely identifies each row in a table; a foreign key in one table refers to the primary key of another, creating a relationship. Constraints enforce rules such as required or unique values. Key/value stores retrieve a value by its key very quickly, while document databases store self-describing records whose fields can vary.
- How it shows up
- You are given a table description, such as an Orders table with a CustomerID column, and asked to identify the key type, or given a data sample and asked to classify its structure.
- Common confusion
- Candidates think a foreign key must be unique in its own table. It must match an existing primary key elsewhere, but it can repeat, as when one customer places many orders.
5.4 Explain basic data backup concepts.File vs. system backups, restoring data, and local or cloud storage locations.
- What it means
- A file backup copies selected files and folders; a system backup captures the whole system, including the operating system, applications and settings. Backups can be stored locally on flash drives, external hard drives or SD cards, or in cloud storage, and their purpose is to restore data after deletion, corruption, theft or hardware failure.
- What to understand
- Choose the backup type by what must be recovered: a deleted document needs a file restore, while a failed drive needs a system restore to avoid reinstalling everything. Local backups restore quickly but share risks with the original, such as fire or theft; cloud backups are offsite but depend on internet access. A backup is only trusted once a restore has been tested.
- How it shows up
- A user needs to recover a deleted spreadsheet, rebuild a stolen laptop, or protect against a house fire, and you pick the backup type and location.
- Common confusion
- Candidates treat file synchronization or a second copy on the same drive as a backup. If the original drive fails or the file is deleted and synced, that copy is lost too.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Data vs. information
Data is raw facts such as individual sales transactions; information is data processed and placed in context, such as a monthly sales trend.
- Remember
- Reporting and analytics turn data into information that supports decisions.
- Tested as
- Underpins objective 5.1 questions on data-driven decisions.
- Trap
- Labeling a raw export of records as information.
-
Critical vs. non-critical data
Critical data, such as customer accounts or financial records, is needed for the business to operate; non-critical data, such as old marketing drafts, can be lost with limited impact.
- Remember
- Protection and backup priority follow criticality.
- Tested as
- Appears when deciding what to back up first or protect most.
- Trap
- Treating every file as equally important, which wastes backup effort.
-
Big Data
Data sets so large, fast-arriving or varied, such as sensor streams or social media feeds, that traditional tools cannot process them efficiently.
- Remember
- Big Data is defined by volume, velocity and variety, not just size.
- Tested as
- Identification within the value-of-data objective.
- Trap
- Calling any large spreadsheet Big Data.
-
Flat file
A single table of data in a spreadsheet or text file, with no relationships to other tables.
- Remember
- Fine for one user and small data; weak at concurrent updates, scale and complex queries.
- Tested as
- The baseline in flat file vs. database questions.
- Trap
- Keeping a flat file when many users must edit the same records simultaneously.
-
Database benefits
Databases support multiple concurrent users, scale to large volumes, retrieve data quickly with queries, and handle a variety of data types.
- Remember
- Match the benefit to the problem: overwritten edits point to concurrency, slow searches to speed, growth to scalability.
- Tested as
- Central to objective 5.2 scenarios.
- Trap
- Choosing scalability when the stated problem is users overwriting each other.
-
Data persistence
Stored data remains available after the program closes or the system restarts, because it is written to non-volatile storage.
- Remember
- Persistence is why a database keeps records that RAM alone would lose.
- Tested as
- Concept identification in objective 5.2.
- Trap
- Confusing persistence with availability, which is about being reachable when needed.
-
Primary key
A field, or set of fields, whose value uniquely identifies each row in a table and is never empty, such as an EmployeeID.
- Remember
- One primary key per table; values are unique.
- Tested as
- Table-reading questions almost always involve keys.
- Trap
- Choosing a field like LastName, which can repeat, as the unique identifier.
-
Foreign key
A field in one table that holds values from another table's primary key, linking related records, such as CustomerID in an Orders table.
- Remember
- Foreign key values can repeat and must match an existing primary key.
- Tested as
- Paired with primary keys in relational design questions.
- Trap
- Calling CustomerID a primary key in the Orders table because it is a primary key in Customers.
-
Constraint
A rule the database enforces on data, such as a value being required, unique or within a valid range.
- Remember
- Constraints prevent bad data from being entered in the first place.
- Tested as
- Appears when a scenario asks how to stop blank or duplicate entries.
- Trap
- Relying on users to type values correctly instead of enforcing a rule.
-
Structured vs. semi-structured vs. unstructured
Structured data follows a fixed table schema, semi-structured data uses tags or keys with flexible fields (JSON, XML), and unstructured data has no predefined model (photos, videos, free text).
- Remember
- Tags without a fixed table layout mean semi-structured.
- Tested as
- A common classification question in objective 5.3.
- Trap
- Calling JSON unstructured because it is not in a table.
-
Key/value vs. document database
A key/value store retrieves a single value by its unique key, such as a session ID; a document database stores self-describing documents whose fields can differ from one record to the next.
- Remember
- Both are non-relational and do not require a fixed schema.
- Tested as
- Distinguishing non-relational types from each other and from relational tables.
- Trap
- Assuming non-relational means the data has no structure at all.
-
File backup vs. system backup
A file backup copies selected files and folders; a system backup captures the entire system, including the OS, applications and settings.
- Remember
- Rebuilding a failed or replaced computer quickly needs a system backup.
- Tested as
- The main decision in objective 5.4 scenarios.
- Trap
- Assuming file backups restore installed applications and settings.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Flat file vs. relational database vs. non-relational database
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Flat file | One table in a spreadsheet or text file | No relationships; weak with many concurrent editors | Using it as a multi-user system of record |
| Relational database | Related tables defined by a schema with keys and constraints | Enforces structure and relationships between tables | Thinking it is just a larger spreadsheet |
| Non-relational database | Key/value or document stores without a fixed table schema | Flexible fields, suited to varied or rapidly changing data | Assuming it cannot be queried or has no structure |
Primary key vs. foreign key vs. constraint
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Primary key | Uniquely identifies each row in its own table | Unique and required | Picking a field such as a name that can repeat |
| Foreign key | Refers to a primary key in another table | Creates a relationship; values may repeat | Mistaking it for the table's own primary key |
| Constraint | Any rule enforced on column values | Validates data on entry; keys are one kind of rule | Overlooking it as the answer to blank or duplicate entries |
Structured vs. semi-structured vs. unstructured data
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Structured | Fixed rows and columns, such as a customer table | Schema defined before data is stored | Assuming any digital file is structured |
| Semi-structured | Tagged or key-based data with flexible fields, such as JSON or XML | Self-describing but not bound to a table layout | Labeling it unstructured because it is not tabular |
| Unstructured | Images, video, audio, free-form documents | No predefined data model | Expecting to query it with ordinary table columns |
File backup vs. system backup; local vs. cloud
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| File backup | Copies chosen files and folders | Restores data, not the OS or applications | Expecting it to rebuild a failed computer |
| System backup | Captures the whole system, including OS, apps and settings | Restores the computer to a previous working state | Using it for every small file restore when a file backup is quicker |
| Local storage (external drive, flash drive, SD card) | Backup kept on media near the computer | Fast restores without internet access | Keeping it beside the computer, where fire or theft can take both |
| Cloud storage | Backup kept in a provider's data centers | Offsite and reachable anywhere, but depends on the connection | Confusing a synced folder, which mirrors deletions, with a backup |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Key that appears in both tables
- What candidates pick
- Primary key for CustomerID in an Orders table.
- Why it looks right
- CustomerID is a primary key in the Customers table, so the label seems to carry over.
- Why it's wrong
- In Orders, CustomerID references another table's primary key and can repeat for many orders, which makes it a foreign key.
Clue to watch for The column's values must match records in a different table, or one customer appears in many rows.
-
Size instead of concurrency
- What candidates pick
- Scalability as the database benefit for a team whose spreadsheet edits keep overwriting each other.
- Why it looks right
- The business is growing, and scalability sounds like the growth answer.
- Why it's wrong
- The stated problem is simultaneous edits colliding, which is solved by a database's support for multiple concurrent users.
Clue to watch for Words such as at the same time, overwrote or locked by another user.
-
Tagged data called unstructured
- What candidates pick
- Unstructured for a JSON file of customer profiles whose fields vary.
- Why it looks right
- The data is not in rows and columns and fields differ between records.
- Why it's wrong
- JSON carries keys and nested structure, making it semi-structured; unstructured data such as photos has no defined model.
Clue to watch for The sample contains named keys, tags or labels around values.
-
Sync mistaken for backup
- What candidates pick
- A cloud sync folder as the protection against accidental deletion.
- Why it looks right
- Files appear in the cloud, so they seem safe.
- Why it's wrong
- A sync service mirrors changes, including deletions and corruption, to every copy; a backup keeps an independent copy that can be restored.
Clue to watch for The scenario involves deleted, encrypted or corrupted files that must be recovered from an earlier point.
-
File backup for a full rebuild
- What candidates pick
- Restoring documents from file backups when a computer must be returned to its exact previous state.
- Why it looks right
- The user's files are the most valuable part.
- Why it's wrong
- File backups do not contain the OS, applications or settings, so everything else must be reinstalled; a system backup restores the whole configuration.
Clue to watch for Requirements mention applications, settings or exactly as it was.
-
Local backup next to the original
- What candidates pick
- An external drive kept beside the computer as the only backup.
- Why it looks right
- It is fast, cheap and easy to restore from.
- Why it's wrong
- Theft, fire or flood can destroy the computer and the drive together; an offsite or cloud copy protects against site-wide loss.
Clue to watch for The scenario mentions a fire, flood, burglary or protection against disaster at the location.
Answer framework
Use these steps for Data and Database Fundamentals questions about value, storage, structure or recovery.
- Identify which stage of the data lifecycle the question targets: collecting and using data, storing it, structuring it, or recovering it.
- For storage decisions, find the stated problem, such as concurrent edits, slow searches, growth or varied data, and match the database benefit to it.
- For table questions, ask whether a column uniquely identifies rows here, points to another table, or enforces a rule on entered values.
- For data classification, look for a fixed table layout, tags or keys with flexible fields, or no model at all.
- For recovery, decide whether files or the whole system must return, then choose a location that survives the threat described.
Practice question
Want more like this? The CompTIA Tech+ practice test has questions for every domain.
Checklist
0 of 13
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Start with database structures, because they carry the most exam-ready vocabulary. Sketch two related tables, such as Customers and Orders, and label the schema, a record, a field, the primary key, the foreign key and a constraint. Then classify ten sample data items, including a photo, a JSON profile and a spreadsheet, as structured, semi-structured or unstructured.
Next, study database concepts by contrasting a shared spreadsheet with a database. For each benefit (concurrent users, scalability, speed and variety) write one problem it solves. Commonly underestimated: persistence vs. availability, and cloud vs. local hosting trade-offs.
Then cover backups. Decide which type and location you would choose for a deleted file, a failed drive, a stolen laptop and a house fire, and explain why a synced folder is not a backup.
Finish with the value of data, the most conceptual objective; tie each term to a business example such as product recommendations. Afterwards, practice table-reading and backup scenarios, and continue into Security, where privacy, encryption and data protection apply the criticality ideas from this domain.
FAQ
How much of CompTIA Tech+ is Data and Database Fundamentals?
It is 13% of the exam, roughly nine questions if applied to the 70-question maximum. CompTIA publishes the weight, not per-domain question counts.
Do I need to write SQL queries for Tech+?
The objectives cover database uses such as querying and reporting, and query languages as a category in Domain 4, rather than writing SQL syntax. Focus on what queries do and on table concepts.
What is the difference between a primary key and a foreign key?
A primary key uniquely identifies each row in its own table. A foreign key holds values from another table's primary key to link records, and its values can repeat.
Is JSON structured or unstructured data?
JSON is semi-structured. It uses named keys and nesting, but its fields are flexible rather than fixed in a table schema.
When is a flat file good enough?
A flat file works for a single user managing a small, simple list. Once several people edit the same data, volume grows, or records relate to each other, a database is the better fit.
Which backup should I choose for a failed hard drive?
A system backup, because it restores the operating system, applications and settings along with the files, avoiding a full reinstall. File backups alone return only the data.
How does this domain connect to other Tech+ domains?
Query languages and data types come from Software Development Concepts, backup media come from Infrastructure's storage types, and Security's encryption and privacy objectives protect the data described here.
Other IT Fundamentals & Hardware certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 5 knowledge
You have covered the value of data, databases versus flat files, keys and data structures, and file versus system backups. Check whether you can read a table design and choose a recovery approach correctly under time pressure.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the CompTIA Tech+ AI tutor Get any concept explained your way