Question 30
In a change-control meeting for a branch FortiGate that terminates an ISP handoff and two IPsec tunnels, a colleague challenges the proposed control ‘Set member cost’ for the requirement to favor a lower-priced uplink only when eligible under lowest-cost SLA rules. Which explanation accurately describes its behavior?
- Physical WAN ports can act as members with their own connectivity, next hops, costs, and measured health.
- Overlay zones provide distinct policy and route targets for tunnel traffic bound for private networks.
- The cost field ranks SLA-qualified members for the Lowest Cost strategy, with smaller values preferred.
- Route-based IPsec tunnel interfaces can be members whose quality is measured and selected for overlay routing.
Explanation
Correct Answer
C:‘Set member cost’ is used to favor a lower-priced uplink only when eligible under lowest-cost SLA rules in a branch FortiGate that terminates an ISP handoff and two IPsec tunnels; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the preferred member has the lower configured cost in the SLA-qualified candidates; the rollout must also respect this constraint: Cost does not replace health measurements or firewall policy matching.
Incorrect Answers
A:The described behavior is part of ‘Use a physical interface as a member’, used to bring a directly connected broadband circuit under SD-WAN decisions instead of the role of ‘Set member cost’. In contrast to ‘Use a physical interface as a member’, ‘Set member cost’ follows a different mechanism: the cost field ranks SLA-qualified members for the Lowest Cost strategy, with smaller values preferred. Treating ‘Use a physical interface as a member’ as equivalent would not address the expensive ISP is chosen even though both links meet SLA and its configured cost is lower in a branch FortiGate that terminates an ISP handoff and two IPsec tunnels.
B:The described behavior is part of ‘Create a dedicated overlay zone’, used to group IPsec tunnel interfaces separately from physical WAN underlays instead of the role of ‘Set member cost’. In contrast to ‘Create a dedicated overlay zone’, ‘Set member cost’ follows a different mechanism: the cost field ranks SLA-qualified members for the Lowest Cost strategy, with smaller values preferred. Treating ‘Create a dedicated overlay zone’ as equivalent would not address the expensive ISP is chosen even though both links meet SLA and its configured cost is lower in a branch FortiGate that terminates an ISP handoff and two IPsec tunnels.
D:The described behavior is part of ‘Use an IPsec interface as a member’, used to apply SD-WAN selection to redundant encrypted site-to-site paths instead of the role of ‘Set member cost’. In contrast to ‘Use an IPsec interface as a member’, ‘Set member cost’ follows a different mechanism: the cost field ranks SLA-qualified members for the Lowest Cost strategy, with smaller values preferred. Treating ‘Use an IPsec interface as a member’ as equivalent would not address the expensive ISP is chosen even though both links meet SLA and its configured cost is lower in a branch FortiGate that terminates an ISP handoff and two IPsec tunnels.
Question 31
At a dispersed workforce that uses a corporate SAML identity provider, an engineer is preparing ‘Distribute a FortiSASE invitation code’ to bind an invited remote user's FortiClient enrollment to the correct organization. Which TWO statements identify a pertinent deployment safeguard and a direct post-change validation result? Choose TWO.
- The configured LDAP source resolves expected groups and authenticated users.
- Onboarding credentials should be shared only with the intended users.
- Agentless proxy steering does not automatically tunnel all nonweb IP traffic.
- The enterprise deployment tool must match endpoint operating systems and device ownership.
- The endpoint registers to the intended FortiSASE environment after using the invitation.
Explanation
Correct Answers
B:This safeguard applies to ‘Distribute a FortiSASE invitation code’, which works because the Onboard Users workflow provides information that remote users use for FortiSASE client registration. Without the correct deployment condition, operators may see that employees have the agent installed but cannot associate it with the enterprise tenant in a dispersed workforce that uses a corporate SAML identity provider.
E:The observation follows from the operation of ‘Distribute a FortiSASE invitation code’: the Onboard Users workflow provides information that remote users use for FortiSASE client registration. It directly tests the requested ability to bind an invited remote user's FortiClient enrollment to the correct organization in a dispersed workforce that uses a corporate SAML identity provider, rather than another policy or network layer.
Incorrect Answers
A:This result would validate ‘Import users through LDAP’, not ‘Distribute a FortiSASE invitation code’, because LDAP integration allows FortiSASE to reference directory accounts and user groups. That separate implementation serves reuse users and groups defined in an accessible directory server, whereas the audit needs evidence specifically of ‘Distribute a FortiSASE invitation code’ at a dispersed workforce that uses a corporate SAML identity provider.
C:The planning point is associated with ‘Enroll an agentless web user’, not ‘Distribute a FortiSASE invitation code’; its real role is to protect an unmanaged Chromebook's HTTP and HTTPS browsing without installing FortiClient. The required deployment instead centers on ‘Distribute a FortiSASE invitation code’, rather than ‘Enroll an agentless web user’; the distinct symptom to guard against is that employees have the agent installed but cannot associate it with the enterprise tenant.
D:The planning point is associated with ‘Deploy FortiClient using enterprise management’, not ‘Distribute a FortiSASE invitation code’; its real role is to roll out FortiClient at scale without requiring hundreds of manual installer sessions. The required deployment instead centers on ‘Distribute a FortiSASE invitation code’, rather than ‘Deploy FortiClient using enterprise management’; the distinct symptom to guard against is that employees have the agent installed but cannot associate it with the enterprise tenant.
Question 32
For a remote call center measuring two ISP paths to the same application target, an audit asks for evidence that the team can avoid a circuit whose packet-delay variation damages live audio. Which finding would answer that question?
- Probe results to the intended external target reflect the actual remote-path problem.
- The rule references a populated health check and shows candidate quality values.
- The failed member becomes ineligible while a healthy route is preferred.
- The high-variation path fails jitter while the stable path passes.
Explanation
Correct Answer
D:This checks ‘Set jitter SLA threshold’ at the correct operational boundary: a jitter target compares delay variation with an allowed maximum to qualify or reject a member. It demonstrates the specific capability to avoid a circuit whose packet-delay variation damages live audio in a remote call center measuring two ISP paths to the same application target; deployment should additionally respect the constraint: Low average latency alone does not demonstrate satisfactory jitter.
Incorrect Answers
A:That observation belongs to ‘Select the correct probe server’, not ‘Set jitter SLA threshold’; its purpose is to measure user-relevant path health rather than only the nearest ISP hop, the underlying behavior is that health checks against a representative reachable target include more of the application path than checks aimed only at the immediate gateway. The reviewer is instead verifying ‘Set jitter SLA threshold’ for a remote call center measuring two ISP paths to the same application target, not the evidence produced by ‘Select the correct probe server’.
B:That observation belongs to ‘Use SLA measurements for best-quality steering’, not ‘Set jitter SLA threshold’; its purpose is to feed measured latency, jitter, or loss into a dynamic path-selection rule, the underlying behavior is that Best Quality uses configured quality criteria derived from a health check to prioritize the most suitable available member. The reviewer is instead verifying ‘Set jitter SLA threshold’ for a remote call center measuring two ISP paths to the same application target, not the evidence produced by ‘Use SLA measurements for best-quality steering’.
C:That observation belongs to ‘Use probe loss to trigger failover’, not ‘Set jitter SLA threshold’; its purpose is to remove a genuinely unreachable transport from eligible load-balancing routes, the underlying behavior is that failed health checks can withdraw the broken member's routes from the SD-WAN eligible path group. The reviewer is instead verifying ‘Set jitter SLA threshold’ for a remote call center measuring two ISP paths to the same application target, not the evidence produced by ‘Use probe loss to trigger failover’.
Question 33
Within a medical office prioritizing stable response times to a hosted patient system, the operator applies the control ‘Create an active probe health check’ as part of an effort to measure reachability and delay even when no user sessions traverse a circuit. Which operating behavior should the team expect?
- Historical SLA samples and logs help distinguish transient degradation from a persistent member failure.
- Health tests depend on packets reaching the target and return traffic finding a valid response path.
- Targets tighter than achievable WAN conditions can cause otherwise connected members to fail policy qualification.
- A jitter target compares delay variation with an allowed maximum to qualify or reject a member.
- Active SD-WAN health checks send periodic probes to a designated target over monitored members.
Explanation
Correct Answer
E:‘Create an active probe health check’ is used to measure reachability and delay even when no user sessions traverse a circuit in a medical office prioritizing stable response times to a hosted patient system; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that health-check status shows probe-derived latency and loss for each monitored member; the rollout must also respect this constraint: The target must answer the selected probe method and be reachable from those paths.
Incorrect Answers
A:The described behavior is part of ‘Review SLA historical changes’, used to establish whether a brief performance decline coincides with a reported outage instead of the role of ‘Create an active probe health check’. In contrast to ‘Review SLA historical changes’, ‘Create an active probe health check’ follows a different mechanism: active SD-WAN health checks send periodic probes to a designated target over monitored members. Treating ‘Review SLA historical changes’ as equivalent would not address the firewall has no latency samples during idle periods despite the need for proactive measurements in a medical office prioritizing stable response times to a hosted patient system.
B:The described behavior is part of ‘Check probe-path asymmetry’, used to confirm health responses return correctly when transport routes are asymmetric instead of the role of ‘Create an active probe health check’. In contrast to ‘Check probe-path asymmetry’, ‘Create an active probe health check’ follows a different mechanism: active SD-WAN health checks send periodic probes to a designated target over monitored members. Treating ‘Check probe-path asymmetry’ as equivalent would not address the firewall has no latency samples during idle periods despite the need for proactive measurements in a medical office prioritizing stable response times to a hosted patient system.
C:The described behavior is part of ‘Avoid overly strict SLA targets’, used to prevent both usable circuits from being excluded by unrealistic quality limits instead of the role of ‘Create an active probe health check’. In contrast to ‘Avoid overly strict SLA targets’, ‘Create an active probe health check’ follows a different mechanism: active SD-WAN health checks send periodic probes to a designated target over monitored members. Treating ‘Avoid overly strict SLA targets’ as equivalent would not address the firewall has no latency samples during idle periods despite the need for proactive measurements in a medical office prioritizing stable response times to a hosted patient system.
D:The described behavior is part of ‘Set jitter SLA threshold’, used to avoid a circuit whose packet-delay variation damages live audio instead of the role of ‘Create an active probe health check’. In contrast to ‘Set jitter SLA threshold’, ‘Create an active probe health check’ follows a different mechanism: active SD-WAN health checks send periodic probes to a designated target over monitored members. Treating ‘Set jitter SLA threshold’ as equivalent would not address the firewall has no latency samples during idle periods despite the need for proactive measurements in a medical office prioritizing stable response times to a hosted patient system.
Question 34
Within a branch outage review comparing session entries and SLA histories, after the rollout, operators find that a blocked application is misdiagnosed as an SLA mismatch although its traffic action is deny. Where should they focus troubleshooting?
- Investigate: Distinguish dropped from forwarded session outcome
- Investigate: Review a matched firewall traffic log
- Investigate: Inspect SD-WAN rule hit counters
- Investigate: Correlate a failover event with SLA history
- Investigate: Use SD-WAN service4 diagnostics
Explanation
Correct Answer
A:The symptom identifies the missing operational behavior: a deny disposition in the traffic log is an authorization result, not evidence of performance-based steering failure. For a branch outage review comparing session entries and SLA histories, a direct diagnostic confirmation would be that the matched session log shows the firewall decision and the associated rule ID; during repair, investigate authorization before tuning member cost or jitter targets.
Incorrect Answers
B:Traffic logs supply session-level context needed to correlate SD-WAN steering with firewall authorization, which serves the different requirement to trace a user's source, destination, policy ID, session, and egress interface instead of the behavior delivered by ‘Distinguish dropped from forwarded session outcome’. If that component were misconfigured, a more characteristic finding would be that users report a drop but operators inspect only SLA charts without a session record; the actual report concerns a blocked application is misdiagnosed as an SLA mismatch although its traffic action is deny at a branch outage review comparing session entries and SLA histories.
C:Service rule counters and diagnostics help confirm which policy actually handles observed traffic, which serves the different requirement to determine whether sessions are matching the intended service rule before editing path priorities instead of the behavior delivered by ‘Distinguish dropped from forwarded session outcome’. If that component were misconfigured, a more characteristic finding would be that a priority member is blamed though the expected service rule never matches any sessions; the actual report concerns a blocked application is misdiagnosed as an SLA mismatch although its traffic action is deny at a branch outage review comparing session entries and SLA histories.
D:Time-aligned SLA logs and service events can show when a member failed and traffic was redirected, which serves the different requirement to differentiate an ISP performance event from a later manual service-rule edit instead of the behavior delivered by ‘Distinguish dropped from forwarded session outcome’. If that component were misconfigured, a more characteristic finding would be that a backup-path surge occurred before an operator changed the preference order; the actual report concerns a blocked application is misdiagnosed as an SLA mismatch although its traffic action is deny at a branch outage review comparing session entries and SLA histories.
E:The service4 diagnostic command exposes IPv4 rule modes, matched criteria, and selected candidates, which serves the different requirement to examine IPv4 SD-WAN rule selection rather than a generic interface status page instead of the behavior delivered by ‘Distinguish dropped from forwarded session outcome’. If that component were misconfigured, a more characteristic finding would be that an IPv4 flow takes the wrong path but only physical WAN link states have been reviewed; the actual report concerns a blocked application is misdiagnosed as an SLA mismatch although its traffic action is deny at a branch outage review comparing session entries and SLA histories.
Question 35
At a policy owner protecting HTTPS web sessions without blocking business use, an engineer is preparing ‘Use DNS filtering’ to stop requests to known malicious or restricted domains at the DNS layer. Which TWO statements identify a pertinent deployment safeguard and a direct post-change validation result? Choose TWO.
- Outgoing SaaS requests contain the configured tenant-restriction header under the inline policy.
- DNS filtering cannot inspect the contents of an already established HTTPS session.
- DNS query logs show the configured domain-category or threat action.
- Web filtering decisions differ from application-control signatures and DNS resolution policies.
- Certificate deployment and inspection exemptions must be handled to avoid breaking legitimate services.
Explanation
Correct Answers
B:This safeguard applies to ‘Use DNS filtering’, which works because DNS Filter evaluates domain lookup activity before a client establishes a normal destination session. Without the correct deployment condition, operators may see that clients resolve domains known to be malicious even before the associated web connection starts in a policy owner protecting HTTPS web sessions without blocking business use.
C:The observation follows from the operation of ‘Use DNS filtering’: DNS Filter evaluates domain lookup activity before a client establishes a normal destination session. It directly tests the requested ability to stop requests to known malicious or restricted domains at the DNS layer in a policy owner protecting HTTPS web sessions without blocking business use, rather than another policy or network layer.
Incorrect Answers
A:This result would validate ‘Use inline CASB HTTP header restrictions’, not ‘Use DNS filtering’, because Web Filter with Inline-CASB can insert or alter supported outbound HTTP headers to enforce SaaS tenant restrictions. That separate implementation serves restrict which SaaS tenant a managed user may access by adjusting inspected web request headers, whereas the audit needs evidence specifically of ‘Use DNS filtering’ at a policy owner protecting HTTPS web sessions without blocking business use.
D:The planning point is associated with ‘Apply a web-filter category action’, not ‘Use DNS filtering’; its real role is to block a prohibited web category while allowing legitimate business browsing. The required deployment instead centers on ‘Use DNS filtering’, rather than ‘Apply a web-filter category action’; the distinct symptom to guard against is that clients resolve domains known to be malicious even before the associated web connection starts.
E:The planning point is associated with ‘Enable SSL deep inspection’, not ‘Use DNS filtering’; its real role is to inspect content carried inside HTTPS when allowed by policy and endpoint trust. The required deployment instead centers on ‘Use DNS filtering’, rather than ‘Enable SSL deep inspection’; the distinct symptom to guard against is that clients resolve domains known to be malicious even before the associated web connection starts.
Question 36
During an authorized lab exercise for a branch outage review comparing session entries and SLA histories, the deployment standard specifies the control ‘Inspect member health-check output’ to explain why a link was removed from service despite remaining physically up. Which functional description matches it?
- Health-check diagnostics expose alive state, loss, latency, jitter, and SLA qualification.
- Member diagnostic output lists interface binding and operational SD-WAN member information.
- The service4 diagnostic command exposes IPv4 rule modes, matched criteria, and selected candidates.
- Time-aligned SLA logs and service events can show when a member failed and traffic was redirected.
Explanation
Correct Answer
A:‘Inspect member health-check output’ is used to explain why a link was removed from service despite remaining physically up in a branch outage review comparing session entries and SLA histories; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the relevant health-check record identifies the failed metric or probe state; the rollout must also respect this constraint: Correlate the event to the health-check target and time of the complaint.
Incorrect Answers
B:The described behavior is part of ‘Use member diagnostics’, used to check the configured gateway, status, and identity of a suspect SD-WAN member instead of the role of ‘Inspect member health-check output’. In contrast to ‘Use member diagnostics’, ‘Inspect member health-check output’ follows a different mechanism: health-check diagnostics expose alive state, loss, latency, jitter, and SLA qualification. Treating ‘Use member diagnostics’ as equivalent would not address the standby uplink appears up at layer one but is excluded as unhealthy in a branch outage review comparing session entries and SLA histories.
C:The described behavior is part of ‘Use SD-WAN service4 diagnostics’, used to examine IPv4 SD-WAN rule selection rather than a generic interface status page instead of the role of ‘Inspect member health-check output’. In contrast to ‘Use SD-WAN service4 diagnostics’, ‘Inspect member health-check output’ follows a different mechanism: health-check diagnostics expose alive state, loss, latency, jitter, and SLA qualification. Treating ‘Use SD-WAN service4 diagnostics’ as equivalent would not address the standby uplink appears up at layer one but is excluded as unhealthy in a branch outage review comparing session entries and SLA histories.
D:The described behavior is part of ‘Correlate a failover event with SLA history’, used to differentiate an ISP performance event from a later manual service-rule edit instead of the role of ‘Inspect member health-check output’. In contrast to ‘Correlate a failover event with SLA history’, ‘Inspect member health-check output’ follows a different mechanism: health-check diagnostics expose alive state, loss, latency, jitter, and SLA qualification. Treating ‘Correlate a failover event with SLA history’ as equivalent would not address the standby uplink appears up at layer one but is excluded as unhealthy in a branch outage review comparing session entries and SLA histories.
Question 37
Within a dispersed workforce that uses a corporate SAML identity provider, after the rollout, operators find that redirect-based identity login cannot complete because the SP and IdP trust are not aligned. Where should they focus troubleshooting?
- Investigate: Match endpoint profiles to the correct user group
- Investigate: Configure RADIUS authentication
- Investigate: Configure SAML single sign-on
- Investigate: Import users through LDAP
- Investigate: Configure agentless proxy SSO
Explanation
Correct Answer
C:The symptom identifies the missing operational behavior: FortiSASE acts as a SAML service provider while the configured IdP issues assertions for authenticated users. For a dispersed workforce that uses a corporate SAML identity provider, a direct diagnostic confirmation would be that a user authenticates at the IdP and returns with an accepted SAML assertion; during repair, the client browser must reach the IdP and the SP metadata and certificates must agree.
Incorrect Answers
A:Endpoint profiles can be assigned according to relevant groups or administrative selection, which serves the different requirement to deliver one set of endpoint controls to contractors and a stricter set to employees instead of the behavior delivered by ‘Configure SAML single sign-on’. If that component were misconfigured, a more characteristic finding would be that a contractor device receives the general employee tunnel settings instead of its restricted profile; the actual report concerns redirect-based identity login cannot complete because the SP and IdP trust are not aligned at a dispersed workforce that uses a corporate SAML identity provider.
B:RADIUS integration delegates user authentication to a configured authentication server, which serves the different requirement to authenticate managed remote agents against a reachable RADIUS infrastructure instead of the behavior delivered by ‘Configure SAML single sign-on’. If that component were misconfigured, a more characteristic finding would be that RADIUS-backed users fail access even though their account is accepted directly by the RADIUS server; the actual report concerns redirect-based identity login cannot complete because the SP and IdP trust are not aligned at a dispersed workforce that uses a corporate SAML identity provider.
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 ‘Configure SAML single sign-on’. 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 redirect-based identity login cannot complete because the SP and IdP trust are not aligned at a dispersed workforce that uses a corporate SAML identity provider.
E: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 ‘Configure SAML single sign-on’. 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 redirect-based identity login cannot complete because the SP and IdP trust are not aligned at a dispersed workforce that uses a corporate SAML identity provider.
Question 38
Within a security administrator refining profiles for allowed remote-user traffic, the administrator must allow a justified business website without disabling an entire restrictive category without redesigning unrelated services. Which option addresses the goal?
- Use a specific URL filter exception
- Use cloud API CASB for SaaS data at rest
- Use DNS filtering
- Configure application control signatures
- Apply remote browser isolation for risky sites
Explanation
Correct Answer
A:URL-level exceptions can refine category-based web filtering when an approved exception is required; that scope directly serves the goal to allow a justified business website without disabling an entire restrictive category in a security administrator refining profiles for allowed remote-user traffic. During implementation, use the narrowest necessary exception to avoid weakening protection broadly rather than treating the configuration label as proof of working service.
Incorrect Answers
B:API-connected CASB can examine supported SaaS tenant content and events without requiring every action to cross the inline proxy, a mechanism intended to inspect cloud-service data through supported SaaS APIs rather than only inline user sessions rather than the requested ‘Use a specific URL filter exception’ control. The stated task instead is to allow a justified business website without disabling an entire restrictive category, and adjusting ‘Use cloud API CASB for SaaS data at rest’ would not deliver ‘Use a specific URL filter exception’. For the ‘Use cloud API CASB for SaaS data at rest’ alternative to ‘Use a specific URL filter exception’, aPI authorization and provider support differ from inline real-time access controls.
C:DNS Filter evaluates domain lookup activity before a client establishes a normal destination session, a mechanism intended to stop requests to known malicious or restricted domains at the DNS layer rather than the requested ‘Use a specific URL filter exception’ control. The stated task instead is to allow a justified business website without disabling an entire restrictive category, and adjusting ‘Use DNS filtering’ would not deliver ‘Use a specific URL filter exception’. For the ‘Use DNS filtering’ alternative to ‘Use a specific URL filter exception’, DNS filtering cannot inspect the contents of an already established HTTPS session.
D:Application Control identifies application behavior and can apply signature-level allow, monitor, or block actions, a mechanism intended to block a specific risky application without disabling every website in its category rather than the requested ‘Use a specific URL filter exception’ control. The stated task instead is to allow a justified business website without disabling an entire restrictive category, and adjusting ‘Configure application control signatures’ would not deliver ‘Use a specific URL filter exception’. For the ‘Configure application control signatures’ alternative to ‘Use a specific URL filter exception’, port-only access controls are not the same as identifying an application signature.
E:Remote Browser Isolation executes supported browsing in an isolated remote context and streams a safer representation, a mechanism intended to isolate web rendering from the endpoint when access is required to a questionable website rather than the requested ‘Use a specific URL filter exception’ control. The stated task instead is to allow a justified business website without disabling an entire restrictive category, and adjusting ‘Apply remote browser isolation for risky sites’ would not deliver ‘Use a specific URL filter exception’. For the ‘Apply remote browser isolation for risky sites’ alternative to ‘Use a specific URL filter exception’, RBI mitigates browser-execution exposure; it is not a substitute for identity verification.
Question 39
Within a test lab containing an overlay tunnel and two underlay next hops, the configuration has been applied. Which measurement or record best confirms the goal to make general internet destinations reachable without listing every WAN member as a separate policy interface?
- The remote forwarding table contains a route back to the branch network.
- The prefix lookup is valid before member cost is adjusted for path preference.
- Policy-route diagnostics and the matched service show the actual selection chain.
- The routing table lists the default prefix associated with the intended SD-WAN zone.
- A route lookup shows the expected egress interface and reachable next hop.
Explanation
Correct Answer
D:This checks ‘Install default route through an SD-WAN zone’ at the correct operational boundary: a zone-based default static route gives SD-WAN a routing candidate for nonlocal destinations. It demonstrates the specific capability to make general internet destinations reachable without listing every WAN member as a separate policy interface in a test lab containing an overlay tunnel and two underlay next hops; deployment should additionally respect the constraint: A route must exist before the steering choice can forward a matching session.
Incorrect Answers
A:That observation belongs to ‘Confirm return route for remote private access’, not ‘Install default route through an SD-WAN zone’; its purpose is to repair one-way traffic where forward packets reach the data center but replies do not, the underlying behavior is that bidirectional reachability requires the remote hub or server-side router to return traffic to the client prefix. The reviewer is instead verifying ‘Install default route through an SD-WAN zone’ for a test lab containing an overlay tunnel and two underlay next hops, not the evidence produced by ‘Confirm return route for remote private access’.
B:That observation belongs to ‘Use routing diagnostics before changing SD-WAN cost’, not ‘Install default route through an SD-WAN zone’; its purpose is to avoid misdiagnosing unreachable prefixes as an economic-selection problem, the underlying behavior is that route inspection distinguishes absent routes from member cost or performance rankings. The reviewer is instead verifying ‘Install default route through an SD-WAN zone’ for a test lab containing an overlay tunnel and two underlay next hops, not the evidence produced by ‘Use routing diagnostics before changing SD-WAN cost’.
C:That observation belongs to ‘Validate policy routing and SD-WAN interaction’, not ‘Install default route through an SD-WAN zone’; its purpose is to identify why a matching policy-route decision changes normal egress selection, the underlying behavior is that policy route and SD-WAN service rules can influence forwarding decisions beyond basic destination-table lookup. The reviewer is instead verifying ‘Install default route through an SD-WAN zone’ for a test lab containing an overlay tunnel and two underlay next hops, not the evidence produced by ‘Validate policy routing and SD-WAN interaction’.
E:That observation belongs to ‘Verify the forwarding information base’, not ‘Install default route through an SD-WAN zone’; its purpose is to confirm the FortiGate has installed a usable next hop for a destination, the underlying behavior is that the FIB holds selected forwarding entries and is essential to actual packet delivery. The reviewer is instead verifying ‘Install default route through an SD-WAN zone’ for a test lab containing an overlay tunnel and two underlay next hops, not the evidence produced by ‘Verify the forwarding information base’.
Question 40
For a remote-user design needing both public SaaS and internal subnet access, a technical review examines the control ‘Configure DNS resolution for private names’ for the objective to let remote users resolve internal application FQDNs to protected addresses. Which statement best describes what it changes?
- Health and service-connection priorities can influence which reachable private hub path is preferred.
- FortiGate can provide the secure private access hub that forwards authorized cloud-to-private traffic.
- Private or split-DNS settings direct internal-name lookups to appropriate enterprise DNS servers.
- A supported SPA BGP design learns and advertises routes over the selected overlay connection.
Explanation
Correct Answer
C:‘Configure DNS resolution for private names’ is used to let remote users resolve internal application FQDNs to protected addresses 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 an enrolled client resolves the private FQDN through the intended enterprise DNS path; the rollout must also respect this constraint: Name resolution must be reachable over the chosen private access topology.
Incorrect Answers
A:The described behavior is part of ‘Select hub path using SLA health’, used to prefer a viable SPA route when one private-access connection becomes degraded instead of the role of ‘Configure DNS resolution for private names’. In contrast to ‘Select hub path using SLA health’, ‘Configure DNS resolution for private names’ follows a different mechanism: private or split-DNS settings direct internal-name lookups to appropriate enterprise DNS servers. Treating ‘Select hub path using SLA health’ as equivalent would not address an internal application works by IP address but its private hostname fails resolution in a remote-user design needing both public SaaS and internal subnet access.
B:The described behavior is part of ‘Use FortiGate as a private-access hub’, used to connect remote FortiSASE clients to data-center applications protected behind a FortiGate instead of the role of ‘Configure DNS resolution for private names’. In contrast to ‘Use FortiGate as a private-access hub’, ‘Configure DNS resolution for private names’ follows a different mechanism: private or split-DNS settings direct internal-name lookups to appropriate enterprise DNS servers. Treating ‘Use FortiGate as a private-access hub’ as equivalent would not address an internal application works by IP address but its private hostname fails resolution in a remote-user design needing both public SaaS and internal subnet access.
D:The described behavior is part of ‘Establish BGP with the SPA hub’, used to exchange private network reachability dynamically between FortiSASE and a FortiGate hub instead of the role of ‘Configure DNS resolution for private names’. In contrast to ‘Establish BGP with the SPA hub’, ‘Configure DNS resolution for private names’ follows a different mechanism: private or split-DNS settings direct internal-name lookups to appropriate enterprise DNS servers. Treating ‘Establish BGP with the SPA hub’ as equivalent would not address an internal application works by IP address but its private hostname fails resolution in a remote-user design needing both public SaaS and internal subnet access.