Compliance reporting in SCADA systems - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to generate a compliance report header.

SCADA systems

report_header = "Compliance Report - [1]"

Drag options to blanks, or click blank then click option'

AReport

B2023-04-01

CApril 2023

DSystem

Attempts:

3 left

💡 Hint

Common Mistakes

Using just the year without month

Using a generic word like 'Report' instead of a date

The header should include the month and year for clarity, so "April 2023" fits best.

2fill in blank

medium

Complete the code to filter logs for compliance checks.

SCADA systems

filtered_logs = [log for log in logs if log['[1]'] == 'ERROR']

Drag options to blanks, or click blank then click option'

Astatus

Blevel

Ctype

Dmessage

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'status' which might not indicate severity

Using 'message' which is the log text, not the level

Logs usually have a 'level' field indicating severity like ERROR or INFO.

3fill in blank

hard

Fix the error in the code to generate a compliance summary.

SCADA systems

summary = {key: len([entry for entry in data if entry['status'] == '[1]']) for key in categories}

Drag options to blanks, or click blank then click option'

Acompliant

BCompliant

CCOMPLIANT

Dcompliance

Attempts:

3 left

💡 Hint

Common Mistakes

Using uppercase or capitalized versions that don't match data

Using unrelated words like 'compliance'

The status values are case-sensitive and usually lowercase like 'compliant'.

4fill in blank

hard

Fill both blanks to create a dictionary of non-compliant devices and their error counts.

SCADA systems

non_compliant = {device['[1]']: device['[2]'] for device in devices if device['status'] == 'non-compliant'}

Drag options to blanks, or click blank then click option'

Aid

Berror_count

Cname

Dstatus

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'name' as key which might not be unique

Using 'status' as value which is the same for all filtered devices

We want device IDs as keys and their error counts as values for non-compliant devices.

5fill in blank

hard

Fill all three blanks to generate a report dictionary with device names, error counts, and compliance status.

SCADA systems

report = [1](device['[2]']: {'errors': device['[3]'], 'status': device['status']} for device in device_list)

Drag options to blanks, or click blank then click option'

Adict

Bname

Cerror_count

Did

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'id' as key instead of 'name'

Not using dict() to create the dictionary

We use dict() to create the dictionary, device names as keys, and error counts as values in the nested dict.

Practice

1. What is the main purpose of compliance reporting in SCADA systems?

easy

A. To backup all system files automatically

B. To increase the speed of data processing

C. To reduce the number of sensors in the system

D. To prove the system follows safety and regulatory rules

Solution

1. Step 1: Understand compliance reporting

   Compliance reporting is about showing that the system meets required rules and standards.

2. Step 2: Identify the main goal

   The main goal is to prove the system follows safety and regulatory rules to ensure safe operation and legal compliance.

3. Final Answer:

   To prove the system follows safety and regulatory rules -> Option D

4. Quick Check:

   Compliance reporting = Prove rules followed [OK]

Hint: Compliance reports show rule-following, not speed or backups [OK]

Common Mistakes:

• Confusing compliance with performance optimization
• Thinking compliance reports reduce hardware
• Assuming compliance reports are for backups

2. Which command syntax correctly generates a compliance report for SCADA system 'PlantA' from 2024-01-01 to 2024-01-31 and saves it to '/reports/january.pdf'?

easy

A. generate_report --system PlantA --start 2024-01-01 --end 2024-01-31 --output /reports/january.pdf

B. report_generate -system=PlantA -from=2024-01-01 -to=2024-01-31 -file=/reports/january.pdf

C. createReport PlantA 2024-01-01 2024-01-31 /reports/january.pdf

D. make_report system=PlantA start=2024-01-01 end=2024-01-31 output=/reports/january.pdf

Solution

1. Step 1: Check command structure

   The correct command uses clear flags: --system, --start, --end, --output with proper values.

2. Step 2: Match syntax to options

   generate_report --system PlantA --start 2024-01-01 --end 2024-01-31 --output /reports/january.pdf matches the expected syntax exactly with correct flags and values.

3. Final Answer:

   generate_report --system PlantA --start 2024-01-01 --end 2024-01-31 --output /reports/january.pdf -> Option A

4. Quick Check:

   Correct flags and order = generate_report --system PlantA --start 2024-01-01 --end 2024-01-31 --output /reports/january.pdf [OK]

Hint: Look for double dashes and clear flag names [OK]

Common Mistakes:

• Using single dashes instead of double
• Mixing flag names or missing equals signs
• Wrong order or missing output path

3. Given the command generate_report --system PlantB --start 2024-02-01 --end 2024-02-28 --output /reports/february.pdf, what will be the expected result?

medium

A. A report for PlantB but only for one day, 2024-02-01

B. A PDF report for PlantB covering February 2024 saved at /reports/february.pdf

C. An error because the output path is missing

D. A CSV report instead of PDF

Solution

1. Step 1: Analyze command parameters

   The command specifies system PlantB, start and end dates for February 2024, and output file path ending with .pdf.

2. Step 2: Determine expected output

   The command should generate a PDF report for the full date range and save it to the given path.

3. Final Answer:

   A PDF report for PlantB covering February 2024 saved at /reports/february.pdf -> Option B

4. Quick Check:

   Correct dates and output path = PDF report [OK]

Hint: Check date range and output file extension carefully [OK]

Common Mistakes:

• Assuming output path is missing or wrong
• Thinking report covers only one day
• Confusing file format from extension

4. You run the command generate_report --system PlantC --start 2024-03-01 --end 2024-02-28 --output /reports/march.pdf but get an error. What is the most likely cause?

medium

A. The output file path is invalid

B. The system name PlantC is not recognized

C. The end date is before the start date

D. The command is missing the --format flag

Solution

1. Step 1: Check date parameters

   The start date is 2024-03-01 but the end date is 2024-02-28, which is before the start date.

2. Step 2: Identify error cause

   Most systems reject date ranges where the end date is earlier than the start date, causing an error.

3. Final Answer:

   The end date is before the start date -> Option C

4. Quick Check:

   End date < start date = Error [OK]

Hint: Check if end date is after start date [OK]

Common Mistakes:

• Ignoring date order and assuming output path error
• Assuming system name error without checking dates
• Thinking a missing format flag causes this error

5. You need to automate monthly compliance reports for three SCADA systems: PlantX, PlantY, and PlantZ. Which approach best ensures reports are generated correctly and saved with clear filenames?

hard

A. Write a script that loops over system names and dates, generating reports with filenames like 'PlantX_2024-04.pdf'

B. Manually run the generate_report command for each system every month

C. Generate one report for all systems combined without separate files

D. Use a single command with all system names and one output file

Solution

1. Step 1: Understand automation needs

   Automating means using a script to repeat commands for each system and date range.

2. Step 2: Choose clear file naming

   Using filenames with system name and date like 'PlantX_2024-04.pdf' keeps reports organized and easy to find.

3. Final Answer:

   Write a script that loops over system names and dates, generating reports with filenames like 'PlantX_2024-04.pdf' -> Option A

4. Quick Check:

   Automation + clear filenames = Write a script that loops over system names and dates, generating reports with filenames like 'PlantX_2024-04.pdf' [OK]

Hint: Automate with loops and clear file names [OK]

Common Mistakes:

• Running commands manually each month
• Combining all systems into one report file
• Using unclear or generic filenames