Question 460
During an authorized lab exercise for a logistics site where routing and SD-WAN services have separate responsibilities, a reviewer needs proof the deployment can pin a specific business application to a preferred transport independent of dynamic quality ranking. Which observation most directly validates it?
- The SD-WAN rule matches the designated Internet Service Database object.
- The relevant service rule includes the exact partner destination address object.
- The matching service displays Manual mode and the chosen ordered member list.
- The selected member passes SLA and has the lowest cost among qualified paths.
Explanation
Correct Answer
C:This checks ‘Use a manual SD-WAN strategy’ at the correct operational boundary: the Manual strategy respects an administrator-specified interface preference list of eligible SD-WAN members. It demonstrates the specific capability to pin a specific business application to a preferred transport independent of dynamic quality ranking in a logistics site where routing and SD-WAN services have separate responsibilities; deployment should additionally respect the constraint: Manual member preference remains subject to route availability and any needed firewall permission.
Incorrect Answers
A:That observation belongs to ‘Match an Internet Service Database destination’, not ‘Use a manual SD-WAN strategy’; its purpose is to identify cloud-service traffic by maintained service definitions instead of a static destination IP, the underlying behavior is that internet service matching can steer flows associated with a known internet service without manually maintaining every destination subnet. The reviewer is instead verifying ‘Use a manual SD-WAN strategy’ for a logistics site where routing and SD-WAN services have separate responsibilities, not the evidence produced by ‘Match an Internet Service Database destination’.
B:That observation belongs to ‘Match destination address in an SD-WAN rule’, not ‘Use a manual SD-WAN strategy’; its purpose is to direct traffic to a particular partner subnet over an overlay while other traffic uses internet DIA, the underlying behavior is that destination-address matching distinguishes route candidates for a specified network target. The reviewer is instead verifying ‘Use a manual SD-WAN strategy’ for a logistics site where routing and SD-WAN services have separate responsibilities, not the evidence produced by ‘Match destination address in an SD-WAN rule’.
D:That observation belongs to ‘Use Lowest Cost with an SLA target’, not ‘Use a manual SD-WAN strategy’; its purpose is to send a service on the cheapest circuit that still meets quality objectives, the underlying behavior is that Lowest Cost chooses the smallest configured member cost among those that satisfy the selected SLA. The reviewer is instead verifying ‘Use a manual SD-WAN strategy’ for a logistics site where routing and SD-WAN services have separate responsibilities, not the evidence produced by ‘Use Lowest Cost with an SLA target’.
Question 461
At an IT team managing both BYOD browsers and corporate FortiClient installations, a controlled test reveals that an unmanaged browser can reach web pages but no traffic reaches the cloud web proxy. Which setting is the strongest first lead?
- Investigate: Configure SAML single sign-on
- Investigate: Configure agentless proxy SSO
- Investigate: Enroll an agentless web user
- Investigate: Import users through LDAP
Explanation
Correct Answer
C:The symptom identifies the missing operational behavior: agentless secure web gateway access uses explicit proxy steering rather than a full-device agent tunnel. For an IT team managing both BYOD browsers and corporate FortiClient installations, a direct diagnostic confirmation would be that browser web requests traverse the configured FortiSASE SWG proxy; during repair, agentless proxy steering does not automatically tunnel all nonweb IP traffic.
Incorrect Answers
A:FortiSASE acts as a SAML service provider while the configured IdP issues assertions for authenticated users, which serves the different requirement to let staff authenticate to FortiSASE through the corporate identity provider instead of the behavior delivered by ‘Enroll an agentless web user’. If that component were misconfigured, a more characteristic finding would be that redirect-based identity login cannot complete because the SP and IdP trust are not aligned; the actual report concerns an unmanaged browser can reach web pages but no traffic reaches the cloud web proxy at an IT team managing both BYOD browsers and corporate FortiClient installations.
B:SWG SSO authenticates a web proxy session using the configured identity provider, which serves the different requirement to associate proxied browser traffic with enterprise user identity during secure web gateway inspection instead of the behavior delivered by ‘Enroll an agentless web user’. If that component were misconfigured, a more characteristic finding would be that proxy requests arrive but user-based policies cannot associate them with an authenticated identity; the actual report concerns an unmanaged browser can reach web pages but no traffic reaches the cloud web proxy at an IT team managing both BYOD browsers and corporate FortiClient installations.
D:LDAP integration allows FortiSASE to reference directory accounts and user groups, which serves the different requirement to reuse users and groups defined in an accessible directory server instead of the behavior delivered by ‘Enroll an agentless web user’. If that component were misconfigured, a more characteristic finding would be that directory staff are not visible to SASE policy although the directory contains them; the actual report concerns an unmanaged browser can reach web pages but no traffic reaches the cloud web proxy at an IT team managing both BYOD browsers and corporate FortiClient installations.
Question 462
In a change-control meeting for a dual-carrier site separating internet transport from data-center overlays, a design review calls for a way to apply a dedicated policy to one exceptional transport while keeping other members grouped. What should the operator configure?
- Define the member health-check source
- Use an isolated single-member zone
- Use a physical interface as a member
- Disable a maintenance member
Explanation
Correct Answer
B:A zone can contain one member, allowing special security or routing treatment for that interface; that scope directly serves the goal to apply a dedicated policy to one exceptional transport while keeping other members grouped in a dual-carrier site separating internet transport from data-center overlays. During implementation, a one-member zone is still referenced as a zone, not as an individual member in firewall policies rather than treating the configuration label as proof of working service.
Incorrect Answers
A:A member health-check source setting controls the source IP used by health probes to a monitored server, a mechanism intended to send probes using the correct reachable source address on a multiaddress uplink rather than the requested ‘Use an isolated single-member zone’ control. The stated task instead is to apply a dedicated policy to one exceptional transport while keeping other members grouped, and adjusting ‘Define the member health-check source’ would not deliver ‘Use an isolated single-member zone’. For the ‘Define the member health-check source’ alternative to ‘Use an isolated single-member zone’, the source must be routable toward the monitor target and accepted by its response path.
C:Physical WAN ports can act as members with their own connectivity, next hops, costs, and measured health, a mechanism intended to bring a directly connected broadband circuit under SD-WAN decisions rather than the requested ‘Use an isolated single-member zone’ control. The stated task instead is to apply a dedicated policy to one exceptional transport while keeping other members grouped, and adjusting ‘Use a physical interface as a member’ would not deliver ‘Use an isolated single-member zone’. For the ‘Use a physical interface as a member’ alternative to ‘Use an isolated single-member zone’, adding a member does not replace interface addressing or carrier troubleshooting.
D:Disabling an SD-WAN member removes it from eligible SD-WAN selection without requiring deletion of its configuration, a mechanism intended to exclude a WAN circuit from SD-WAN decisions during scheduled carrier work rather than the requested ‘Use an isolated single-member zone’ control. The stated task instead is to apply a dedicated policy to one exceptional transport while keeping other members grouped, and adjusting ‘Disable a maintenance member’ would not deliver ‘Use an isolated single-member zone’. For the ‘Disable a maintenance member’ alternative to ‘Use an isolated single-member zone’, ensure remaining members provide viable routes and sufficient capacity.
Question 463
At a campus running FortiOS 7.6 with application-aware policies, the rollout includes the control ‘Use DSCP-based SD-WAN steering’ to distinguish preclassified media packets from ordinary web traffic at path-selection time. Which observed mechanism is consistent with this configuration?
- Source-address criteria restrict SD-WAN rule matching to sessions from specified client address ranges.
- DSCP match criteria can steer traffic carrying designated IP-header service markings.
- The implicit SD-WAN rule handles unmatched traffic using available routing and interface-priority logic.
- SD-WAN service diagnostics expose matched rules, interface lists, modes, and selected member status.
Explanation
Correct Answer
B:‘Use DSCP-based SD-WAN steering’ is used to distinguish preclassified media packets from ordinary web traffic at path-selection time in a campus running FortiOS 7.6 with application-aware policies; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the matched service specifies the corresponding DSCP codepoint and steers marked packets; the rollout must also respect this constraint: Trust and policing of DSCP markings require an appropriate network policy design.
Incorrect Answers
A:The described behavior is part of ‘Match a source subnet in an SD-WAN rule’, used to apply a special path selection only to traffic originating in one department network instead of the role of ‘Use DSCP-based SD-WAN steering’. In contrast to ‘Match a source subnet in an SD-WAN rule’, ‘Use DSCP-based SD-WAN steering’ follows a different mechanism: dSCP match criteria can steer traffic carrying designated IP-header service markings. Treating ‘Match a source subnet in an SD-WAN rule’ as equivalent would not address voice packets bearing priority markings share the generic internet selection rule in a campus running FortiOS 7.6 with application-aware policies.
C:The described behavior is part of ‘Use an implicit SD-WAN rule as fallback’, used to provide default path behavior when traffic does not match any explicit steering service instead of the role of ‘Use DSCP-based SD-WAN steering’. In contrast to ‘Use an implicit SD-WAN rule as fallback’, ‘Use DSCP-based SD-WAN steering’ follows a different mechanism: dSCP match criteria can steer traffic carrying designated IP-header service markings. Treating ‘Use an implicit SD-WAN rule as fallback’ as equivalent would not address voice packets bearing priority markings share the generic internet selection rule in a campus running FortiOS 7.6 with application-aware policies.
D:The described behavior is part of ‘Test rule matching with service diagnostics’, used to identify which SD-WAN rule and candidate member were chosen for a particular session instead of the role of ‘Use DSCP-based SD-WAN steering’. In contrast to ‘Test rule matching with service diagnostics’, ‘Use DSCP-based SD-WAN steering’ follows a different mechanism: dSCP match criteria can steer traffic carrying designated IP-header service markings. Treating ‘Test rule matching with service diagnostics’ as equivalent would not address voice packets bearing priority markings share the generic internet selection rule in a campus running FortiOS 7.6 with application-aware policies.
Question 464
At a campus running FortiOS 7.6 with application-aware policies, the rollout includes the control ‘Match an Internet Service Database destination’ to identify cloud-service traffic by maintained service definitions instead of a static destination IP. Which observed mechanism is consistent with this configuration?
- Associating a service rule with an SLA target filters or prioritizes measured candidates based on the rule's strategy.
- SD-WAN rules determine egress path candidates; firewall policies separately allow or deny traffic.
- The Manual strategy respects an administrator-specified interface preference list of eligible SD-WAN members.
- Internet service matching can steer flows associated with a known internet service without manually maintaining every destination subnet.
Explanation
Correct Answer
D:‘Match an Internet Service Database destination’ is used to identify cloud-service traffic by maintained service definitions instead of a static destination IP in a campus running FortiOS 7.6 with application-aware policies; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the SD-WAN rule matches the designated Internet Service Database object; the rollout must also respect this constraint: An ISDB object is not the same as a local DNS record or the name of a user group.
Incorrect Answers
A:The described behavior is part of ‘Use an SLA target within an SD-WAN service rule’, used to select a path only after it meets the performance objective for that particular application instead of the role of ‘Match an Internet Service Database destination’. In contrast to ‘Use an SLA target within an SD-WAN service rule’, ‘Match an Internet Service Database destination’ follows a different mechanism: internet service matching can steer flows associated with a known internet service without manually maintaining every destination subnet. Treating ‘Use an SLA target within an SD-WAN service rule’ as equivalent would not address a SaaS provider changes IP addresses and a hardcoded address-match rule misses new endpoints in a campus running FortiOS 7.6 with application-aware policies.
B:The described behavior is part of ‘Separate steering from security authorization’, used to choose a fast WAN without accidentally treating SD-WAN selection as firewall access permission instead of the role of ‘Match an Internet Service Database destination’. In contrast to ‘Separate steering from security authorization’, ‘Match an Internet Service Database destination’ follows a different mechanism: internet service matching can steer flows associated with a known internet service without manually maintaining every destination subnet. Treating ‘Separate steering from security authorization’ as equivalent would not address a SaaS provider changes IP addresses and a hardcoded address-match rule misses new endpoints in a campus running FortiOS 7.6 with application-aware policies.
C:The described behavior is part of ‘Use a manual SD-WAN strategy’, used to pin a specific business application to a preferred transport independent of dynamic quality ranking instead of the role of ‘Match an Internet Service Database destination’. In contrast to ‘Use a manual SD-WAN strategy’, ‘Match an Internet Service Database destination’ follows a different mechanism: internet service matching can steer flows associated with a known internet service without manually maintaining every destination subnet. Treating ‘Use a manual SD-WAN strategy’ as equivalent would not address a SaaS provider changes IP addresses and a hardcoded address-match rule misses new endpoints in a campus running FortiOS 7.6 with application-aware policies.
Question 465
Within a cloud security tenant inspecting traffic from managed remote laptops, the team wants to avoid an ineffective configuration of ‘Configure data loss prevention patterns’. Which consideration deserves attention?
- The SaaS provider must support the header convention and the request must be inspectable.
- DNS filtering cannot inspect the contents of an already established HTTPS session.
- Choose deep inspection when the requirement actually depends on encrypted content visibility.
- Detection requires representative patterns and an inspection path that exposes payload content.
- Specific overrides should be tested against recognized application signatures.
Explanation
Correct Answer
D:This condition matters for ‘Configure data loss prevention patterns’ because DLP examines supported inspected content for configured sensitive-data patterns and applies an action. Omitting the relevant safeguard can produce an approved SaaS service accepts uploads containing explicitly restricted account identifiers; a successful test at a cloud security tenant inspecting traffic from managed remote laptops would instead demonstrate that DLP records a matching sensitive-data pattern and the configured action.
Incorrect Answers
A:The condition is associated with ‘Use inline CASB HTTP header restrictions’, a mechanism used to restrict which SaaS tenant a managed user may access by adjusting inspected web request headers instead of ‘Configure data loss prevention patterns’, because Web Filter with Inline-CASB can insert or alter supported outbound HTTP headers to enforce SaaS tenant restrictions. For ‘Configure data loss prevention patterns’, unlike ‘Use inline CASB HTTP header restrictions’, the characteristic failure would be an approved SaaS service accepts uploads containing explicitly restricted account identifiers, which this alternative prerequisite would not directly address at a cloud security tenant inspecting traffic from managed remote laptops.
B:The condition is associated with ‘Use DNS filtering’, a mechanism used to stop requests to known malicious or restricted domains at the DNS layer instead of ‘Configure data loss prevention patterns’, because DNS Filter evaluates domain lookup activity before a client establishes a normal destination session. For ‘Configure data loss prevention patterns’, unlike ‘Use DNS filtering’, the characteristic failure would be an approved SaaS service accepts uploads containing explicitly restricted account identifiers, which this alternative prerequisite would not directly address at a cloud security tenant inspecting traffic from managed remote laptops.
C:The condition is associated with ‘Use certificate inspection for metadata-only TLS checks’, a mechanism used to inspect certificate-related connection metadata without decrypting application bodies instead of ‘Configure data loss prevention patterns’, because certificate inspection can evaluate visible TLS metadata but does not expose encrypted HTTP payload contents. For ‘Configure data loss prevention patterns’, unlike ‘Use certificate inspection for metadata-only TLS checks’, the characteristic failure would be an approved SaaS service accepts uploads containing explicitly restricted account identifiers, which this alternative prerequisite would not directly address at a cloud security tenant inspecting traffic from managed remote laptops.
E:The condition is associated with ‘Use application category overrides’, a mechanism used to deny one high-risk application within an otherwise permitted collaboration category instead of ‘Configure data loss prevention patterns’, because Application Control overrides provide a more specific action than a broad application-category setting. For ‘Configure data loss prevention patterns’, unlike ‘Use application category overrides’, the characteristic failure would be an approved SaaS service accepts uploads containing explicitly restricted account identifiers, which this alternative prerequisite would not directly address at a cloud security tenant inspecting traffic from managed remote laptops.
Question 466
For a remote-user design needing both public SaaS and internal subnet access, a technical review examines the control ‘Use FortiGate as a private-access hub’ for the objective to connect remote FortiSASE clients to data-center applications protected behind a FortiGate. Which statement best describes what it changes?
- An SD-WAN-based SPA design can provide routed access to private TCP and UDP applications.
- FortiGate can provide the secure private access hub that forwards authorized cloud-to-private traffic.
- Multiple suitably configured SPA hubs can provide a redundant path to private resources.
- Site-based on-ramp configuration determines which branch flows are forwarded into FortiSASE.
Explanation
Correct Answer
B:‘Use FortiGate as a private-access hub’ is used to connect remote FortiSASE clients to data-center applications protected behind a FortiGate in a remote-user design needing both public SaaS and internal subnet access; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the hub connection is healthy and routes exist to the internal application networks; the rollout must also respect this constraint: The protected data-center prefixes need return routes toward FortiSASE clients.
Incorrect Answers
A:The described behavior is part of ‘Use SD-WAN private access for TCP and UDP’, used to extend private resource connectivity beyond the TCP-focused ZTNA access proxy model instead of the role of ‘Use FortiGate as a private-access hub’. In contrast to ‘Use SD-WAN private access for TCP and UDP’, ‘Use FortiGate as a private-access hub’ follows a different mechanism: FortiGate can provide the secure private access hub that forwards authorized cloud-to-private traffic. Treating ‘Use SD-WAN private access for TCP and UDP’ as equivalent would not address internet access works for remote agents but data-center CIDRs remain unreachable in a remote-user design needing both public SaaS and internal subnet access.
C:The described behavior is part of ‘Use a redundant private-access hub’, used to maintain access to applications when one data-center gateway or tunnel fails instead of the role of ‘Use FortiGate as a private-access hub’. In contrast to ‘Use a redundant private-access hub’, ‘Use FortiGate as a private-access hub’ follows a different mechanism: FortiGate can provide the secure private access hub that forwards authorized cloud-to-private traffic. Treating ‘Use a redundant private-access hub’ as equivalent would not address internet access works for remote agents but data-center CIDRs remain unreachable in a remote-user design needing both public SaaS and internal subnet access.
D:The described behavior is part of ‘Verify site-based SASE traffic steering’, used to differentiate local branch DIA from traffic genuinely sent to cloud enforcement instead of the role of ‘Use FortiGate as a private-access hub’. In contrast to ‘Verify site-based SASE traffic steering’, ‘Use FortiGate as a private-access hub’ follows a different mechanism: FortiGate can provide the secure private access hub that forwards authorized cloud-to-private traffic. Treating ‘Verify site-based SASE traffic steering’ as equivalent would not address internet access works for remote agents but data-center CIDRs remain unreachable in a remote-user design needing both public SaaS and internal subnet access.
Question 467
During an authorized lab exercise for a remote-user design needing both public SaaS and internal subnet access, a reviewer needs proof the deployment can let remote users resolve internal application FQDNs to protected addresses. Which observation most directly validates it?
- Matching site flows are observed through the branch on-ramp and SASE enforcement logs.
- The secure IPsec association is established to the intended cloud edge.
- The intended private prefix is visible through the correct service connection.
- An enrolled client resolves the private FQDN through the intended enterprise DNS path.
Explanation
Correct Answer
D:This checks ‘Configure DNS resolution for private names’ at the correct operational boundary: private or split-DNS settings direct internal-name lookups to appropriate enterprise DNS servers. It demonstrates the specific capability to let remote users resolve internal application FQDNs to protected addresses in a remote-user design needing both public SaaS and internal subnet access; deployment should additionally respect the constraint: Name resolution must be reachable over the chosen private access topology.
Incorrect Answers
A:That observation belongs to ‘Verify site-based SASE traffic steering’, not ‘Configure DNS resolution for private names’; its purpose is to differentiate local branch DIA from traffic genuinely sent to cloud enforcement, the underlying behavior is that site-based on-ramp configuration determines which branch flows are forwarded into FortiSASE. The reviewer is instead verifying ‘Configure DNS resolution for private names’ for a remote-user design needing both public SaaS and internal subnet access, not the evidence produced by ‘Verify site-based SASE traffic steering’.
B:That observation belongs to ‘Use IPsec transport for the SASE branch connection’, not ‘Configure DNS resolution for private names’; its purpose is to carry branch traffic securely across an untrusted ISP toward a SASE service edge, the underlying behavior is that an IPsec-based on-ramp encapsulates site traffic for cloud delivery over the public underlay. The reviewer is instead verifying ‘Configure DNS resolution for private names’ for a remote-user design needing both public SaaS and internal subnet access, not the evidence produced by ‘Use IPsec transport for the SASE branch connection’.
C:That observation belongs to ‘Advertise internal prefixes to SPA routing’, not ‘Configure DNS resolution for private names’; its purpose is to make specific private data-center networks reachable from security PoPs, the underlying behavior is that routing advertisement or static private routes informs FortiSASE how to reach protected application subnets. The reviewer is instead verifying ‘Configure DNS resolution for private names’ for a remote-user design needing both public SaaS and internal subnet access, not the evidence produced by ‘Advertise internal prefixes to SPA routing’.
Question 468
For a service operator standardizing remote internet protection across sites, a review of the current state finds that off-site users bypass cloud inspection while on-premises users remain protected. Which configuration area most directly addresses this?
- Investigate: Organize SASE users into policy groups
- Investigate: Choose an appropriate security PoP path
- Investigate: Use geolocation-aware access restrictions
- Investigate: Verify FortiSASE service provisioning
Explanation
Correct Answer
B:The symptom identifies the missing operational behavior: FortiSASE steers supported client traffic toward its security points of presence for consistent remote policy enforcement. For a service operator standardizing remote internet protection across sites, a direct diagnostic confirmation would be that client connectivity shows active SASE steering to a security PoP; during repair, the user's steering method determines which traffic types are inspected.
Incorrect Answers
A:User groups provide a membership basis for matching different FortiSASE access policies, which serves the different requirement to apply different web access controls to developers and finance staff instead of the behavior delivered by ‘Choose an appropriate security PoP path’. If that component were misconfigured, a more characteristic finding would be that users from two departments unexpectedly receive the same unrestricted access policy; the actual report concerns off-site users bypass cloud inspection while on-premises users remain protected at a service operator standardizing remote internet protection across sites.
C:Geographic policy criteria can help distinguish traffic by geolocation where FortiSASE policy supports that selection, which serves the different requirement to restrict access from locations outside an organization-approved geographic footprint instead of the behavior delivered by ‘Choose an appropriate security PoP path’. If that component were misconfigured, a more characteristic finding would be that remote access occurs from a region that violates the deployment's stated geographic rule; the actual report concerns off-site users bypass cloud inspection while on-premises users remain protected at a service operator standardizing remote internet protection across sites.
D:FortiSASE must have an active provisioned instance with security points of presence before managed users can use its cloud enforcement, which serves the different requirement to confirm the cloud security service is available before distributing client configurations instead of the behavior delivered by ‘Choose an appropriate security PoP path’. If that component were misconfigured, a more characteristic finding would be that installation invitations are sent while the tenant has no functioning security PoP resources; the actual report concerns off-site users bypass cloud inspection while on-premises users remain protected at a service operator standardizing remote internet protection across sites.
Question 469
At a campus running FortiOS 7.6 with application-aware policies, the team will implement ‘Consider first-flow application recognition’ to explain why the first newly observed app session may not match application-based steering immediately. Select THREE statements that accurately describe this control's mechanism, deployment consideration, and validating evidence. Choose THREE.
- Do not assume every first encrypted connection is identified before its initial path is chosen.
- FortiOS learns application signatures and destination tuples from inspected sessions for subsequent application-based matches.
- Service matching narrows selection by transport protocol and destination-port criteria.
- The narrow rule appears ahead of the broad rule and receives matching hits.
- The application-control internet-service list contains the learned application destination tuple.
- Application Control must be enabled in the matching firewall policy for identification-based steering.
Explanation
Correct Answers
A:This safeguard applies to ‘Consider first-flow application recognition’, which works because FortiOS learns application signatures and destination tuples from inspected sessions for subsequent application-based matches. Without the correct deployment condition, operators may see that the first session uses a general path but later sessions to the recognized service use the preferred route in a campus running FortiOS 7.6 with application-aware policies.
B:This is the mechanism behind ‘Consider first-flow application recognition’ in a campus running FortiOS 7.6 with application-aware policies; its objective is to explain why the first newly observed app session may not match application-based steering immediately. The deployment can be confirmed when the application-control internet-service list contains the learned application destination tuple, subject to the boundary that do not assume every first encrypted connection is identified before its initial path is chosen.
E:The observation follows from the operation of ‘Consider first-flow application recognition’: FortiOS learns application signatures and destination tuples from inspected sessions for subsequent application-based matches. It directly tests the requested ability to explain why the first newly observed app session may not match application-based steering immediately in a campus running FortiOS 7.6 with application-aware policies, rather than another policy or network layer.
Incorrect Answers
C:This describes ‘Match service protocol and port’, not the requested ‘Consider first-flow application recognition’, and is meant to steer a well-defined TCP service without affecting unrelated traffic to the same server. Its evidence would be that the rule matches the intended TCP or UDP service and leaves other ports to later rules, not a demonstration of ‘Consider first-flow application recognition’ and its distinct outcome.
D:This result would validate ‘Order specific SD-WAN rules above general matches’, not ‘Consider first-flow application recognition’, because SD-WAN service rules are evaluated in configured order, so earlier matching entries can take precedence. That separate implementation serves ensure a narrow high-priority policy wins instead of a catch-all service rule, whereas the audit needs evidence specifically of ‘Consider first-flow application recognition’ at a campus running FortiOS 7.6 with application-aware policies.
F:The planning point is associated with ‘Match by detected application’, not ‘Consider first-flow application recognition’; its real role is to prefer an SD-WAN path based on application identification rather than fixed port alone. The required deployment instead centers on ‘Consider first-flow application recognition’, rather than ‘Match by detected application’; the distinct symptom to guard against is that the first session uses a general path but later sessions to the recognized service use the preferred route.
Question 470
At a hub-and-spoke network with internet breakout and private IPsec overlays, the change request is to reach an on-premises network across an IPsec overlay SD-WAN group. Which configuration is the most direct fit?
- Use a route-based IPsec overlay
- Install default route through an SD-WAN zone
- Use a BGP learned private prefix
- Configure a static partner route through overlay zone
Explanation
Correct Answer
D:A destination-specific static route referencing the overlay zone makes private routes accessible to SD-WAN selection; that scope directly serves the goal to reach an on-premises network across an IPsec overlay SD-WAN group in a hub-and-spoke network with internet breakout and private IPsec overlays. During implementation, the remote peer must also know a return path to the local subnet rather than treating the configuration label as proof of working service.
Incorrect Answers
A:Route-based IPsec exposes a logical tunnel interface that routing and SD-WAN can reference, a mechanism intended to carry private routed traffic as a selectable interface-based tunnel path rather than the requested ‘Configure a static partner route through overlay zone’ control. The stated task instead is to reach an on-premises network across an IPsec overlay SD-WAN group, and adjusting ‘Use a route-based IPsec overlay’ would not deliver ‘Configure a static partner route through overlay zone’. For the ‘Use a route-based IPsec overlay’ alternative to ‘Configure a static partner route through overlay zone’, tunnel security negotiation and return routing still need separate validation.
B:A zone-based default static route gives SD-WAN a routing candidate for nonlocal destinations, a mechanism intended to make general internet destinations reachable without listing every WAN member as a separate policy interface rather than the requested ‘Configure a static partner route through overlay zone’ control. The stated task instead is to reach an on-premises network across an IPsec overlay SD-WAN group, and adjusting ‘Install default route through an SD-WAN zone’ would not deliver ‘Configure a static partner route through overlay zone’. For the ‘Install default route through an SD-WAN zone’ alternative to ‘Configure a static partner route through overlay zone’, a route must exist before the steering choice can forward a matching session.
C:BGP can advertise and learn remote private networks over supported routed overlays, a mechanism intended to obtain branch or data-center destinations without maintaining individual manual static routes rather than the requested ‘Configure a static partner route through overlay zone’ control. The stated task instead is to reach an on-premises network across an IPsec overlay SD-WAN group, and adjusting ‘Use a BGP learned private prefix’ would not deliver ‘Configure a static partner route through overlay zone’. For the ‘Use a BGP learned private prefix’ alternative to ‘Configure a static partner route through overlay zone’, routing adjacency and accepted prefix policies must be healthy independently of tunnel state.