Question 450
Original Fortinet NSE5_SSE_AD-7.6 educational scenario: A remote warehouse uses a secondary internet link for updates but a local static DNS route still points through the primary ISP during outage. Which observable result would best verify the correction?
Explanation
Correct Answer
In this situation, a remote warehouse uses a secondary internet link for updates but a local static DNS route still points through the primary ISP during outage. The relevant technical mechanism is: Ancillary infrastructure destinations can depend on routes outside the main application path. The most direct diagnostic or implementation action is: Correct destination routes for the resolver and test DNS through the intended backup. A useful verification is: Names resolve and updates proceed after primary member failure. An ongoing safeguard is: Include essential support services in failover route matrices. This is the INTENDED choice for the strongest verification evidence. The issuer documents define the topic and product background, not the truth of this item-level intended key.
Incorrect Answers
The alternative verifies a different condition: A valid outbound route cannot compensate for missing return reachability. The current case instead depends on: Ancillary infrastructure destinations can depend on routes outside the main application path. Confirm that “Names resolve and updates proceed after primary member failure”.
That test belongs to another control with this basis: Member-probe reachability can differ from application route reachability. In the current case, the governing reason is: Ancillary infrastructure destinations can depend on routes outside the main application path. The direct verification is “Names resolve and updates proceed after primary member failure”.
This observation would test a different technical dependency: Broad destination classifications can fail to identify the specific application required. The current issue is governed by: Ancillary infrastructure destinations can depend on routes outside the main application path. Its decisive check is “Names resolve and updates proceed after primary member failure”.