Which of the following would work BEST stored as a flat file rather than stored in a database?
Which of the following would work BEST stored as a flat file rather than stored in a database?
Directions to a doctor's office are typically simple and concise text or map-based data that do not require frequent updates, complex queries, or relational data management. Such data can be easily stored and retrieved as a flat file. In contrast, a contact list, movie theater locations, and store inventory contain multiple attributes and might require more complex searching, sorting, and updating capabilities, making them more suitable for storage in a database.
Is this the correct answer? I feel like C is more applicable. What am I missing?
Directions to a specific location, such as a doctor's office, are usually simple textual or map-based data that doesn't require frequent updates or complex queries, Hence direction to the doctors office is the best and right answer. A contact list can include multiple fields (e.g., name, address, phone number) and may need to be queried or sorted. A database is more suitable for efficiently managing and retrieving contact information. Movie theater Locations data may include multiple attributes (e.g., address, showtimes, seating capacity) and could benefit from a database for easier management and searching. Store Inventory data often involves multiple attributes (e.g., product ID, description, quantity, price) and requires frequent updates, querying, and reporting. A database is well-suited for this purpose.
directions to the office would be something you would literally print out and take with you the one time you needed it. it wouldnt change, receive frequent additions or updates, and it isn't a list like all of the other three choices.
A, is relevant because flat files contain simple information that are simply stored and dont contain complex directions. Directions layed out to the doctors office would be too much now would it.
I also think the answer should be C
this should only have two factor need to store, so this should be the right answer
is CSV
contact list
If I had to choose two would be A and C, but since it's a single answer I lean to C. The wording is not clear enough and too vague. For example, contact lists may have names, phones, emails, locations, notes, work, type of contact (e.g. friend, colleague etc.), notes etc. and you can group them. On the other hand directions to a place seem more appropriate to be a flat file, so you have a list of doctors and the directions. Nevertheless, both can be complex so...
Contact list is the answer. Your storing contact list for individuals not a company. The other provided answers would require a relational DB.
Both contact list or doctors directions. Now depending on how many doctors and how many doctor locations? Some doctor's have multiple locations, If you're talking about many doctors and many locations you would need a structure DB.
A because contacts list can be stored in a simple and single tabular structure.
Feels more like the directions to the doctors office would be better stored as a flat file. A flat file is typically unstructured and all the other possibilities lend themselves to a database structure. Contacts lists are names, addresses and phone numbers which a database is very well suited to.
I feel the answer should be C