Risk monitoring and control in Software Engineering - Step-by-Step Execution

Concept Flow - Risk monitoring and control

Identify Risks

↓

Set Risk Metrics

↓

Monitor Risks

↓

Analyze Risk Data

↓

Implement Controls

↓

Review Effectiveness

↓

Adjust Controls

This flow shows how risks are identified, monitored, controlled, and reviewed continuously to keep projects safe.

Execution Sample

Software Engineering

1. Identify risk: 'Server downtime'
2. Set metric: downtime < 1 hour/month
3. Monitor: track downtime daily
4. Analyze: downtime = 2 hours last week
5. Control: add backup server
6. Review: downtime reduced to 0.5 hour

This example traces how a risk of server downtime is monitored and controlled step-by-step.

Analysis Table

Step	Action	Risk Metric	Observed Value	Control Action	Result
1	Identify risk	N/A	Server downtime	N/A	Risk documented
2	Set risk metric	Downtime < 1 hour/month	N/A	N/A	Metric set
3	Monitor risk	Downtime < 1 hour/month	Downtime tracked daily	N/A	Data collected
4	Analyze data	Downtime < 1 hour/month	2 hours last week	N/A	Risk threshold breached
5	Implement control	Downtime < 1 hour/month	2 hours last week	Add backup server	Control applied
6	Review effectiveness	Downtime < 1 hour/month	0.5 hour last week	N/A	Risk reduced below threshold
7	Adjust controls if needed	Downtime < 1 hour/month	0.5 hour last week	N/A	No adjustment needed

💡 Risk controlled successfully; downtime reduced below threshold

State Tracker

Variable	Start	After Step 3	After Step 4	After Step 6	Final
Risk Metric	Not set	Downtime < 1 hour/month	Downtime < 1 hour/month	Downtime < 1 hour/month	Downtime < 1 hour/month
Observed Downtime	N/A	Tracked daily	2 hours last week	0.5 hour last week	0.5 hour last week
Control Action	None	None	None	Backup server added	Backup server added

Key Insights - 3 Insights

Why do we keep monitoring risk even after implementing controls?

Because controls may not fully eliminate risk immediately; monitoring (see step 6) shows if controls work or need adjustment.

What happens if observed risk value is below the metric?

It means risk is under control (step 6 shows downtime reduced to 0.5 hour, below 1 hour limit). No further action needed unless conditions change.

Why set a risk metric before monitoring?

A metric (step 2) defines what level of risk is acceptable, so monitoring can detect when risk exceeds that level and triggers control actions.

Visual Quiz - 3 Questions

Look at the execution table, at which step is the risk threshold first breached?

A Step 5

B Step 3

C Step 4

D Step 6

💡 Hint

Check the 'Result' column for 'Risk threshold breached' in the execution table.

According to the variable tracker, what is the observed downtime after step 6?

A 0.5 hour last week

B Not tracked

C 2 hours last week

D 1 hour last week

💡 Hint

Look at the 'Observed Downtime' row under 'After Step 6' in the variable tracker.

If the control action was not implemented at step 5, what would likely happen at step 6?

A Downtime would reduce below threshold

B Downtime would remain above threshold

C Risk metric would change

D Risk would be ignored

💡 Hint

Refer to the execution table where control action at step 5 reduces downtime by step 6.

Concept Snapshot

Risk Monitoring and Control:
1. Identify risks early.
2. Set clear risk metrics.
3. Monitor risk data regularly.
4. Analyze if risk exceeds limits.
5. Apply controls to reduce risk.
6. Review and adjust controls continuously.

Full Transcript

Risk monitoring and control is a continuous process. First, risks are identified and documented. Then, clear metrics define acceptable risk levels. Monitoring collects data to see if risks stay within limits. If risks exceed thresholds, controls are applied to reduce them. Finally, effectiveness is reviewed and controls adjusted as needed to keep risks managed.

Practice

1. What is the main goal of risk monitoring and control in DevOps projects?

easy

A. To ignore risks until they cause problems

B. To create risks so the team can practice handling them

C. To document risks once at the start and never update

D. To continuously watch risks and act quickly to reduce their impact

Solution

1. Step 1: Understand risk monitoring purpose

   Risk monitoring means watching risks regularly to see if they change or get worse.

2. Step 2: Identify the correct goal

   The goal is to act fast to reduce risk impact, not ignore or create risks.

3. Final Answer:

   To continuously watch risks and act quickly to reduce their impact -> Option D

4. Quick Check:

   Risk monitoring = watch and act fast [OK]

Hint: Risk monitoring means watch and act fast, not ignore [OK]

Common Mistakes:

• Thinking risk monitoring means ignoring risks
• Believing risks should be created intentionally
• Assuming risks are documented once and never updated

2. Which of the following commands is commonly used to check the status of running services for risk monitoring in a Linux environment?

easy

A. docker build

B. git commit

C. systemctl status

D. kubectl apply

Solution

1. Step 1: Identify commands related to service status

   In Linux, systemctl status shows the current status of system services.

2. Step 2: Eliminate unrelated commands

   git commit is for version control, docker build builds images, kubectl apply manages Kubernetes resources.

3. Final Answer:

   systemctl status -> Option C

4. Quick Check:

   Check service status = systemctl status [OK]

Hint: Use systemctl status to check Linux services quickly [OK]

Common Mistakes:

• Confusing git commands with system monitoring
• Using docker build instead of status commands
• Mixing Kubernetes commands with local service checks

3. Given this snippet of a monitoring script output:

ALERT: Disk space usage at 92% on /dev/sda1
ACTION: Trigger cleanup script
STATUS: Cleanup completed successfully
ALERT: CPU usage at 85%

What is the next logical step in risk control?

medium

A. Ignore the CPU alert since cleanup was successful

B. Investigate and reduce CPU usage to prevent overload

C. Reboot the server immediately without checking

D. Delete all logs to free disk space

Solution

1. Step 1: Analyze the alerts and actions

   The disk space alert was handled by cleanup successfully, but CPU usage is still high at 85%.

2. Step 2: Decide the correct risk control action

   Ignoring CPU alert risks overload; rebooting immediately or deleting logs are extreme or unsafe actions.

3. Final Answer:

   Investigate and reduce CPU usage to prevent overload -> Option B

4. Quick Check:

   High CPU alert = investigate and reduce [OK]

Hint: Address each alert; don't ignore new ones after fixing old [OK]

Common Mistakes:

• Ignoring new alerts after fixing previous ones
• Taking drastic actions without investigation
• Deleting logs which may be needed for diagnosis

4. You have a monitoring script that should alert when memory usage exceeds 80%, but it never triggers alerts even when usage is 90%. What is the most likely cause?

medium

A. The alert threshold is set incorrectly above 90%

B. The script is missing execution permissions

C. The monitoring tool is not installed

D. The server has no memory usage

Solution

1. Step 1: Check alert threshold settings

   If alerts never trigger at 90%, the threshold might be set higher than 90%, so condition never met.

2. Step 2: Evaluate other options

   Missing permissions or tool not installed would cause no script run or errors, not silent no alerts. Server always uses some memory.

3. Final Answer:

   The alert threshold is set incorrectly above 90% -> Option A

4. Quick Check:

   Alerts not triggering = check threshold settings [OK]

Hint: Check alert thresholds first if alerts never trigger [OK]

Common Mistakes:

• Assuming script permission issues without checking thresholds
• Thinking server can have zero memory usage
• Ignoring tool installation status

5. In a DevOps pipeline, you want to implement risk monitoring that automatically pauses deployment if test failures exceed 5%. Which combination of tools and steps best achieves this?

hard

A. Use a CI tool with test reports and configure a gate to stop deployment on failure threshold

B. Manually check test logs after deployment and rollback if needed

C. Deploy first, then run tests and notify team by email only

D. Ignore test failures and deploy continuously without checks

Solution

1. Step 1: Identify automated risk monitoring needs

   Automatic pause on failure requires integration of test results with deployment control.

2. Step 2: Choose correct tool and configuration

   CI tools can generate test reports and enforce gates to stop deployment if failures exceed limits.

3. Final Answer:

   Use a CI tool with test reports and configure a gate to stop deployment on failure threshold -> Option A

4. Quick Check:

   Automate risk control = CI gate on test failures [OK]

Hint: Use CI gates to auto-stop deployment on test failures [OK]

Common Mistakes:

• Relying on manual checks after deployment
• Running tests post-deployment without blocking
• Ignoring test failures completely