0
0
SCADA systemsdevops~10 mins

Why historical data storage matters in SCADA systems - Test Your Understanding

Choose your learning style9 modes available
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to store sensor data in the historical database.

SCADA systems
database.insert([1])
Drag options to blanks, or click blank then click option'
Asensor_data
Bcurrent_time
Cdevice_status
Derror_log
Attempts:
3 left
💡 Hint
Common Mistakes
Using current_time instead of the actual data to store.
2fill in blank
medium

Complete the code to retrieve historical data for analysis.

SCADA systems
historical_data = database.query('SELECT * FROM records WHERE timestamp [1] start_time')
Drag options to blanks, or click blank then click option'
A>=
B<=
C!=
D==
Attempts:
3 left
💡 Hint
Common Mistakes
Using <=' which would get records before the start time.
3fill in blank
hard

Fix the error in the code to archive old historical data.

SCADA systems
archive_data = database.extract('SELECT * FROM records WHERE timestamp [1] cutoff_date')
Drag options to blanks, or click blank then click option'
A>
B==
C<
D!=
Attempts:
3 left
💡 Hint
Common Mistakes
Using > which selects newer data instead of old data.
4fill in blank
hard

Fill both blanks to filter and store only valid historical data.

SCADA systems
valid_data = {record: record[1]2 for record in data if record.status [2] 'valid'}
Drag options to blanks, or click blank then click option'
A**
B==
C!=
D//
Attempts:
3 left
💡 Hint
Common Mistakes
Using != instead of == for filtering valid records.
5fill in blank
hard

Fill all three blanks to create a summary dictionary of historical data counts.

SCADA systems
summary = [1]: len(records) for [2], records in grouped_data.items() if [3] > 0}
Drag options to blanks, or click blank then click option'
Acategory
Clen(records)
Dcount
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'count' instead of 'len(records)' for filtering.