Question 480
An emergency change is proposed for: A FortiGate SD-WAN hub is added to FortiSASE but the tenant does not show an approved device for private access integration. Which caution is most important for this specific change?
Explanation
Correct Answer
The most relevant caution is that a FortiGate serial registered elsewhere need not be authorized for this SASE tenant automatically. The case concerns a FortiGate SD-WAN hub is added to FortiSASE but the tenant does not show an approved device for private access integration. The safer path is to check supported hub onboarding, authorization state, device registration, and service prerequisites and then, after verification, to authorize and associate the correct hub in the supported FortiSASE SPA workflow. This is the closest caution because it addresses the failure mechanism instead of a generic issue from another security workflow.
Incorrect Answers
An ordinary FortiGate SD-WAN license should not be presumed sufficient for every secure-edge mode. The check concerns an ordinary FortiGate SD-WAN license should not be presumed sufficient for every secure-edge mode, not confirming that a FortiGate serial registered elsewhere need not be authorized for this SASE tenant automatically.
Public internet steering must not silently substitute for confidential private application transport. This assesses public internet steering must not silently substitute for confidential private application transport; it does not determine the reported condition—a FortiGate SD-WAN hub is added to FortiSASE but the tenant does not show an approved device for private access integration.
Drawing a backup hub in the architecture is not proof that route failover is functional. The case-specific requirement is confirming that a FortiGate serial registered elsewhere need not be authorized for this SASE tenant automatically, which that option does not establish.