Which of the following sets of data would NOT be a good fit for storing in a single HubDB table?

A single HubDB table is designed to store related data in a structured format, similar to a spreadsheet. Storing product inventory, hex values for internal branding, and a vendor contact archive in one table is problematic because these are three distinct datasets with different fields and purposes. Combining them would lead to a table with many empty cells (sparse data) and make it difficult to manage, query, and maintain. The other options represent cohesive datasets suitable for a single table: Employee information: All fields (name, title, bio) relate to a single employee record. Dinner menu: All fields (dish name, description, price) relate to menu items. Cat adoption information: All fields (cat name, breed, age, description) relate to a single adoptable cat.