Data Mining Test

You are designing a data model for a healthcare system with the following requirements:

A: A separate table for each entity with foreign keys as specified, and a DoctorPatient table linking Doctors to Patients.
B: A separate table for each entity with foreign keys as specified, without additional tables.
C: A combined PatientDoctor table replacing Patient and Doctor, and separate tables for Appointment and Prescription.
D: A separate table for each entity with foreign keys, and a PatientPrescription table to track prescriptions directly linked to patients.
E: A single table combining Patient, Doctor, Appointment, and Prescription into one.
F: A separate table for each entity with foreign keys as specified, and an AppointmentDetails table linking Appointments to Prescriptions.

Look at the given ER diagram. What do you think is the least number of tables we would need to represent M, N, P, R1 and R2?

Consider a healthcare database with a table named PatientRecords that stores patient visit information. The table has the following attributes:

- VisitID
- PatientID
- PatientName
- DoctorID
- DoctorName
- VisitDate
- Diagnosis
- Treatment
- TreatmentCost

In this table:

- Each VisitID uniquely identifies a patient's visit and is associated with one PatientID.
- PatientID is associated with exactly one PatientName.
- Each DoctorID is associated with a unique DoctorName.
- TreatmentCost is a fixed cost based on the Treatment.

Evaluating the PatientRecords table, which of the following statements most accurately describes its normalization state and the required actions for higher normalization?

A: The table is in 1NF. To achieve 2NF, remove partial dependencies by separating Patient information (PatientID, PatientName) and Doctor information (DoctorID, DoctorName) into different tables.
B: The table is in 2NF. To achieve 3NF, remove transitive dependencies by creating separate tables for Patients (PatientID, PatientName), Doctors (DoctorID, DoctorName), and Visits (VisitID, PatientID, DoctorID, VisitDate, Diagnosis, Treatment, TreatmentCost).
C: The table is in 3NF. To achieve BCNF, adjust for functional dependencies such as moving DoctorName to a separate Doctors table.
D: The table is in 1NF. To achieve 3NF, create separate tables for Patients, Doctors, and Visits, and remove TreatmentCost as it is a derived attribute.
E: The table is in 2NF. To achieve 4NF, address any multi-valued dependencies by separating Visit details and Treatment details.
F: The table is in 3NF. To achieve 4NF, remove multi-valued dependencies related to VisitID.

Based on the ER diagram, which of the following statements is accurate and requires specific knowledge of the ER diagram's details?

A: A Student can major in multiple Departments.
B: An Instructor can belong to multiple Departments.
C: A Course can be offered by multiple Departments.
D: Enrollment records can link a Student to multiple Courses in a single semester.
E: Each Course must be associated with an Enrollment record.
F: A Department can offer courses without having any instructors.

A data engineer is tasked with merging and transforming data from two sources for a business analytics report. Source 1 is a SQL database 'Employee' with fields EmployeeID (int), Name (varchar), DepartmentID (int), and JoinDate (date). Source 2 is a CSV file 'Department' with fields DepartmentID (int), DepartmentName (varchar), and Budget (float). The objective is to create a summary table that lists EmployeeID, Name, DepartmentName, and YearsInCompany. The YearsInCompany should be calculated based on the JoinDate and the current date, rounded down to the nearest whole number. Consider the following initial SQL query:

Which of the following modifications ensures accurate data transformation as per the requirements?

A: Change FLOOR to CEILING in the calculation of YearsInCompany.
B: Add WHERE e.JoinDate IS NOT NULL before the JOIN clause.
C: Replace JOIN with LEFT JOIN and use COALESCE(d.DepartmentName, 'Unknown').
D: Change the YearsInCompany calculation to YEAR(CURRENT_DATE) - YEAR(e.JoinDate).
E: Use DATEDIFF(YEAR, e.JoinDate, CURRENT_DATE) for YearsInCompany calculation.

Jaylo is hired as Data warehouse engineer at Affflex Inc. Jaylo is tasked with designing an ETL process for loading data from SQL server database into a large fact table. Here are the specifications of the system:

1. Orders data from SQL to be stored in fact table in the warehouse each day with prior day’s order data
2. Loading new data must take as less time as possible
3. Remove data that is more then 2 years old
4. Ensure the data loads correctly
5. Minimize record locking and impact on transaction log

Which of the following should be part of Jaylo’s ETL design?

A: Partition the destination fact table by date
B: Partition the destination fact table by customer
C: Insert new data directly into fact table
D: Delete old data directly from fact table
E: Use partition switching and staging table to load new data
F: Use partition switching and staging table to remove old data

In an ETL process designed for a retail company, a complex SQL transformation is applied to the 'Sales' table. The 'Sales' table has fields SaleID, ProductID, Quantity, SaleDate, and Price. The goal is to generate a report that shows the total sales amount and average sale amount per product, aggregated monthly. The following SQL code snippet is used in the transformation step:

What specific function does this SQL code perform in the context of the ETL process, and how does it contribute to the reporting goal?

A: The code calculates the total and average sales amount for each product annually.
B: It aggregates sales data by month and product, computing total and average sales amounts.
C: This query generates a daily breakdown of sales, both total and average, for each product.
D: The code is designed to identify the best-selling products on a monthly basis by sales amount.
E: It calculates the overall sales and average price per product, without considering the time dimension.

Silverman Sachs is a trading firm and deals with daily trade data for various stocks. They have the following fact table in their data warehouse:

Table: Trades
Indexes: None
Columns: TradeID, TradeDate, Open, Close, High, Low, Volume

Here are three common queries that are run on the data:

Dhavid Polomon is hired as an ETL Developer and is tasked with implementing an indexing strategy for the Trades fact table. Here are the specifications of the indexing strategy:

- All three common queries must use a columnstore index
- Minimize number of indexes
- Minimize size of indexes

Which of the following strategies should Dhavid pick:

A: Create three columnstore indexes: 
1. Containing TradeDate and Close
2. Containing TradeDate, High and Low
3. Container TradeDate and Volume

B: Create two columnstore indexes:
1. Containing TradeID, TradeDate, Volume and Close
2. Containing TradeID, TradeDate, High and Low

C: Create one columnstore index that contains TradeDate, Close, High, Low and Volume

D: Create one columnstore index that contains TradeID, Close, High, Low, Volume and Trade Date