Question 340
In a change-control meeting for a security administrator refining profiles for allowed remote-user traffic, the proposed control is ‘Use a specific URL filter exception’. Which deployment condition is particularly relevant?
- Use the narrowest necessary exception to avoid weakening protection broadly.
- Application behavior and HTTPS fallback must be validated for the deployed browsers.
- RBI mitigates browser-execution exposure; it is not a substitute for identity verification.
- Web filtering decisions differ from application-control signatures and DNS resolution policies.
Explanation
Correct Answer
A:This condition matters for ‘Use a specific URL filter exception’ because URL-level exceptions can refine category-based web filtering when an approved exception is required. Omitting the relevant safeguard can produce a single approved vendor portal is blocked with every site in a broader category; a successful test at a security administrator refining profiles for allowed remote-user traffic would instead demonstrate that only the designated URL is exempted while the category continues to be restricted.
Incorrect Answers
B:The condition is associated with ‘Handle QUIC when deep inspection is required’, a mechanism used to keep SaaS web traffic on an inspectable TLS-over-TCP path for inline content controls instead of ‘Use a specific URL filter exception’, because blocking QUIC can force compatible browsers to fall back from HTTP/3 to TLS connections inspectable by the configured SASE controls. For ‘Use a specific URL filter exception’, unlike ‘Handle QUIC when deep inspection is required’, the characteristic failure would be a single approved vendor portal is blocked with every site in a broader category, which this alternative prerequisite would not directly address at a security administrator refining profiles for allowed remote-user traffic.
C:The condition is associated with ‘Apply remote browser isolation for risky sites’, a mechanism used to isolate web rendering from the endpoint when access is required to a questionable website instead of ‘Use a specific URL filter exception’, because remote Browser Isolation executes supported browsing in an isolated remote context and streams a safer representation. For ‘Use a specific URL filter exception’, unlike ‘Apply remote browser isolation for risky sites’, the characteristic failure would be a single approved vendor portal is blocked with every site in a broader category, which this alternative prerequisite would not directly address at a security administrator refining profiles for allowed remote-user traffic.
D:The condition is associated with ‘Apply a web-filter category action’, a mechanism used to block a prohibited web category while allowing legitimate business browsing instead of ‘Use a specific URL filter exception’, because web filtering classifies requested sites and applies the configured category or URL action. For ‘Use a specific URL filter exception’, unlike ‘Apply a web-filter category action’, the characteristic failure would be a single approved vendor portal is blocked with every site in a broader category, which this alternative prerequisite would not directly address at a security administrator refining profiles for allowed remote-user traffic.
Question 341
During an authorized lab exercise for a policy owner determining which protective control stopped a session, a pilot is about to enable ‘Correlate endpoint posture and access events’. Which precaution is most closely tied to this choice?
- Category decisions must be distinguished from DNS filter results and generic firewall denies.
- Correlate user, device, policy and time before treating the rejection as a routing fault.
- DNS filtering operates at name resolution, not by scanning file payloads.
- A traffic deny log by itself does not establish that antivirus detected malware.
Explanation
Correct Answer
B:This condition matters for ‘Correlate endpoint posture and access events’ because endpoint and access records can show that a posture tag triggered a conditional denial. Omitting the relevant safeguard can produce a valid user is blocked from private access while another managed device succeeds; a successful test at a policy owner determining which protective control stopped a session would instead demonstrate that the posture status and denied policy event agree on the noncompliant device condition.
Incorrect Answers
A:The condition is associated with ‘Inspect web-filter category logs’, a mechanism used to determine whether a website was blocked by category policy rather than by transport failure instead of ‘Correlate endpoint posture and access events’, because web-filter logs associate an HTTP or HTTPS destination with category evaluation and action. For ‘Correlate endpoint posture and access events’, unlike ‘Inspect web-filter category logs’, the characteristic failure would be a valid user is blocked from private access while another managed device succeeds, which this alternative prerequisite would not directly address at a policy owner determining which protective control stopped a session.
C:The condition is associated with ‘Inspect DNS-filter threat events’, a mechanism used to identify blocked malicious name resolution before the browser opens a TCP session instead of ‘Correlate endpoint posture and access events’, because DNS security logs record affected domain requests and configured malicious-domain actions. For ‘Correlate endpoint posture and access events’, unlike ‘Inspect DNS-filter threat events’, the characteristic failure would be a valid user is blocked from private access while another managed device succeeds, which this alternative prerequisite would not directly address at a policy owner determining which protective control stopped a session.
D:The condition is associated with ‘Inspect antivirus detection events’, a mechanism used to identify which inspected download was blocked for malware and under which policy instead of ‘Correlate endpoint posture and access events’, because aV logs identify signature or file detections and the security action applied to a session. For ‘Correlate endpoint posture and access events’, unlike ‘Inspect antivirus detection events’, the characteristic failure would be a valid user is blocked from private access while another managed device succeeds, which this alternative prerequisite would not directly address at a policy owner determining which protective control stopped a session.
Question 342
At a video collaboration office using two simultaneously healthy circuits, the change board is evaluating ‘Match service protocol and port’. Which technical consideration must be built into the plan?
- Port matching cannot reliably distinguish applications that share or change ports.
- A highly specific match below a catch-all does not automatically outrank it.
- Do not assume a rule edit retroactively redistributes every already established flow.
- Source steering does not itself authenticate an individual user.
Explanation
Correct Answer
A:This condition matters for ‘Match service protocol and port’ because service matching narrows selection by transport protocol and destination-port criteria. Omitting the relevant safeguard can produce all traffic to the server uses the special circuit instead of only the target application port; a successful test at a video collaboration office using two simultaneously healthy circuits would instead demonstrate that the rule matches the intended TCP or UDP service and leaves other ports to later rules.
Incorrect Answers
B:The condition is associated with ‘Order specific SD-WAN rules above general matches’, a mechanism used to ensure a narrow high-priority policy wins instead of a catch-all service rule instead of ‘Match service protocol and port’, because SD-WAN service rules are evaluated in configured order, so earlier matching entries can take precedence. For ‘Match service protocol and port’, unlike ‘Order specific SD-WAN rules above general matches’, the characteristic failure would be all traffic to the server uses the special circuit instead of only the target application port, which this alternative prerequisite would not directly address at a video collaboration office using two simultaneously healthy circuits.
C:The condition is associated with ‘Treat existing sessions differently from new flows’, a mechanism used to troubleshoot a session that remains associated with an earlier selection after an SD-WAN change instead of ‘Match service protocol and port’, because session state and configured failover behavior affect when path changes apply; newly created flows are evaluated against current steering. For ‘Match service protocol and port’, unlike ‘Treat existing sessions differently from new flows’, the characteristic failure would be all traffic to the server uses the special circuit instead of only the target application port, which this alternative prerequisite would not directly address at a video collaboration office using two simultaneously healthy circuits.
D:The condition is associated with ‘Match a source subnet in an SD-WAN rule’, a mechanism used to apply a special path selection only to traffic originating in one department network instead of ‘Match service protocol and port’, because source-address criteria restrict SD-WAN rule matching to sessions from specified client address ranges. For ‘Match service protocol and port’, unlike ‘Match a source subnet in an SD-WAN rule’, the characteristic failure would be all traffic to the server uses the special circuit instead of only the target application port, which this alternative prerequisite would not directly address at a video collaboration office using two simultaneously healthy circuits.
Question 343
In a change-control meeting for an industrial branch sending payroll traffic to a data-center application, a design review calls for a way to obtain branch or data-center destinations without maintaining individual manual static routes. What should the operator configure?
- Use a BGP learned private prefix
- Inspect route withdrawal after health failure
- Configure a static partner route through overlay zone
- Confirm return route for remote private access
Explanation
Correct Answer
A:BGP can advertise and learn remote private networks over supported routed overlays; that scope directly serves the goal to obtain branch or data-center destinations without maintaining individual manual static routes in an industrial branch sending payroll traffic to a data-center application. During implementation, routing adjacency and accepted prefix policies must be healthy independently of tunnel state rather than treating the configuration label as proof of working service.
Incorrect Answers
B:SD-WAN health failure can remove a member's route from the link load-balancing candidate set, a mechanism intended to explain why a failed WAN member stops being considered for new forwarding rather than the requested ‘Use a BGP learned private prefix’ control. The stated task instead is to obtain branch or data-center destinations without maintaining individual manual static routes, and adjusting ‘Inspect route withdrawal after health failure’ would not deliver ‘Use a BGP learned private prefix’. For the ‘Inspect route withdrawal after health failure’ alternative to ‘Use a BGP learned private prefix’, a failed SLA state can change route eligibility without a physical link-down event.
C:A destination-specific static route referencing the overlay zone makes private routes accessible to SD-WAN selection, a mechanism intended to reach an on-premises network across an IPsec overlay SD-WAN group rather than the requested ‘Use a BGP learned private prefix’ control. The stated task instead is to obtain branch or data-center destinations without maintaining individual manual static routes, and adjusting ‘Configure a static partner route through overlay zone’ would not deliver ‘Use a BGP learned private prefix’. For the ‘Configure a static partner route through overlay zone’ alternative to ‘Use a BGP learned private prefix’, the remote peer must also know a return path to the local subnet.
D:Bidirectional reachability requires the remote hub or server-side router to return traffic to the client prefix, a mechanism intended to repair one-way traffic where forward packets reach the data center but replies do not rather than the requested ‘Use a BGP learned private prefix’ control. The stated task instead is to obtain branch or data-center destinations without maintaining individual manual static routes, and adjusting ‘Confirm return route for remote private access’ would not deliver ‘Use a BGP learned private prefix’. For the ‘Confirm return route for remote private access’ alternative to ‘Use a BGP learned private prefix’, forward-route success is insufficient for stateful end-to-end communication.
Question 344
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 explain why a failed WAN member stops being considered for new forwarding?
- ARP or neighbor resolution and route lookup identify the reachable gateway.
- The route view includes the intended equal-cost candidates for that prefix.
- A route lookup shows the expected egress interface and reachable next hop.
- Route and health-check diagnostics show the failed member and available alternate.
- The routing table has a valid longer-prefix route to the partner CIDR.
Explanation
Correct Answer
D:This checks ‘Inspect route withdrawal after health failure’ at the correct operational boundary: SD-WAN health failure can remove a member's route from the link load-balancing candidate set. It demonstrates the specific capability to explain why a failed WAN member stops being considered for new forwarding in a test lab containing an overlay tunnel and two underlay next hops; deployment should additionally respect the constraint: A failed SLA state can change route eligibility without a physical link-down event.
Incorrect Answers
A:That observation belongs to ‘Check the route's next hop reachability’, not ‘Inspect route withdrawal after health failure’; its purpose is to differentiate a configured route from an actually usable gateway on a WAN link, the underlying behavior is that forwarding requires that the selected next hop can be resolved and reached via the member. The reviewer is instead verifying ‘Inspect route withdrawal after health failure’ for a test lab containing an overlay tunnel and two underlay next hops, not the evidence produced by ‘Check the route's next hop reachability’.
B:That observation belongs to ‘Use ECMP-compatible route candidates’, not ‘Inspect route withdrawal after health failure’; its purpose is to make multiple eligible equal-cost paths available for subsequent SD-WAN decisions, the underlying behavior is that equal Cost Multi-Path allows compatible routes to coexist as candidates when distance and priority permit. The reviewer is instead verifying ‘Inspect route withdrawal after health failure’ for a test lab containing an overlay tunnel and two underlay next hops, not the evidence produced by ‘Use ECMP-compatible route candidates’.
C:That observation belongs to ‘Verify the forwarding information base’, not ‘Inspect route withdrawal after health failure’; 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 ‘Inspect route withdrawal after health failure’ for a test lab containing an overlay tunnel and two underlay next hops, not the evidence produced by ‘Verify the forwarding information base’.
E:That observation belongs to ‘Prefer a more specific prefix’, not ‘Inspect route withdrawal after health failure’; its purpose is to send a partner network into a private tunnel even while default internet routing is present, the underlying behavior is that longest-prefix match chooses a more specific valid destination route ahead of a broader default. The reviewer is instead verifying ‘Inspect route withdrawal after health failure’ for a test lab containing an overlay tunnel and two underlay next hops, not the evidence produced by ‘Prefer a more specific prefix’.
Question 345
During an authorized lab exercise for a security administrator refining profiles for allowed remote-user traffic, a reviewer needs proof the deployment can allow a justified business website without disabling an entire restrictive category. Which observation most directly validates it?
- The connected SaaS application's API scans produce inventory and findings about stored content.
- The selected profile explicitly performs metadata checks without claiming payload inspection.
- Only the designated URL is exempted while the category continues to be restricted.
- A test destination in the prohibited category is blocked with a web-filter log.
Explanation
Correct Answer
C:This checks ‘Use a specific URL filter exception’ at the correct operational boundary: URL-level exceptions can refine category-based web filtering when an approved exception is required. It demonstrates the specific capability to allow a justified business website without disabling an entire restrictive category in a security administrator refining profiles for allowed remote-user traffic; deployment should additionally respect the constraint: Use the narrowest necessary exception to avoid weakening protection broadly.
Incorrect Answers
A:That observation belongs to ‘Use cloud API CASB for SaaS data at rest’, not ‘Use a specific URL filter exception’; its purpose is to inspect cloud-service data through supported SaaS APIs rather than only inline user sessions, the underlying behavior is that aPI-connected CASB can examine supported SaaS tenant content and events without requiring every action to cross the inline proxy. The reviewer is instead verifying ‘Use a specific URL filter exception’ for a security administrator refining profiles for allowed remote-user traffic, not the evidence produced by ‘Use cloud API CASB for SaaS data at rest’.
B:That observation belongs to ‘Use certificate inspection for metadata-only TLS checks’, not ‘Use a specific URL filter exception’; its purpose is to inspect certificate-related connection metadata without decrypting application bodies, the underlying behavior is that certificate inspection can evaluate visible TLS metadata but does not expose encrypted HTTP payload contents. The reviewer is instead verifying ‘Use a specific URL filter exception’ for a security administrator refining profiles for allowed remote-user traffic, not the evidence produced by ‘Use certificate inspection for metadata-only TLS checks’.
D:That observation belongs to ‘Apply a web-filter category action’, not ‘Use a specific URL filter exception’; its purpose is to block a prohibited web category while allowing legitimate business browsing, the underlying behavior is that web filtering classifies requested sites and applies the configured category or URL action. The reviewer is instead verifying ‘Use a specific URL filter exception’ for a security administrator refining profiles for allowed remote-user traffic, not the evidence produced by ‘Apply a web-filter category action’.
Question 346
During an authorized lab exercise for a company enrolling remote Windows and macOS employees into FortiSASE, the incident notes state that pilot users install a generic client but lack the intended cloud service configuration. Which change is most relevant to this symptom?
- Investigate: Account for SSO precedence over other methods
- Investigate: Use preconfigured FortiClient installers
- Investigate: Match endpoint profiles to the correct user group
- Investigate: Configure agentless proxy SSO
Explanation
Correct Answer
B:The symptom identifies the missing operational behavior: the FortiSASE onboarding flow can provide prepared FortiClient installers that users install on their devices. For a company enrolling remote Windows and macOS employees into FortiSASE, a direct diagnostic confirmation would be that the installed agent registers to the correct FortiSASE tenant using its onboarding configuration; during repair, the device must be supported and permitted to run FortiClient.
Incorrect Answers
A:Enabling FortiSASE SSO takes precedence over previously configured user authentication methods, which serves the different requirement to avoid expecting local or RADIUS credentials to work after enabling SAML SSO instead of the behavior delivered by ‘Use preconfigured FortiClient installers’. If that component were misconfigured, a more characteristic finding would be that an old LDAP-based login stops working immediately after the SAML SSO cutover; the actual report concerns pilot users install a generic client but lack the intended cloud service configuration at a company enrolling remote Windows and macOS employees into FortiSASE.
C: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 ‘Use preconfigured FortiClient installers’. 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 pilot users install a generic client but lack the intended cloud service configuration at a company enrolling remote Windows and macOS employees into FortiSASE.
D: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 ‘Use preconfigured FortiClient installers’. 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 pilot users install a generic client but lack the intended cloud service configuration at a company enrolling remote Windows and macOS employees into FortiSASE.
Question 347
Within a private-access rollout spanning two data-center hubs, the operator applies the control ‘Allow security PoP access to private applications’ as part of an effort to permit cloud-originated SPA traffic through the data-center firewall policy. Which operating behavior should the team expect?
- Private or split-DNS settings direct internal-name lookups to appropriate enterprise DNS servers.
- Health and service-connection priorities can influence which reachable private hub path is preferred.
- Hub-side FortiGate policies authorize FortiSASE service traffic toward the protected servers.
- A supported FortiGate branch on-ramp can steer site traffic to FortiSASE enforcement PoPs.
- An IPsec-based on-ramp encapsulates site traffic for cloud delivery over the public underlay.
Explanation
Correct Answer
C:‘Allow security PoP access to private applications’ is used to permit cloud-originated SPA traffic through the data-center firewall policy in a private-access rollout spanning two data-center hubs; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that an explicit hub policy accepts the intended PoP-to-server application flow; the rollout must also respect this constraint: Routing reachability and firewall permission must both be satisfied.
Incorrect Answers
A:The described behavior is part of ‘Configure DNS resolution for private names’, used to let remote users resolve internal application FQDNs to protected addresses instead of the role of ‘Allow security PoP access to private applications’. In contrast to ‘Configure DNS resolution for private names’, ‘Allow security PoP access to private applications’ follows a different mechanism: hub-side FortiGate policies authorize FortiSASE service traffic toward the protected servers. Treating ‘Configure DNS resolution for private names’ as equivalent would not address BGP and tunnels are up yet all application SYN packets are denied at the data-center perimeter in a private-access rollout spanning two data-center hubs.
B: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 ‘Allow security PoP access to private applications’. In contrast to ‘Select hub path using SLA health’, ‘Allow security PoP access to private applications’ follows a different mechanism: hub-side FortiGate policies authorize FortiSASE service traffic toward the protected servers. Treating ‘Select hub path using SLA health’ as equivalent would not address BGP and tunnels are up yet all application SYN packets are denied at the data-center perimeter in a private-access rollout spanning two data-center hubs.
D:The described behavior is part of ‘Integrate branch SD-WAN with FortiSASE on-ramp’, used to send on-site user internet traffic to FortiSASE cloud inspection using a supported branch edge instead of the role of ‘Allow security PoP access to private applications’. In contrast to ‘Integrate branch SD-WAN with FortiSASE on-ramp’, ‘Allow security PoP access to private applications’ follows a different mechanism: hub-side FortiGate policies authorize FortiSASE service traffic toward the protected servers. Treating ‘Integrate branch SD-WAN with FortiSASE on-ramp’ as equivalent would not address BGP and tunnels are up yet all application SYN packets are denied at the data-center perimeter in a private-access rollout spanning two data-center hubs.
E:The described behavior is part of ‘Use IPsec transport for the SASE branch connection’, used to carry branch traffic securely across an untrusted ISP toward a SASE service edge instead of the role of ‘Allow security PoP access to private applications’. In contrast to ‘Use IPsec transport for the SASE branch connection’, ‘Allow security PoP access to private applications’ follows a different mechanism: hub-side FortiGate policies authorize FortiSASE service traffic toward the protected servers. Treating ‘Use IPsec transport for the SASE branch connection’ as equivalent would not address BGP and tunnels are up yet all application SYN packets are denied at the data-center perimeter in a private-access rollout spanning two data-center hubs.
Question 348
For a help desk investigating a short cloud access degradation, a review of the current state finds that operators compare total traffic only and miss a rise in blocked high-risk web requests. Which configuration area most directly addresses this?
- Investigate: Review application usage reports
- Investigate: Trend security events by category
- Investigate: Compare user traffic volume trends
- Investigate: Correlate policy action with destination risk
Explanation
Correct Answer
B:The symptom identifies the missing operational behavior: security reporting aggregates action and threat categories so changes can be compared across time. For a help desk investigating a short cloud access degradation, a direct diagnostic confirmation would be that before-and-after summaries show the relevant security category event counts; during repair, changes in log policy or user population must be considered before claiming a causal improvement.
Incorrect Answers
A:Application analytics classify observed traffic into recognizable applications for reporting, which serves the different requirement to identify which SaaS or application class dominates inspected remote traffic instead of the behavior delivered by ‘Trend security events by category’. If that component were misconfigured, a more characteristic finding would be that the help desk cannot determine whether collaboration usage or software updates caused an increase; the actual report concerns operators compare total traffic only and miss a rise in blocked high-risk web requests at a help desk investigating a short cloud access degradation.
C:User traffic analytics aggregate bytes and sessions by identity and time for usage investigation, which serves the different requirement to find which authenticated population caused a sustained increase in cloud egress instead of the behavior delivered by ‘Trend security events by category’. If that component were misconfigured, a more characteristic finding would be that an ISP usage spike is blamed on anonymous traffic without identifying the active user groups; the actual report concerns operators compare total traffic only and miss a rise in blocked high-risk web requests at a help desk investigating a short cloud access degradation.
D:Security analytics can group blocked traffic by destination or policy to reveal recurring patterns, which serves the different requirement to identify repeated attempts to reach restricted destinations across remote users instead of the behavior delivered by ‘Trend security events by category’. If that component were misconfigured, a more characteristic finding would be that a burst of denials is reported without knowing whether one bad domain or many sites were involved; the actual report concerns operators compare total traffic only and miss a rise in blocked high-risk web requests at a help desk investigating a short cloud access degradation.
Question 349
During an authorized lab exercise for a warehouse where a primary fiber WAN and a standby broadband WAN feed the same firewall, the deployment standard specifies the control ‘Set a static WAN member gateway’ to reach an ISP next hop on a manually numbered uplink. Which functional description matches it?
- A statically addressed SD-WAN member must use the reachable ISP next hop for proper packet forwarding.
- A zone groups SD-WAN members for firewall policies, static routes, and service rules without merging the physical circuits.
- SD-WAN creates selectable member objects while retaining each interface's underlying addressing and link state.
- An SD-WAN member on a DHCP WAN can inherit the gateway learned from the DHCP interface.
Explanation
Correct Answer
A:‘Set a static WAN member gateway’ is used to reach an ISP next hop on a manually numbered uplink in a warehouse where a primary fiber WAN and a standby broadband WAN feed the same firewall; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the member gateway matches the adjacent router on that circuit; the rollout must also respect this constraint: Verify the next hop is reachable on the configured interface subnet.
Incorrect Answers
B:The described behavior is part of ‘Configure an SD-WAN zone’, used to use a common logical outgoing interface for two alternate WAN circuits instead of the role of ‘Set a static WAN member gateway’. In contrast to ‘Configure an SD-WAN zone’, ‘Set a static WAN member gateway’ follows a different mechanism: a statically addressed SD-WAN member must use the reachable ISP next hop for proper packet forwarding. Treating ‘Configure an SD-WAN zone’ as equivalent would not address the link shows carrier but packets are sent toward an incorrect next-hop address in a warehouse where a primary fiber WAN and a standby broadband WAN feed the same firewall.
C:The described behavior is part of ‘Enable SD-WAN member selection’, used to place two independently addressed internet interfaces under centralized path selection instead of the role of ‘Set a static WAN member gateway’. In contrast to ‘Enable SD-WAN member selection’, ‘Set a static WAN member gateway’ follows a different mechanism: a statically addressed SD-WAN member must use the reachable ISP next hop for proper packet forwarding. Treating ‘Enable SD-WAN member selection’ as equivalent would not address the link shows carrier but packets are sent toward an incorrect next-hop address in a warehouse where a primary fiber WAN and a standby broadband WAN feed the same firewall.
D:The described behavior is part of ‘Use DHCP-provided WAN gateway’, used to keep a dynamically assigned ISP next hop aligned with lease changes instead of the role of ‘Set a static WAN member gateway’. In contrast to ‘Use DHCP-provided WAN gateway’, ‘Set a static WAN member gateway’ follows a different mechanism: a statically addressed SD-WAN member must use the reachable ISP next hop for proper packet forwarding. Treating ‘Use DHCP-provided WAN gateway’ as equivalent would not address the link shows carrier but packets are sent toward an incorrect next-hop address in a warehouse where a primary fiber WAN and a standby broadband WAN feed the same firewall.
Question 350
Within a branch outage review comparing session entries and SLA histories, after the rollout, operators find that the standby uplink appears up at layer one but is excluded as unhealthy. Where should they focus troubleshooting?
- Investigate: Inspect member health-check output
- Investigate: Correlate a failover event with SLA history
- Investigate: Use SD-WAN service4 diagnostics
- Investigate: Inspect selected member in service diagnostics
- Investigate: Use member diagnostics
Explanation
Correct Answer
A:The symptom identifies the missing operational behavior: health-check diagnostics expose alive state, loss, latency, jitter, and SLA qualification. For a branch outage review comparing session entries and SLA histories, a direct diagnostic confirmation would be that the relevant health-check record identifies the failed metric or probe state; during repair, correlate the event to the health-check target and time of the complaint.
Incorrect Answers
B: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 ‘Inspect member health-check output’. 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 the standby uplink appears up at layer one but is excluded as unhealthy at a branch outage review comparing session entries and SLA histories.
C: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 ‘Inspect member health-check output’. 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 the standby uplink appears up at layer one but is excluded as unhealthy at a branch outage review comparing session entries and SLA histories.
D:SD-WAN service diagnostics show selected members, eligibility, and rule selection behavior, which serves the different requirement to establish which egress candidate an SD-WAN service is actively using instead of the behavior delivered by ‘Inspect member health-check output’. If that component were misconfigured, a more characteristic finding would be that the administrator sees unexpected carrier billing but has not confirmed the selected member; the actual report concerns the standby uplink appears up at layer one but is excluded as unhealthy at a branch outage review comparing session entries and SLA histories.
E:Member diagnostic output lists interface binding and operational SD-WAN member information, which serves the different requirement to check the configured gateway, status, and identity of a suspect SD-WAN member instead of the behavior delivered by ‘Inspect member health-check output’. If that component were misconfigured, a more characteristic finding would be that a service refers to member sequence 2 but its actual bound WAN interface is unknown; the actual report concerns the standby uplink appears up at layer one but is excluded as unhealthy at a branch outage review comparing session entries and SLA histories.