FC0-U71 Data and Database Fundamentals Practice Question

Answer analysis

Option-by-option breakdown

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

• ✗

  Simpler setup and configuration

  Why it's wrong here

  While a flat file might offer a more immediate and less involved initial setup for very basic data storage, databases introduce inherent complexity through their structured schema, query languages, and management overhead. This option is tempting because for trivial datasets or single-user applications where data integrity and complex relationships are not concerns, a flat file's direct accessibility can appear advantageous. However, this simplicity is precisely what databases overcome to provide robust data management.

• ✗

  Faster file transfer speeds

  Why it's wrong here

  Databases add indexing, query planning and transaction overhead, so bulk byte transfer is typically slower than reading a flat file sequentially. Faster transfer is the reason to choose flat files for simple log shipping or one-off exports, not a benefit databases provide over them.

• ✗

  Lower storage requirements

  Why it's wrong here

  Databases consume additional space for indexes, system catalogues, transaction logs and preallocated pages, so they generally exceed the flat file's raw footprint. Lower storage is precisely why flat files suit small, static datasets; databases trade space for concurrent access, integrity and query flexibility.

• ✓

  Support for concurrent multi-user access

  Why this is correct

  A database engine manages locking, transactions, and isolation so many users can read and write the same records simultaneously without overwriting each other. A flat file offers no such coordination, so concurrent edits corrupt or clobber data. This directly satisfies the stem's concurrent multi-user access benefit.

Go deeper

Related to this question