Cloud-based SCADA (IIoT) in SCADA systems - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to deploy the SCADA data collector service on the cloud.

SCADA systems

kubectl apply -f [1]

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

Ascada-collector.yaml

Bscada-collector.json

Ccollector-config.txt

Ddeploy.sh

Attempts:

3 left

💡 Hint

Common Mistakes

Using a JSON or script file instead of YAML for kubectl apply.

The kubectl apply -f command requires a YAML file describing the deployment. Here, scada-collector.yaml is the correct file.

2fill in blank

medium

Complete the command to check the status of the SCADA collector pods.

SCADA systems

kubectl get pods -l app=[1]

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

Adatabase

Bgateway

Ccollector

Dsensor

Attempts:

3 left

💡 Hint

Common Mistakes

Using unrelated labels like 'database' or 'sensor'.

The label app=collector selects pods related to the SCADA data collector service.

3fill in blank

hard

Fix the error in the command to expose the SCADA collector service on port 8080.

SCADA systems

kubectl expose deployment scada-collector --type=[1] --port=8080

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

AExternalName

BLoadBalancer

CNodePort

DClusterIP

Attempts:

3 left

💡 Hint

Common Mistakes

Using ClusterIP which is internal only.

To expose the service externally on port 8080, LoadBalancer type is used in cloud environments.

4fill in blank

hard

Fill both blanks to create a ConfigMap for SCADA collector settings.

SCADA systems

kubectl create configmap [1] --from-file=[2]

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

Ascada-config

Bcollector-settings.yaml

Cscada-collector

Dconfig.yaml

Attempts:

3 left

💡 Hint

Common Mistakes

Using deployment names instead of config names.

The ConfigMap is named scada-config and created from the file collector-settings.yaml.

5fill in blank

hard

Fill all three blanks to define a Kubernetes secret for SCADA credentials.

SCADA systems

kubectl create secret generic [1] --from-literal=[2]=[3]

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

Ascada-credentials

Busername

Cscada_user

Dpassword

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing secret name with key or value.

The secret is named scada-credentials and stores the literal username=scada_user.

Practice

1. What is the main advantage of using cloud-based SCADA systems in industrial settings?

easy

A. Requires physical presence at the factory to operate

B. Does not support real-time data updates

C. Only works with wired connections

D. Remote monitoring and control of machines via the internet

Solution

1. Step 1: Understand cloud-based SCADA purpose

   Cloud-based SCADA allows monitoring and controlling machines remotely using internet connectivity.

2. Step 2: Compare options

   Remote monitoring and control of machines via the internet correctly states remote control via internet. Options A, C, and D contradict the cloud-based approach.

3. Final Answer:

   Remote monitoring and control of machines via the internet -> Option D

4. Quick Check:

   Cloud SCADA = Remote control [OK]

Hint: Cloud SCADA means control machines from anywhere [OK]

Common Mistakes:

• Thinking cloud SCADA needs physical presence
• Assuming only wired connections work
• Believing cloud SCADA can't update data in real-time

2. Which protocol is commonly used to send sensor data from SCADA devices to the cloud?

easy

A. MQTT

B. FTP

C. HTTP

D. SMTP

Solution

1. Step 1: Identify common IIoT protocols

   MQTT is a lightweight messaging protocol designed for IoT and SCADA data transmission.

2. Step 2: Eliminate other protocols

   HTTP is general web protocol, FTP is for file transfer, SMTP is for email. MQTT fits SCADA sensor data best.

3. Final Answer:

   MQTT -> Option A

4. Quick Check:

   SCADA sensor data uses MQTT [OK]

Hint: MQTT is made for IoT messaging [OK]

Common Mistakes:

• Confusing FTP or SMTP as sensor data protocols
• Choosing HTTP which is less efficient for SCADA
• Not knowing MQTT is lightweight and fast

3. Given this MQTT topic subscription in a cloud SCADA system:
factory1/machineA/temperature
What data will the system receive?

medium

A. Temperature readings from machine A in factory 1

B. Humidity readings from machine A in factory 1

C. Temperature readings from all machines in factory 1

D. Control commands for machine A

Solution

1. Step 1: Analyze MQTT topic structure

   The topic 'factory1/machineA/temperature' specifies data from machine A's temperature sensor in factory 1.

2. Step 2: Match topic to data type

   Temperature readings from machine A in factory 1 matches temperature readings from machine A. Other options mention humidity, all machines, or commands, which don't match the topic.

3. Final Answer:

   Temperature readings from machine A in factory 1 -> Option A

4. Quick Check:

   Topic matches temperature data [OK]

Hint: Topic parts show source and data type [OK]

Common Mistakes:

• Confusing temperature with humidity
• Assuming topic covers all machines
• Thinking topic is for control commands

4. A cloud SCADA system fails to receive sensor data. The MQTT broker URL is set as mqtt://broker.example.com. What is the likely issue?

medium

A. The URL should use tcp:// instead of mqtt://

B. The URL should be http://broker.example.com

C. The broker URL must include a port number

D. The MQTT protocol is not supported for SCADA

Solution

1. Step 1: Check MQTT broker URL format

   MQTT URLs usually require a port number (e.g., 1883) to connect properly.

2. Step 2: Evaluate options

   The broker URL must include a port number correctly identifies missing port number. The URL should use tcp:// instead of mqtt:// is incorrect because mqtt:// is a valid scheme. The MQTT protocol is not supported for SCADA is false; MQTT is supported. The URL should be http://broker.example.com uses HTTP which is wrong for MQTT.

3. Final Answer:

   The broker URL must include a port number -> Option C

4. Quick Check:

   MQTT URL needs port [OK]

Hint: MQTT URLs need port number to connect [OK]

Common Mistakes:

• Changing mqtt:// to tcp:// incorrectly
• Using HTTP instead of MQTT protocol
• Assuming MQTT is unsupported in SCADA

5. You want to design a cloud SCADA system that scales automatically when more machines are added. Which cloud feature should you use?

hard

A. Manual server provisioning

B. Auto-scaling groups with MQTT brokers

C. Static IP addresses for each machine

D. Local data storage on each machine only

Solution

1. Step 1: Understand scalability needs

   Auto-scaling groups allow cloud resources to grow or shrink automatically based on demand.

2. Step 2: Match cloud feature to SCADA scaling

   Using auto-scaling with MQTT brokers supports dynamic machine additions. Manual provisioning and static IPs do not scale well. Local storage only limits cloud benefits.

3. Final Answer:

   Auto-scaling groups with MQTT brokers -> Option B

4. Quick Check:

   Auto-scaling = scalable SCADA [OK]

Hint: Auto-scaling adjusts resources automatically [OK]

Common Mistakes:

• Choosing manual provisioning which is slow
• Using static IPs that limit flexibility
• Relying only on local storage without cloud