Courseiva
← FC0-U71
Full test
mediumMultiple Select

FC0-U71 Practice Question: Which TWO of the following are advantages of…

Which TWO of the following are advantages of using a relational database management system (RDBMS) over a file-based system?

⚠ Common exam trap

A common mix-up: candidates assume 'faster data access' is always true for RDBMS due to indexing, but they overlook the overhead of SQL processing and the fact that file-based systems can be faster for simple, non-relational lookups.

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

✓

Enforcement of data integrity

Option A (Enforcement of data integrity) is correct because an RDBMS enforces integrity through mechanisms such as primary keys, foreign keys, unique constraints, CHECK constraints, and ACID-compliant transactions, which a flat file-based system cannot natively provide. Option C (Reduced data redundancy) is correct because an RDBMS supports normalization, storing each fact once and linking records via relationships, whereas file-based systems typically duplicate data across separate files. Option B is incorrect because an RDBMS does not guarantee faster access for all queries; poorly indexed or complex joins can be slower than reading a simple flat file, and performance depends on design and workload. Option D is incorrect because an RDBMS generally requires more administration (backups, tuning, user management, patching), not less. Option E is incorrect because an RDBMS is typically more complex to install, configure, and maintain than a simple file-based system.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✓

    Enforcement of data integrity

    Why this is correct

    An RDBMS enforces integrity through primary keys, foreign keys, NOT NULL and CHECK constraints at the engine level. A file-based system has no such declarative rules, so this constraint enforcement is a genuine RDBMS advantage over flat files.

  • ✗

    Faster data access for all queries

    Why it's wrong here

    An RDBMS does not guarantee faster access for every query; unindexed joins and complex queries can be slower than a flat file scan. It is tempting because indexed lookups and query optimisation often outperform file reads, which is the scenario where the claim holds.

  • ✓

    Reduced data redundancy

    Why this is correct

    Normalising data across related tables means each fact is stored once, so an RDBMS eliminates the duplicated records inherent in separate flat files. This reduced redundancy is a direct advantage of the relational model over file-based storage.

  • ✗

    No need for a database administrator

    Why it's wrong here

    Most RDBMS environments require a DBA.

  • ✗

    Simpler setup and maintenance

    Why it's wrong here

    RDBMS requires explicit schema definition, normalisation, and index configuration—steps absent in file-based systems where data is simply stored in flat files. The temptation arises because file systems lack built-in referential integrity and concurrency management, so an RDBMS automates these safeguards; however, that automation imposes additional setup and maintenance tasks. For a single-user, static dataset with no relationships, a file-based system would indeed involve less administrative overhead.

About these practice questions

This FC0-U71 question is part of Courseiva's 988-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more way this is tested on FC0-U71

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. Which THREE of the following are types of data integrity enforced in relational databases?

medium
  • ✓ A.Referential integrity
  • ✓ B.Entity integrity
  • C.Network integrity
  • D.File integrity
  • ✓ E.Domain integrity

Why A: Referential integrity (A) is a relational-database constraint that ensures a foreign key value in one table matches an existing primary key or unique value in the referenced table, preventing orphaned rows. Entity integrity (B) requires that every table have a primary key and that its values be unique and non-null, so each row is uniquely identifiable. Domain integrity (E) restricts a column's values to a defined set of valid data types, formats, ranges, or allowed values, typically enforced with CHECK constraints, data types, and NOT NULL. Network integrity (C) and file integrity (D) are not relational-database integrity types; they concern data transmission and file-level integrity (e.g., checksums), not the relational model's constraint categories.

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

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.