Question 500
In a change-control meeting for a global remote-user rollout with separate employee and contractor policies, acceptance testing shows that directory staff are not visible to SASE policy although the directory contains them. Which control should be investigated first?
- Investigate: Import users through LDAP
- Investigate: Deploy FortiClient using enterprise management
- Investigate: Match endpoint profiles to the correct user group
- Investigate: Configure agentless proxy SSO
Explanation
Correct Answer
A:The symptom identifies the missing operational behavior: LDAP integration allows FortiSASE to reference directory accounts and user groups. For a global remote-user rollout with separate employee and contractor policies, a direct diagnostic confirmation would be that the configured LDAP source resolves expected groups and authenticated users; during repair, FortiSASE must reach the directory service through its permitted network path.
Incorrect Answers
B:Group policy or mobile device management can deploy prepared FortiClient packages to managed endpoints, which serves the different requirement to roll out FortiClient at scale without requiring hundreds of manual installer sessions instead of the behavior delivered by ‘Import users through LDAP’. If that component were misconfigured, a more characteristic finding would be that a mass enrollment depends on each employee manually finding and configuring a local installer; the actual report concerns directory staff are not visible to SASE policy although the directory contains them at a global remote-user rollout with separate employee and contractor policies.
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 ‘Import users through LDAP’. 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 directory staff are not visible to SASE policy although the directory contains them at a global remote-user rollout with separate employee and contractor policies.
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 ‘Import users through LDAP’. 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 directory staff are not visible to SASE policy although the directory contains them at a global remote-user rollout with separate employee and contractor policies.
Question 501
During an authorized lab exercise for a monitoring dashboard where health status disagrees with user experience, a pilot is about to enable ‘Use member diagnostics’. Which precaution is most closely tied to this choice?
- Displayed member preference is not equivalent to proof that a specific session matched.
- Correlate the event to the health-check target and time of the complaint.
- Member identity should be resolved before interpreting service-rule candidate lists.
- Use the IPv6-specific counterpart when investigating IPv6 service steering.
Explanation
Correct Answer
C:This condition matters for ‘Use member diagnostics’ because member diagnostic output lists interface binding and operational SD-WAN member information. Omitting the relevant safeguard can produce a service refers to member sequence 2 but its actual bound WAN interface is unknown; a successful test at a monitoring dashboard where health status disagrees with user experience would instead demonstrate that the member command maps sequence number to interface and configured gateway.
Incorrect Answers
A:The condition is associated with ‘Inspect selected member in service diagnostics’, a mechanism used to establish which egress candidate an SD-WAN service is actively using instead of ‘Use member diagnostics’, because SD-WAN service diagnostics show selected members, eligibility, and rule selection behavior. For ‘Use member diagnostics’, unlike ‘Inspect selected member in service diagnostics’, the characteristic failure would be a service refers to member sequence 2 but its actual bound WAN interface is unknown, which this alternative prerequisite would not directly address at a monitoring dashboard where health status disagrees with user experience.
B:The condition is associated with ‘Inspect member health-check output’, a mechanism used to explain why a link was removed from service despite remaining physically up instead of ‘Use member diagnostics’, because health-check diagnostics expose alive state, loss, latency, jitter, and SLA qualification. For ‘Use member diagnostics’, unlike ‘Inspect member health-check output’, the characteristic failure would be a service refers to member sequence 2 but its actual bound WAN interface is unknown, which this alternative prerequisite would not directly address at a monitoring dashboard where health status disagrees with user experience.
D:The condition is associated with ‘Use SD-WAN service4 diagnostics’, a mechanism used to examine IPv4 SD-WAN rule selection rather than a generic interface status page instead of ‘Use member diagnostics’, because the service4 diagnostic command exposes IPv4 rule modes, matched criteria, and selected candidates. For ‘Use member diagnostics’, unlike ‘Use SD-WAN service4 diagnostics’, the characteristic failure would be a service refers to member sequence 2 but its actual bound WAN interface is unknown, which this alternative prerequisite would not directly address at a monitoring dashboard where health status disagrees with user experience.
Question 502
During an authorized lab exercise for a SASE change-control review using an authorized test identity, a pilot is about to enable ‘Separate internet and private access policies’. Which precaution is most closely tied to this choice?
- Certificate deployment must be coordinated with inspection and endpoint management.
- Authentication source membership must be available for identity-based rule evaluation.
- Scope and privilege should be limited to the operator's actual duties.
- Private resource reachability needs a supported SPA design in addition to SIA controls.
Explanation
Correct Answer
D:This condition matters for ‘Separate internet and private access policies’ because SIA and SPA use distinct routing and policy constructs despite sharing the FortiSASE service. Omitting the relevant safeguard can produce an internal application is evaluated only as a generic public web destination; a successful test at a SASE change-control review using an authorized test identity would instead demonstrate that the design documents and logs show separate SIA and SPA traffic paths.
Incorrect Answers
A:The condition is associated with ‘Configure SASE certificate trust’, a mechanism used to avoid TLS warnings and ensure clients trust the cloud security inspection certificate instead of ‘Separate internet and private access policies’, because when deep inspection is used, managed endpoints need the appropriate inspection CA trust anchor. For ‘Separate internet and private access policies’, unlike ‘Configure SASE certificate trust’, the characteristic failure would be an internal application is evaluated only as a generic public web destination, which this alternative prerequisite would not directly address at a SASE change-control review using an authorized test identity.
B:The condition is associated with ‘Organize SASE users into policy groups’, a mechanism used to apply different web access controls to developers and finance staff instead of ‘Separate internet and private access policies’, because user groups provide a membership basis for matching different FortiSASE access policies. For ‘Separate internet and private access policies’, unlike ‘Organize SASE users into policy groups’, the characteristic failure would be an internal application is evaluated only as a generic public web destination, which this alternative prerequisite would not directly address at a SASE change-control review using an authorized test identity.
C:The condition is associated with ‘Assign FortiSASE administrator access’, a mechanism used to let a delegated operator manage the cloud configuration without sharing the primary account instead of ‘Separate internet and private access policies’, because distinct authorized administrators enable accountable management while the original account retains ownership. For ‘Separate internet and private access policies’, unlike ‘Assign FortiSASE administrator access’, the characteristic failure would be an internal application is evaluated only as a generic public web destination, which this alternative prerequisite would not directly address at a SASE change-control review using an authorized test identity.
Question 503
During an authorized lab exercise for an enterprise interconnecting SD-WAN overlays and cloud security edges, a pilot is about to enable ‘Use SD-WAN private access for TCP and UDP’. Which precaution is most closely tied to this choice?
- Make the observed steering decision consistent with routing, policy, and tunnel state.
- Branch integration requires transport reachability and matching on-ramp security policy.
- Choose the private-access architecture according to protocol and trust requirements.
- The protected data-center prefixes need return routes toward FortiSASE clients.
- Autonomous system settings and route filters must agree across peers.
- The FortiGate ZTNA server, access policy, and required client posture must be configured.
Explanation
Correct Answer
C:This condition matters for ‘Use SD-WAN private access for TCP and UDP’ because an SD-WAN-based SPA design can provide routed access to private TCP and UDP applications. Omitting the relevant safeguard can produce the organization requires an internal UDP service that a TCP-only application proxy cannot carry; a successful test at an enterprise interconnecting SD-WAN overlays and cloud security edges would instead demonstrate that the routed SPA service connection reaches the approved UDP application behind the hub.
Incorrect Answers
A:The condition is associated with ‘Verify site-based SASE traffic steering’, a mechanism used to differentiate local branch DIA from traffic genuinely sent to cloud enforcement instead of ‘Use SD-WAN private access for TCP and UDP’, because site-based on-ramp configuration determines which branch flows are forwarded into FortiSASE. For ‘Use SD-WAN private access for TCP and UDP’, unlike ‘Verify site-based SASE traffic steering’, the characteristic failure would be the organization requires an internal UDP service that a TCP-only application proxy cannot carry, which this alternative prerequisite would not directly address at an enterprise interconnecting SD-WAN overlays and cloud security edges.
B:The condition is associated with ‘Integrate branch SD-WAN with FortiSASE on-ramp’, a mechanism used to send on-site user internet traffic to FortiSASE cloud inspection using a supported branch edge instead of ‘Use SD-WAN private access for TCP and UDP’, because a supported FortiGate branch on-ramp can steer site traffic to FortiSASE enforcement PoPs. For ‘Use SD-WAN private access for TCP and UDP’, unlike ‘Integrate branch SD-WAN with FortiSASE on-ramp’, the characteristic failure would be the organization requires an internal UDP service that a TCP-only application proxy cannot carry, which this alternative prerequisite would not directly address at an enterprise interconnecting SD-WAN overlays and cloud security edges.
D:The condition is associated with ‘Use FortiGate as a private-access hub’, a mechanism used to connect remote FortiSASE clients to data-center applications protected behind a FortiGate instead of ‘Use SD-WAN private access for TCP and UDP’, because FortiGate can provide the secure private access hub that forwards authorized cloud-to-private traffic. For ‘Use SD-WAN private access for TCP and UDP’, unlike ‘Use FortiGate as a private-access hub’, the characteristic failure would be the organization requires an internal UDP service that a TCP-only application proxy cannot carry, which this alternative prerequisite would not directly address at an enterprise interconnecting SD-WAN overlays and cloud security edges.
E:The condition is associated with ‘Establish BGP with the SPA hub’, a mechanism used to exchange private network reachability dynamically between FortiSASE and a FortiGate hub instead of ‘Use SD-WAN private access for TCP and UDP’, because a supported SPA BGP design learns and advertises routes over the selected overlay connection. For ‘Use SD-WAN private access for TCP and UDP’, unlike ‘Establish BGP with the SPA hub’, the characteristic failure would be the organization requires an internal UDP service that a TCP-only application proxy cannot carry, which this alternative prerequisite would not directly address at an enterprise interconnecting SD-WAN overlays and cloud security edges.
F:The condition is associated with ‘Use ZTNA application proxy for a protected TCP app’, a mechanism used to publish a narrowly scoped internal TCP application through a FortiGate ZTNA gateway instead of ‘Use SD-WAN private access for TCP and UDP’, because ZTNA private access targets authorized TCP applications rather than granting generic network reachability. For ‘Use SD-WAN private access for TCP and UDP’, unlike ‘Use ZTNA application proxy for a protected TCP app’, the characteristic failure would be the organization requires an internal UDP service that a TCP-only application proxy cannot carry, which this alternative prerequisite would not directly address at an enterprise interconnecting SD-WAN overlays and cloud security edges.
Question 504
For an insurance branch with a real-time application and a bulk-backup workload, an audit asks for evidence that the team can apply a special path selection only to traffic originating in one department network. Which finding would answer that question?
- The rule matches the intended TCP or UDP service and leaves other ports to later rules.
- The matched rule contains the required source address object and other subnets bypass it.
- The SD-WAN rule matches the designated Internet Service Database object.
- The application-control internet-service list contains the learned application destination tuple.
Explanation
Correct Answer
B:This checks ‘Match a source subnet in an SD-WAN rule’ at the correct operational boundary: source-address criteria restrict SD-WAN rule matching to sessions from specified client address ranges. It demonstrates the specific capability to apply a special path selection only to traffic originating in one department network in an insurance branch with a real-time application and a bulk-backup workload; deployment should additionally respect the constraint: Source steering does not itself authenticate an individual user.
Incorrect Answers
A:That observation belongs to ‘Match service protocol and port’, not ‘Match a source subnet in an SD-WAN rule’; its purpose is to steer a well-defined TCP service without affecting unrelated traffic to the same server, the underlying behavior is that service matching narrows selection by transport protocol and destination-port criteria. The reviewer is instead verifying ‘Match a source subnet in an SD-WAN rule’ for an insurance branch with a real-time application and a bulk-backup workload, not the evidence produced by ‘Match service protocol and port’.
C:That observation belongs to ‘Match an Internet Service Database destination’, not ‘Match a source subnet in an SD-WAN rule’; 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 ‘Match a source subnet in an SD-WAN rule’ for an insurance branch with a real-time application and a bulk-backup workload, not the evidence produced by ‘Match an Internet Service Database destination’.
D:That observation belongs to ‘Consider first-flow application recognition’, not ‘Match a source subnet in an SD-WAN rule’; its purpose is to explain why the first newly observed app session may not match application-based steering immediately, the underlying behavior is that FortiOS learns application signatures and destination tuples from inspected sessions for subsequent application-based matches. The reviewer is instead verifying ‘Match a source subnet in an SD-WAN rule’ for an insurance branch with a real-time application and a bulk-backup workload, not the evidence produced by ‘Consider first-flow application recognition’.
Question 505
For a company enrolling remote Windows and macOS employees into FortiSASE, an audit asks for evidence that the team can associate proxied browser traffic with enterprise user identity during secure web gateway inspection. Which finding would answer that question?
- Managed devices receive the intended FortiClient package through centralized deployment.
- New login attempts follow the configured IdP authentication flow.
- A controlled browser request establishes an SSO user session for the cloud proxy.
- Browser web requests traverse the configured FortiSASE SWG proxy.
Explanation
Correct Answer
C:This checks ‘Configure agentless proxy SSO’ at the correct operational boundary: sWG SSO authenticates a web proxy session using the configured identity provider. It demonstrates the specific capability to associate proxied browser traffic with enterprise user identity during secure web gateway inspection in a company enrolling remote Windows and macOS employees into FortiSASE; deployment should additionally respect the constraint: Proxy SSO often depends on compatible deep inspection and IdP reachability.
Incorrect Answers
A:That observation belongs to ‘Deploy FortiClient using enterprise management’, not ‘Configure agentless proxy SSO’; its purpose is to roll out FortiClient at scale without requiring hundreds of manual installer sessions, the underlying behavior is that group policy or mobile device management can deploy prepared FortiClient packages to managed endpoints. The reviewer is instead verifying ‘Configure agentless proxy SSO’ for a company enrolling remote Windows and macOS employees into FortiSASE, not the evidence produced by ‘Deploy FortiClient using enterprise management’.
B:That observation belongs to ‘Account for SSO precedence over other methods’, not ‘Configure agentless proxy SSO’; its purpose is to avoid expecting local or RADIUS credentials to work after enabling SAML SSO, the underlying behavior is that enabling FortiSASE SSO takes precedence over previously configured user authentication methods. The reviewer is instead verifying ‘Configure agentless proxy SSO’ for a company enrolling remote Windows and macOS employees into FortiSASE, not the evidence produced by ‘Account for SSO precedence over other methods’.
D:That observation belongs to ‘Enroll an agentless web user’, not ‘Configure agentless proxy SSO’; its purpose is to protect an unmanaged Chromebook's HTTP and HTTPS browsing without installing FortiClient, the underlying behavior is that agentless secure web gateway access uses explicit proxy steering rather than a full-device agent tunnel. The reviewer is instead verifying ‘Configure agentless proxy SSO’ for a company enrolling remote Windows and macOS employees into FortiSASE, not the evidence produced by ‘Enroll an agentless web user’.
Question 506
At a private-access rollout spanning two data-center hubs, the change board is evaluating ‘Allow security PoP access to private applications’. Which technical consideration must be built into the plan?
- A working tunnel does not automatically advertise every internal route.
- Routing reachability and firewall permission must both be satisfied.
- IKE negotiations and underlay routing must work before traffic steering over the tunnel.
- The alternate hub must advertise the needed application prefix to take over.
Explanation
Correct Answer
B:This condition matters for ‘Allow security PoP access to private applications’ because hub-side FortiGate policies authorize FortiSASE service traffic toward the protected servers. Omitting the relevant safeguard can produce BGP and tunnels are up yet all application SYN packets are denied at the data-center perimeter; a successful test at a private-access rollout spanning two data-center hubs would instead demonstrate that an explicit hub policy accepts the intended PoP-to-server application flow.
Incorrect Answers
A:The condition is associated with ‘Advertise internal prefixes to SPA routing’, a mechanism used to make specific private data-center networks reachable from security PoPs instead of ‘Allow security PoP access to private applications’, because routing advertisement or static private routes informs FortiSASE how to reach protected application subnets. For ‘Allow security PoP access to private applications’, unlike ‘Advertise internal prefixes to SPA routing’, the characteristic failure would be BGP and tunnels are up yet all application SYN packets are denied at the data-center perimeter, which this alternative prerequisite would not directly address at a private-access rollout spanning two data-center hubs.
C:The condition is associated with ‘Use IPsec transport for the SASE branch connection’, a mechanism used to carry branch traffic securely across an untrusted ISP toward a SASE service edge instead of ‘Allow security PoP access to private applications’, because an IPsec-based on-ramp encapsulates site traffic for cloud delivery over the public underlay. For ‘Allow security PoP access to private applications’, unlike ‘Use IPsec transport for the SASE branch connection’, the characteristic failure would be BGP and tunnels are up yet all application SYN packets are denied at the data-center perimeter, which this alternative prerequisite would not directly address at a private-access rollout spanning two data-center hubs.
D:The condition is associated with ‘Select hub path using SLA health’, a mechanism used to prefer a viable SPA route when one private-access connection becomes degraded instead of ‘Allow security PoP access to private applications’, because health and service-connection priorities can influence which reachable private hub path is preferred. For ‘Allow security PoP access to private applications’, unlike ‘Select hub path using SLA health’, the characteristic failure would be BGP and tunnels are up yet all application SYN packets are denied at the data-center perimeter, which this alternative prerequisite would not directly address at a private-access rollout spanning two data-center hubs.
Question 507
Within a branch FortiGate that terminates an ISP handoff and two IPsec tunnels, the team wants to avoid an ineffective configuration of ‘Create a dedicated overlay zone’. Which consideration deserves attention?
- Cost does not replace health measurements or firewall policy matching.
- The tunnel interfaces must first be configured and eligible to join SD-WAN.
- Zone placement does not automatically create a firewall rule or a route.
- Cellular availability and data cost are distinct from the SD-WAN rule's selection policy.
- Bring up the route-based tunnel and verify selectors and reachability independently.
Explanation
Correct Answer
B:This condition matters for ‘Create a dedicated overlay zone’ because overlay zones provide distinct policy and route targets for tunnel traffic bound for private networks. Omitting the relevant safeguard can produce private application traffic follows an internet egress policy instead of an overlay policy; a successful test at a branch FortiGate that terminates an ISP handoff and two IPsec tunnels would instead demonstrate that both IPsec tunnel members appear in the overlay zone and match the private route.
Incorrect Answers
A:The condition is associated with ‘Set member cost’, a mechanism used to favor a lower-priced uplink only when eligible under lowest-cost SLA rules instead of ‘Create a dedicated overlay zone’, because the cost field ranks SLA-qualified members for the Lowest Cost strategy, with smaller values preferred. For ‘Create a dedicated overlay zone’, unlike ‘Set member cost’, the characteristic failure would be private application traffic follows an internet egress policy instead of an overlay policy, which this alternative prerequisite would not directly address at a branch FortiGate that terminates an ISP handoff and two IPsec tunnels.
C:The condition is associated with ‘Assign members to the intended zone’, a mechanism used to put two ISP circuits in the internet transport zone rather than the private-overlay group instead of ‘Create a dedicated overlay zone’, because a member's zone association determines which zone-based routes and policies can use that interface. For ‘Create a dedicated overlay zone’, unlike ‘Assign members to the intended zone’, the characteristic failure would be private application traffic follows an internet egress policy instead of an overlay policy, which this alternative prerequisite would not directly address at a branch FortiGate that terminates an ISP handoff and two IPsec tunnels.
D:The condition is associated with ‘Use a FortiExtender interface member’, a mechanism used to include a cellular backup path in SD-WAN selection instead of ‘Create a dedicated overlay zone’, because a FortiExtender-provided network interface can participate as an SD-WAN member alongside wired transports. For ‘Create a dedicated overlay zone’, unlike ‘Use a FortiExtender interface member’, the characteristic failure would be private application traffic follows an internet egress policy instead of an overlay policy, which this alternative prerequisite would not directly address at a branch FortiGate that terminates an ISP handoff and two IPsec tunnels.
E:The condition is associated with ‘Use an IPsec interface as a member’, a mechanism used to apply SD-WAN selection to redundant encrypted site-to-site paths instead of ‘Create a dedicated overlay zone’, because route-based IPsec tunnel interfaces can be members whose quality is measured and selected for overlay routing. For ‘Create a dedicated overlay zone’, unlike ‘Use an IPsec interface as a member’, the characteristic failure would be private application traffic follows an internet egress policy instead of an overlay policy, which this alternative prerequisite would not directly address at a branch FortiGate that terminates an ISP handoff and two IPsec tunnels.
Question 508
Within a policy owner determining which protective control stopped a session, the configuration has been applied. Which measurement or record best confirms the goal to identify an endpoint denied for noncompliance rather than for missing network reachability?
- The DLP event identifies the matching content pattern and policy action.
- The posture status and denied policy event agree on the noncompliant device condition.
- The IPS log records an appropriate attack signature and the related action.
- A time-matched AV event shows the detection and enforced action for the download.
- The web-filter event shows the URL category and associated block action.
Explanation
Correct Answer
B:This checks ‘Correlate endpoint posture and access events’ at the correct operational boundary: endpoint and access records can show that a posture tag triggered a conditional denial. It demonstrates the specific capability to identify an endpoint denied for noncompliance rather than for missing network reachability in a policy owner determining which protective control stopped a session; deployment should additionally respect the constraint: Correlate user, device, policy and time before treating the rejection as a routing fault.
Incorrect Answers
A:That observation belongs to ‘Inspect DLP matches’, not ‘Correlate endpoint posture and access events’; its purpose is to explain which sensitive-content pattern caused a SaaS upload to be denied, the underlying behavior is that DLP logs record content-rule matches and the action taken for an inspected transfer. The reviewer is instead verifying ‘Correlate endpoint posture and access events’ for a policy owner determining which protective control stopped a session, not the evidence produced by ‘Inspect DLP matches’.
C:That observation belongs to ‘Inspect IPS threat logs’, not ‘Correlate endpoint posture and access events’; its purpose is to verify whether an exploit signature triggered inspection rather than a generic connectivity failure, the underlying behavior is that IPS events contain the signature context and configured security response for detected traffic. The reviewer is instead verifying ‘Correlate endpoint posture and access events’ for a policy owner determining which protective control stopped a session, not the evidence produced by ‘Inspect IPS threat logs’.
D:That observation belongs to ‘Inspect antivirus detection events’, not ‘Correlate endpoint posture and access events’; its purpose is to identify which inspected download was blocked for malware and under which policy, the underlying behavior is that aV logs identify signature or file detections and the security action applied to a session. The reviewer is instead verifying ‘Correlate endpoint posture and access events’ for a policy owner determining which protective control stopped a session, not the evidence produced by ‘Inspect antivirus detection events’.
E:That observation belongs to ‘Inspect web-filter category logs’, not ‘Correlate endpoint posture and access events’; its purpose is to determine whether a website was blocked by category policy rather than by transport failure, the underlying behavior is that web-filter logs associate an HTTP or HTTPS destination with category evaluation and action. The reviewer is instead verifying ‘Correlate endpoint posture and access events’ for a policy owner determining which protective control stopped a session, not the evidence produced by ‘Inspect web-filter category logs’.
Question 509
For a policy owner determining which protective control stopped a session, a maintenance plan requires the firewall team to identify an endpoint denied for noncompliance rather than for missing network reachability. Which choice is appropriate?
- Correlate endpoint posture and access events
- Inspect DNS-filter threat events
- Inspect antivirus detection events
- Inspect web-filter category logs
Explanation
Correct Answer
A:Endpoint and access records can show that a posture tag triggered a conditional denial; that scope directly serves the goal to identify an endpoint denied for noncompliance rather than for missing network reachability in a policy owner determining which protective control stopped a session. During implementation, correlate user, device, policy and time before treating the rejection as a routing fault rather than treating the configuration label as proof of working service.
Incorrect Answers
B:DNS security logs record affected domain requests and configured malicious-domain actions, a mechanism intended to identify blocked malicious name resolution before the browser opens a TCP session rather than the requested ‘Correlate endpoint posture and access events’ control. The stated task instead is to identify an endpoint denied for noncompliance rather than for missing network reachability, and adjusting ‘Inspect DNS-filter threat events’ would not deliver ‘Correlate endpoint posture and access events’. For the ‘Inspect DNS-filter threat events’ alternative to ‘Correlate endpoint posture and access events’, DNS filtering operates at name resolution, not by scanning file payloads.
C:AV logs identify signature or file detections and the security action applied to a session, a mechanism intended to identify which inspected download was blocked for malware and under which policy rather than the requested ‘Correlate endpoint posture and access events’ control. The stated task instead is to identify an endpoint denied for noncompliance rather than for missing network reachability, and adjusting ‘Inspect antivirus detection events’ would not deliver ‘Correlate endpoint posture and access events’. For the ‘Inspect antivirus detection events’ alternative to ‘Correlate endpoint posture and access events’, a traffic deny log by itself does not establish that antivirus detected malware.
D:Web-filter logs associate an HTTP or HTTPS destination with category evaluation and action, a mechanism intended to determine whether a website was blocked by category policy rather than by transport failure rather than the requested ‘Correlate endpoint posture and access events’ control. The stated task instead is to identify an endpoint denied for noncompliance rather than for missing network reachability, and adjusting ‘Inspect web-filter category logs’ would not deliver ‘Correlate endpoint posture and access events’. For the ‘Inspect web-filter category logs’ alternative to ‘Correlate endpoint posture and access events’, category decisions must be distinguished from DNS filter results and generic firewall denies.
Question 510
At a hub-and-spoke network with internet breakout and private IPsec overlays, the change request is to identify why a matching policy-route decision changes normal egress selection. Which configuration is the most direct fit?
- Validate policy routing and SD-WAN interaction
- Verify the forwarding information base
- Review route priority
- Confirm return route for remote private access
Explanation
Correct Answer
A:Policy route and SD-WAN service rules can influence forwarding decisions beyond basic destination-table lookup; that scope directly serves the goal to identify why a matching policy-route decision changes normal egress selection in a hub-and-spoke network with internet breakout and private IPsec overlays. During implementation, review configured policy-routing precedence before rewriting otherwise correct static routes rather than treating the configuration label as proof of working service.
Incorrect Answers
B:The FIB holds selected forwarding entries and is essential to actual packet delivery, a mechanism intended to confirm the FortiGate has installed a usable next hop for a destination rather than the requested ‘Validate policy routing and SD-WAN interaction’ control. The stated task instead is to identify why a matching policy-route decision changes normal egress selection, and adjusting ‘Verify the forwarding information base’ would not deliver ‘Validate policy routing and SD-WAN interaction’. For the ‘Verify the forwarding information base’ alternative to ‘Validate policy routing and SD-WAN interaction’, the SD-WAN rule must be reconciled with actual route installation.
C:Route priority can provide an additional selection differentiator when distance and prefix do not distinguish alternatives, a mechanism intended to resolve preference among otherwise comparable FortiGate route candidates rather than the requested ‘Validate policy routing and SD-WAN interaction’ control. The stated task instead is to identify why a matching policy-route decision changes normal egress selection, and adjusting ‘Review route priority’ would not deliver ‘Validate policy routing and SD-WAN interaction’. For the ‘Review route priority’ alternative to ‘Validate policy routing and SD-WAN interaction’, priority has meaning within the relevant route-selection context, not across unrelated prefixes.
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 ‘Validate policy routing and SD-WAN interaction’ control. The stated task instead is to identify why a matching policy-route decision changes normal egress selection, and adjusting ‘Confirm return route for remote private access’ would not deliver ‘Validate policy routing and SD-WAN interaction’. For the ‘Confirm return route for remote private access’ alternative to ‘Validate policy routing and SD-WAN interaction’, forward-route success is insufficient for stateful end-to-end communication.