b$.$ Predict what data they store in the second row.

c$.$ Predict what kinds of queries or requests for data are made by the system in the third row. We$$re not looking for a specific SQL query or command. It$$s important here to have a specific system$/$database in mind $($a$),$ with specific types of data $($b$).$ Think about the system $($a$)$ and the data $($b$)$ and various users $($or applications$)$ that access that data. For example, as an online bank customer, what kinds of data queries$/$requests might I want to know about my account with that bank? As an HR manager in a large company, what kinds of data $($b$)$ might be interesting to retain about employees in an employee database $($a$)$ and what kinds of data queries$/$request might be common on that data? OK$,$ now that you$$ve been given two examples $($an online banking example and an employee database example$),$ you may use ONE of these examples in your table below but not BOTH. Please develop at least two additional, different examples. A Banking example and an Employee Database example should NOT both appear in your table below.

Data Table

$($a$)$

Systems $($sites$/$apps$)$ Accessed $(1)$

$(2)(3)$

$($b$)$

Types of data stored

$($c$)$

Kinds of data queries$/$ requests