Question 220
At Cedarhaven Biotechnology, the FortiGate 7.6 security administration team encounters the following authorized operational case: a passive FortiGate VM starts after an active instance fails but cloud routes still target the failed virtual NIC. They need a defensible FortiOS configuration, diagnosis, validation or prevention decision. Which recurring review is most relevant to the same root risk?
Explanation
Correct Answer
Test cloud API permissions and route-switch timing regularly. This recurring practice addresses cloud fortigate ha route update because cloud routes and interface attachments may require explicit control-plane updates after firewall failover. It reinforces the supported change to implement the supported cloud HA failover automation and grant required scoped API permissions rather than relying on an unrelated periodic audit.
Incorrect Answers
Revalidate posture criteria when endpoint software changes reduces recurrence of sase device posture requirement, rather than the observed cloud fortigate ha route update issue. The relevant preventive control for Cedarhaven Biotechnology is: Test cloud API permissions and route-switch timing regularly. This distinction matters because cloud routes and interface attachments may require explicit control-plane updates after firewall failover.
Review SSO certificates and access assignments before rotation reduces recurrence of identity sso onboarding, rather than the observed cloud fortigate ha route update issue. The relevant preventive control for Cedarhaven Biotechnology is: Test cloud API permissions and route-switch timing regularly. This distinction matters because cloud routes and interface attachments may require explicit control-plane updates after firewall failover.
Retain versioned protected backups with tested recovery instructions reduces recurrence of configuration backup before changes, rather than the observed cloud fortigate ha route update issue. The relevant preventive control for Cedarhaven Biotechnology is: Test cloud API permissions and route-switch timing regularly. This distinction matters because cloud routes and interface attachments may require explicit control-plane updates after firewall failover.