A critical AI system cannot be shut down and must remain secure.

Option B is correct because patching critical vulnerabilities directly removes or reduces known exploitable weaknesses while allowing the essential AI service to remain available. The organization should prioritize patches according to exploitability and impact, test them in a representative environment, use redundancy or rolling deployment where possible, and verify that remediation succeeded. Option A would weaken confidentiality and create an additional security exposure; encryption is not the obstacle to secure continuous operation. Option C is valuable as a detective control because log analysis can reveal abnormal activity, but it does not remediate a known critical vulnerability. Option D redeploys the production model, which may restore model files or configuration, but it does not necessarily update the vulnerable operating system, library, container, API, or orchestration component. For a system that cannot be shut down, the correct strategy is controlled patch management supported by high availability, maintenance coordination, monitoring, and rollback capability. NIST describes enterprise patch management as preventive maintenance that reduces the likelihood of compromise, breaches, and operational disruption.

================