Consequence of diminished data integrity: impacted operations

Tip: Choose Save as PDF in the print dialog to download. Use A4 paper size.

Consequence of diminished data integrity: impacted operations

Name:
Date:
Class:

Quick Questions

Shade in the A or B circle for each question.

1. A warehouse database shows the wrong stock counts, so orders are shipped late. Which consequence of poor data integrity is this?
A Regulatory compliance
B Impacted operations
2. Which is an example of impacted operations caused by poor data integrity?
A A system is taken offline for hours so staff can fix corrupted records
B A firewall blocks an unknown IP address
3. True or false: When data is inaccurate, staff often spend extra time checking and correcting records instead of doing their normal work.
A False
B True
4. A customer's address is recorded wrongly, so their parcel is sent to the wrong suburb and has to be re-sent. What is the main operational impact?
A A delayed order
B A stronger password policy
5. Which statement best describes why an IT team might shut down a system after finding corrupted data?
A To stop errors spreading while the data is repaired
B To make the data more confidential

Match the Pairs

Draw a line connecting each item on the left to its match on the right.

Left columnRight column
1impacted operations AA system is taken out of service while staff fix corrupted or incorrect records
2system offline for data repair Bstaff time lost
3Incorrect addresses in customer records cause parcels to be sent late or to the wrong place CPoor data integrity disrupts daily business, causing delays, errors and wasted effort
4Staff must manually check and correct unreliable records instead of doing their normal work Ddelayed orders
5Poor data integrity only affects reports, so daily operations carry on as normal ESystems taken offline stop staff from processing orders or accessing records, so operations are disrupted.
6Taking a system offline to fix data errors has no effect on the business FPoor data integrity also disrupts daily operations, causing delays, errors and system shutdowns, not just reports.

Definitions

impacted operations

Fill in the Blanks

Complete each line of code by filling in the missing parts.

1.
Poor data integrity ________ operations
2.
Wrong addresses cause _______ orders
3.
Systems taken _______ to fix data errors
4.
Staff ____ is lost correcting records
5.
Impacted operations is a ___________ of diminished data integrity

Spot the Error

Shade in the letter of the line that contains an error.

Question 1
A orders = 120
B bad_records = 15
C good_orders = orders - bad_records
D shipped = orders
E print(shipped)
Question 2
A minutes_per_fix = 6
B errors = 40
C total = minutes_per_fix * errors
D hours = total * 60
E print(hours)
Question 3
A errors = 25
B limit = 20
C if errors < limit:
D print("System offline")
Question 4
A order = {"id": 7, "bad": True}
B if order["bad"]:
C order["status"] == "Delayed"
D print(order["status"])
Question 5
A orders_per_day = 50
B delay_days = 3
C backlog = orders_per_day + delay_days
D print("Backlog:", backlog)

Answer Key

Consequence of diminished data integrity: impacted operations
Section A: Quick Questions
Q1
B — Impacted operations
Q2
A — A system is taken offline for hours so staff can fix corrupted records
Q3
B — True
Q4
A — A delayed order
Q5
A — To stop errors spreading while the data is repaired
Section B: Match the Pairs
Q1
impacted operations → Poor data integrity disrupts daily business, causing delays, errors and wasted effort
Q2
system offline for data repair → A system is taken out of service while staff fix corrupted or incorrect records
Q3
Incorrect addresses in customer records cause parcels to be sent late or to the wrong place → delayed orders
Q4
Staff must manually check and correct unreliable records instead of doing their normal work → staff time lost
Q5
Poor data integrity only affects reports, so daily operations carry on as normal → Poor data integrity also disrupts daily operations, causing delays, errors and system shutdowns, not just reports.
Q6
Taking a system offline to fix data errors has no effect on the business → Systems taken offline stop staff from processing orders or accessing records, so operations are disrupted.
Section C: Definitions
Q1
impacted operations — Poor data integrity disrupts daily business, causing delayed orders, systems taken offline to fix data errors, and staff time wasted checking and correcting records.
Section D: Fill in the Blanks
Q1
Poor data integrity disrupts operations
Q2
Wrong addresses cause delayed orders
Q3
Systems taken offline to fix data errors
Q4
Staff time is lost correcting records
Q5
Impacted operations is a consequence of diminished data integrity
Section E: Spot the Error
Q1
D — Orders with bad data are delayed while they are fixed, so they cannot be shipped. The line should be shipped = good_orders.
Q2
D — Staff time lost to fixing records is measured in minutes. To convert minutes to hours you divide by 60, so it should be hours = total / 60.
Q3
C — The system should be taken offline to fix data when the errors go above the limit. The condition should be errors > limit.
Q4
C — == only compares values, so the status is never set and the order is not marked as delayed. It should use = to assign the status.
Q5
C — The backlog is the orders that pile up each day of the delay, so the two values must be multiplied. It should be orders_per_day * delay_days.