Polling vs report-by-exception in SCADA systems - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Polling in SCADA Systems

In a SCADA system, what is the main characteristic of the polling communication method?

A Data is sent continuously without any request from the central system.

B Devices send data only when a change or event occurs.

C The central system regularly requests data from devices at fixed intervals.

D Devices send data only when manually triggered by an operator.

💡 Hint

Think about who initiates the data transfer and how often.

Polling means the central system asks devices for data regularly, regardless of changes.

🧠 Conceptual

intermediate

Report-by-Exception Behavior

What best describes the report-by-exception method in SCADA communication?

A Devices send data only when a monitored value changes beyond a set threshold.

B The central system continuously requests data from devices.

C Data is sent at fixed time intervals regardless of changes.

D Operators manually request data from devices when needed.

💡 Hint

Focus on when devices decide to send data.

Report-by-exception means devices send data only when something important changes.

✅ Best Practice

advanced

Choosing Between Polling and Report-by-Exception

Which scenario is best suited for using report-by-exception instead of polling in a SCADA system?

A Collecting temperature data every second for trend analysis.

B Monitoring a variable that rarely changes but requires immediate alerts when it does.

C Regularly checking the status of a device every minute regardless of changes.

D Manually requesting data from devices during maintenance.

💡 Hint

Think about when immediate notification is important and data changes are rare.

Report-by-exception is efficient for rare but critical changes needing quick alerts.

❓ Troubleshoot

advanced

Troubleshooting Data Delays in Polling

A SCADA system using polling experiences delays in detecting critical changes. What is a likely cause?

A Operators are manually requesting data too often.

B Devices are sending data too frequently, overwhelming the system.

C Report-by-exception is enabled, causing missed data.

D Polling interval is too long, causing slow detection of changes.

💡 Hint

Consider how often the system asks for data.

If polling happens too rarely, changes can be detected late, causing delays.

🔀 Workflow

expert

Optimizing SCADA Communication Workflow

In a large SCADA network, which workflow best balances network load and timely data updates?

A Use polling for critical variables with short intervals and report-by-exception for less critical variables.

B Use polling for all variables at the shortest possible interval.

C Use report-by-exception for all variables regardless of criticality.

D Manually poll devices only during scheduled maintenance.

💡 Hint

Think about mixing methods to optimize performance and responsiveness.

Combining polling for critical data and report-by-exception for others reduces load and keeps updates timely.

Practice

1. What is the main difference between polling and report-by-exception in SCADA systems?

easy

A. Polling sends data only on changes; report-by-exception requests data regularly.

B. Polling and report-by-exception both send data at fixed intervals.

C. Polling requests data regularly; report-by-exception sends data only on changes.

D. Polling uses less network bandwidth than report-by-exception.

Solution

1. Step 1: Understand polling behavior

   Polling means the system asks for data at fixed times, regardless of changes.

2. Step 2: Understand report-by-exception behavior

   Report-by-exception sends data only when there is a change or event to report.

3. Final Answer:

   Polling requests data regularly; report-by-exception sends data only on changes. -> Option C

4. Quick Check:

   Polling = regular requests, Report-by-exception = event-driven [OK]

Hint: Polling = ask often; report-by-exception = send only on change [OK]

Common Mistakes:

• Confusing which method sends data regularly
• Thinking both methods behave the same
• Assuming report-by-exception always uses more bandwidth

2. Which of the following is the correct syntax to configure polling interval in a SCADA system configuration file?

easy

A. polling-interval = 5 seconds

B. polling_interval = '5s' # Poll every 5 seconds

C. pollingInterval: 5sec

D. polling interval = 5s

Solution

1. Step 1: Identify correct syntax format

   Configuration files often use key = 'value' format with quotes for time strings.

2. Step 2: Check each option for syntax correctness

   polling_interval = '5s' # Poll every 5 seconds uses correct key, equals sign, and quotes with valid time unit '5s'. Others have syntax errors or invalid formats.

3. Final Answer:

   polling_interval = '5s' # Poll every 5 seconds -> Option B

4. Quick Check:

   Correct config syntax uses key = 'value' [OK]

Hint: Config keys use underscores and quotes for values [OK]

Common Mistakes:

• Using spaces instead of underscores in keys
• Missing quotes around time values
• Using colons instead of equals sign

3. Given this SCADA polling setup code snippet:

polling_interval = 10  # seconds
last_value = 100
current_value = 100
if current_value != last_value:
    send_report()
else:
    wait(polling_interval)

What will happen when this code runs?

medium

A. The code causes an error due to missing function definitions.

B. send_report() is never called because values are equal.

C. send_report() is called every 10 seconds regardless of value changes.

D. send_report() is called only if current_value changes from last_value.

Solution

1. Step 1: Analyze the condition

   The code compares current_value and last_value; if different, it calls send_report().

2. Step 2: Check values given

   Both values are 100, so condition is false; else branch waits for polling_interval.

3. Final Answer:

   send_report() is called only if current_value changes from last_value. -> Option D

4. Quick Check:

   Report sent only on value change [OK]

Hint: send_report() triggers only on value difference [OK]

Common Mistakes:

• Assuming send_report() runs every time
• Ignoring the if condition logic
• Thinking wait() causes an error

4. You have a SCADA system using report-by-exception, but it never sends updates even when values change. What is the most likely cause?

medium

A. Exception reporting is disabled or misconfigured.

B. The system is polling too frequently.

C. Network bandwidth is too high.

D. Polling interval is set too low.

Solution

1. Step 1: Understand report-by-exception behavior

   It sends data only when exceptions or changes occur and reporting is enabled.

2. Step 2: Identify cause of no updates

   If no updates are sent despite changes, reporting is likely disabled or misconfigured.

3. Final Answer:

   Exception reporting is disabled or misconfigured. -> Option A

4. Quick Check:

   Disabled reporting stops updates [OK]

Hint: Check if exception reporting is enabled first [OK]

Common Mistakes:

• Confusing polling interval with report-by-exception
• Assuming high bandwidth stops updates
• Thinking frequent polling affects exception reporting

5. A SCADA system monitors temperature sensors. To reduce network load but ensure critical alerts are sent immediately, which approach is best?

hard

A. Use report-by-exception for normal data and polling for critical alerts.

B. Use report-by-exception only, ignoring polling.

C. Use polling only with a very short interval.

D. Use polling with a long interval and no exception reporting.

Solution

1. Step 1: Analyze network load and alert needs

   Polling often increases network load; report-by-exception reduces it by sending only changes.

2. Step 2: Combine methods for best result

   Using report-by-exception for normal data saves bandwidth, while polling ensures critical alerts are checked regularly.

3. Final Answer:

   Use report-by-exception for normal data and polling for critical alerts. -> Option A

4. Quick Check:

   Combine polling and exception reporting for efficiency [OK]

Hint: Mix polling and exception reporting for best balance [OK]

Common Mistakes:

• Using polling only causes high network load
• Ignoring critical alert needs
• Relying solely on report-by-exception may miss urgent data