Risk monitoring and control in Software Engineering - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary purpose of risk monitoring in DevOps?

Choose the best description of the main goal of risk monitoring in a DevOps environment.

A To continuously track identified risks and detect new risks during the project lifecycle

B To eliminate all risks before starting any deployment

C To document risks only at the beginning of the project without updates

D To assign blame when risks cause failures

💡 Hint

Think about how risks change over time and what monitoring helps with.

Risk monitoring is about keeping an eye on known risks and spotting new ones as the project moves forward, so teams can respond quickly.

💻 Command Output

intermediate

What is the output of this command for checking risk status in a CI/CD pipeline?

Given the command riskctl status --pipeline=deploy, what output indicates that no critical risks are currently active?

A Warning: riskctl command deprecated

B Error: pipeline deploy not found

C Pipeline deploy: No critical risks detected. All checks passed.

D Pipeline deploy: 3 critical risks active

💡 Hint

Look for a message that confirms no critical risks are present.

The output stating no critical risks and all checks passed means the pipeline is currently safe to proceed.

🔀 Workflow

advanced

Which step correctly follows risk identification in a DevOps risk control workflow?

After identifying risks in a DevOps project, what is the next step to effectively control those risks?

A Ignoring low priority risks to save time

B Deploying code immediately without further checks

C Deleting the risk records to avoid confusion

D Risk analysis to evaluate the impact and likelihood of each risk

💡 Hint

Think about what you need to understand about risks before deciding how to handle them.

Risk analysis helps prioritize risks by understanding their potential impact and likelihood, guiding control actions.

❓ Troubleshoot

advanced

Why might a risk monitoring tool fail to alert on a new critical risk?

Identify the most likely cause why a risk monitoring tool does not send alerts for a newly detected critical risk.

A The risk monitoring tool is designed to ignore critical risks

B The alerting rules were not updated to include the new risk category

C The new risk is not actually critical and does not require alerts

D The tool only sends alerts once per project lifecycle

💡 Hint

Consider how alerting systems depend on configuration to detect specific risks.

If alerting rules do not cover the new risk category, the tool will not trigger alerts for it.

✅ Best Practice

expert

What is the best practice for integrating risk control in an automated deployment pipeline?

Choose the best practice to ensure risk control is effective within an automated deployment pipeline.

A Incorporate automated risk assessment checks that block deployment if critical risks are detected

B Disable risk controls during peak deployment hours to avoid delays

C Run risk assessments manually after deployment to save time

D Only assess risks once at the start of the project and never update

💡 Hint

Think about how automation can help prevent risky deployments.

Automated risk checks that can block deployment help catch issues early and prevent problems in production.

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