Question 130
The deployment team is preparing a sign-off for: A FortiGate has correct SD-WAN members but DNS requests from clients fail because its forward policy blocks UDP and TCP 53. Which limitation or risk should it explicitly consider before approval?
Explanation
Correct Answer
The most relevant caution is that changing the default route cannot fix a firewall rule that explicitly denies required traffic. The case concerns a FortiGate has correct SD-WAN members but DNS requests from clients fail because its forward policy blocks UDP and TCP 53. The safer path is to inspect security policy matched to the SD-WAN zone and DNS traffic logs separately from routing and then, after verification, to permit only approved DNS services to authorized resolvers with appropriate inspection and NAT. This is the closest caution because it addresses the failure mechanism instead of a generic issue from another security workflow.
Incorrect Answers
A valid route cannot compensate for missing translation of private source addresses at an ISP boundary. The check concerns a valid route cannot compensate for missing translation of private source addresses at an ISP boundary, not confirming that changing the default route cannot fix a firewall rule that explicitly denies required traffic.
Policy-route precedence can make debugging only the SD-WAN rule misleading. This assesses policy-route precedence can make debugging only the SD-WAN rule misleading; it does not determine the reported condition—a FortiGate has correct SD-WAN members but DNS requests from clients fail because its forward policy blocks UDP and TCP 53.
A default SD-WAN route should not be expected to override a valid longer prefix. The case-specific requirement is confirming that changing the default route cannot fix a firewall rule that explicitly denies required traffic, which that option does not establish.