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.