Question 590
At a campus running FortiOS 7.6 with application-aware policies, an engineer is preparing ‘Match an Internet Service Database destination’ to identify cloud-service traffic by maintained service definitions instead of a static destination IP. Which TWO statements identify a pertinent deployment safeguard and a direct post-change validation result? Choose TWO.
- An ISDB object is not the same as a local DNS record or the name of a user group.
- Zone preference and routing reachability must point to compatible paths.
- Session logs show flows using multiple eligible SD-WAN member paths.
- The SD-WAN rule matches the designated Internet Service Database object.
- Trust and policing of DSCP markings require an appropriate network policy design.
Explanation
Correct Answers
A:This safeguard applies to ‘Match an Internet Service Database destination’, which works because internet service matching can steer flows associated with a known internet service without manually maintaining every destination subnet. Without the correct deployment condition, operators may see that a SaaS provider changes IP addresses and a hardcoded address-match rule misses new endpoints in a campus running FortiOS 7.6 with application-aware policies.
D:The observation follows from the operation of ‘Match an Internet Service Database destination’: internet service matching can steer flows associated with a known internet service without manually maintaining every destination subnet. It directly tests the requested ability to identify cloud-service traffic by maintained service definitions instead of a static destination IP in a campus running FortiOS 7.6 with application-aware policies, rather than another policy or network layer.
Incorrect Answers
B:The planning point is associated with ‘Specify an SD-WAN zone preference’, not ‘Match an Internet Service Database destination’; its real role is to restrict an application to members grouped within a chosen logical zone. The required deployment instead centers on ‘Match an Internet Service Database destination’, rather than ‘Specify an SD-WAN zone preference’; the distinct symptom to guard against is that a SaaS provider changes IP addresses and a hardcoded address-match rule misses new endpoints.
C:This result would validate ‘Enable SD-WAN rule load balancing’, not ‘Match an Internet Service Database destination’, because a load-balancing rule spreads session assignments among candidates by its configured selection behavior. That separate implementation serves distribute independent new sessions across eligible members rather than always selecting one, whereas the audit needs evidence specifically of ‘Match an Internet Service Database destination’ at a campus running FortiOS 7.6 with application-aware policies.
E:The planning point is associated with ‘Use DSCP-based SD-WAN steering’, not ‘Match an Internet Service Database destination’; its real role is to distinguish preclassified media packets from ordinary web traffic at path-selection time. The required deployment instead centers on ‘Match an Internet Service Database destination’, rather than ‘Use DSCP-based SD-WAN steering’; the distinct symptom to guard against is that a SaaS provider changes IP addresses and a hardcoded address-match rule misses new endpoints.
Question 591
Within a security team classifying devices by their current local protection state, the operator applies the control ‘Use endpoint-profile assignment for managed groups’ as part of an effort to apply a stricter posture and connection configuration to a high-risk user population. Which operating behavior should the team expect?
- Posture-based enforcement depends on updated FortiClient registration and local security-condition evaluation.
- Endpoint tagging can evaluate the presence and properties of a required client certificate.
- Endpoint profile assignment determines which device-side checks and tunnel behavior a managed group receives.
- Private access policies can use security posture tags as dynamic matching criteria.
- FortiClient evaluates defined endpoint posture conditions and associates matching endpoints with security tags.
Explanation
Correct Answer
C:‘Use endpoint-profile assignment for managed groups’ is used to apply a stricter posture and connection configuration to a high-risk user population in a security team classifying devices by their current local protection state; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the group receives the profile containing the designated posture and connection controls; the rollout must also respect this constraint: A cloud traffic policy alone does not deploy settings to FortiClient endpoints.
Incorrect Answers
A:The described behavior is part of ‘Validate fresh endpoint posture telemetry’, used to avoid relying on stale compliance information after an endpoint stops reporting to management instead of the role of ‘Use endpoint-profile assignment for managed groups’. In contrast to ‘Validate fresh endpoint posture telemetry’, ‘Use endpoint-profile assignment for managed groups’ follows a different mechanism: endpoint profile assignment determines which device-side checks and tunnel behavior a managed group receives. Treating ‘Validate fresh endpoint posture telemetry’ as equivalent would not address contractor devices use the default endpoint configuration rather than the intended restricted policy in a security team classifying devices by their current local protection state.
B:The described behavior is part of ‘Use a certificate-based posture check’, used to identify managed endpoints that carry an enterprise-issued device credential instead of the role of ‘Use endpoint-profile assignment for managed groups’. In contrast to ‘Use a certificate-based posture check’, ‘Use endpoint-profile assignment for managed groups’ follows a different mechanism: endpoint profile assignment determines which device-side checks and tunnel behavior a managed group receives. Treating ‘Use a certificate-based posture check’ as equivalent would not address contractor devices use the default endpoint configuration rather than the intended restricted policy in a security team classifying devices by their current local protection state.
D:The described behavior is part of ‘Assign compliant endpoint tags to private policies’, used to grant sensitive private access only to managed devices meeting specified security conditions instead of the role of ‘Use endpoint-profile assignment for managed groups’. In contrast to ‘Assign compliant endpoint tags to private policies’, ‘Use endpoint-profile assignment for managed groups’ follows a different mechanism: endpoint profile assignment determines which device-side checks and tunnel behavior a managed group receives. Treating ‘Assign compliant endpoint tags to private policies’ as equivalent would not address contractor devices use the default endpoint configuration rather than the intended restricted policy in a security team classifying devices by their current local protection state.
E:The described behavior is part of ‘Build a security posture tag rule’, used to label endpoints dynamically when a specified local security condition is met instead of the role of ‘Use endpoint-profile assignment for managed groups’. In contrast to ‘Build a security posture tag rule’, ‘Use endpoint-profile assignment for managed groups’ follows a different mechanism: endpoint profile assignment determines which device-side checks and tunnel behavior a managed group receives. Treating ‘Build a security posture tag rule’ as equivalent would not address contractor devices use the default endpoint configuration rather than the intended restricted policy in a security team classifying devices by their current local protection state.
Question 592
At a remote workforce with strict data-handling rules and encrypted web traffic, the rollout includes the control ‘Configure file filtering’ to block transfer of prohibited file types regardless of benign website category. Which observed mechanism is consistent with this configuration?
- Inline-CASB application control adds SaaS-aware decisions to recognized HTTP traffic traversing FortiSASE.
- An enabled antivirus inspection component examines supported file content for malicious signatures or behavior indicators.
- File Filter identifies supported file types in inspected sessions and enforces the configured file action.
- IPS analyzes supported traffic patterns against intrusion-detection signatures and configured actions.
Explanation
Correct Answer
C:‘Configure file filtering’ is used to block transfer of prohibited file types regardless of benign website category in a remote workforce with strict data-handling rules and encrypted web traffic; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that a file-filter event records the prohibited file type being blocked; the rollout must also respect this constraint: Encrypted transfers need suitable deep inspection for content-aware file filtering.
Incorrect Answers
A:The described behavior is part of ‘Use inline CASB application controls’, used to apply SaaS-specific application restrictions on inspected cloud traffic instead of the role of ‘Configure file filtering’. In contrast to ‘Use inline CASB application controls’, ‘Configure file filtering’ follows a different mechanism: file Filter identifies supported file types in inspected sessions and enforces the configured file action. Treating ‘Use inline CASB application controls’ as equivalent would not address a restricted executable file is downloaded from an otherwise approved website in a remote workforce with strict data-handling rules and encrypted web traffic.
B:The described behavior is part of ‘Apply an antivirus profile to allowed traffic’, used to detect malware payloads passing through a permitted cloud access policy instead of the role of ‘Configure file filtering’. In contrast to ‘Apply an antivirus profile to allowed traffic’, ‘Configure file filtering’ follows a different mechanism: file Filter identifies supported file types in inspected sessions and enforces the configured file action. Treating ‘Apply an antivirus profile to allowed traffic’ as equivalent would not address a restricted executable file is downloaded from an otherwise approved website in a remote workforce with strict data-handling rules and encrypted web traffic.
D:The described behavior is part of ‘Enable intrusion prevention’, used to detect and block network exploits recognized by attack signatures or protocol decoders instead of the role of ‘Configure file filtering’. In contrast to ‘Enable intrusion prevention’, ‘Configure file filtering’ follows a different mechanism: file Filter identifies supported file types in inspected sessions and enforces the configured file action. Treating ‘Enable intrusion prevention’ as equivalent would not address a restricted executable file is downloaded from an otherwise approved website in a remote workforce with strict data-handling rules and encrypted web traffic.
Question 593
For an off-site workforce where some endpoints fail compliance verification, a technical review examines the control ‘Build a security posture tag rule’ for the objective to label endpoints dynamically when a specified local security condition is met. Which statement best describes what it changes?
- Endpoint profile assignment determines which device-side checks and tunnel behavior a managed group receives.
- FortiClient evaluates defined endpoint posture conditions and associates matching endpoints with security tags.
- A configured pre-connection check can allow or deny a tunnel attempt based on an assigned posture tag.
- Posture-based enforcement depends on updated FortiClient registration and local security-condition evaluation.
Explanation
Correct Answer
B:‘Build a security posture tag rule’ is used to label endpoints dynamically when a specified local security condition is met in an off-site workforce where some endpoints fail compliance verification; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the managed device receives the intended posture tag after a matching check; the rollout must also respect this constraint: The tag logic must accurately represent the actual security requirement.
Incorrect Answers
A:The described behavior is part of ‘Use endpoint-profile assignment for managed groups’, used to apply a stricter posture and connection configuration to a high-risk user population instead of the role of ‘Build a security posture tag rule’. In contrast to ‘Use endpoint-profile assignment for managed groups’, ‘Build a security posture tag rule’ follows a different mechanism: FortiClient evaluates defined endpoint posture conditions and associates matching endpoints with security tags. Treating ‘Use endpoint-profile assignment for managed groups’ as equivalent would not address the application policy cannot distinguish secure laptops from devices missing a required check in an off-site workforce where some endpoints fail compliance verification.
C:The described behavior is part of ‘Configure pre-connection posture enforcement’, used to block an untrusted FortiClient endpoint before it establishes its protected cloud tunnel instead of the role of ‘Build a security posture tag rule’. In contrast to ‘Configure pre-connection posture enforcement’, ‘Build a security posture tag rule’ follows a different mechanism: FortiClient evaluates defined endpoint posture conditions and associates matching endpoints with security tags. Treating ‘Configure pre-connection posture enforcement’ as equivalent would not address the application policy cannot distinguish secure laptops from devices missing a required check in an off-site workforce where some endpoints fail compliance verification.
D:The described behavior is part of ‘Validate fresh endpoint posture telemetry’, used to avoid relying on stale compliance information after an endpoint stops reporting to management instead of the role of ‘Build a security posture tag rule’. In contrast to ‘Validate fresh endpoint posture telemetry’, ‘Build a security posture tag rule’ follows a different mechanism: FortiClient evaluates defined endpoint posture conditions and associates matching endpoints with security tags. Treating ‘Validate fresh endpoint posture telemetry’ as equivalent would not address the application policy cannot distinguish secure laptops from devices missing a required check in an off-site workforce where some endpoints fail compliance verification.
Question 594
Within a warehouse where a primary fiber WAN and a standby broadband WAN feed the same firewall, after the rollout, operators find that the link shows carrier but packets are sent toward an incorrect next-hop address. Where should they focus troubleshooting?
- Investigate: Enable SD-WAN member selection
- Investigate: Use DHCP-provided WAN gateway
- Investigate: Set a static WAN member gateway
- Investigate: Separate underlay and overlay SD-WAN zones
- Investigate: Install an SD-WAN default route
Explanation
Correct Answer
C:The symptom identifies the missing operational behavior: a statically addressed SD-WAN member must use the reachable ISP next hop for proper packet forwarding. For a warehouse where a primary fiber WAN and a standby broadband WAN feed the same firewall, a direct diagnostic confirmation would be that the member gateway matches the adjacent router on that circuit; during repair, verify the next hop is reachable on the configured interface subnet.
Incorrect Answers
A:SD-WAN creates selectable member objects while retaining each interface's underlying addressing and link state, which serves the different requirement to place two independently addressed internet interfaces under centralized path selection instead of the behavior delivered by ‘Set a static WAN member gateway’. If that component were misconfigured, a more characteristic finding would be that the WAN ports are up but neither is listed as a selectable SD-WAN member; the actual report concerns the link shows carrier but packets are sent toward an incorrect next-hop address at a warehouse where a primary fiber WAN and a standby broadband WAN feed the same firewall.
B:An SD-WAN member on a DHCP WAN can inherit the gateway learned from the DHCP interface, which serves the different requirement to keep a dynamically assigned ISP next hop aligned with lease changes instead of the behavior delivered by ‘Set a static WAN member gateway’. If that component were misconfigured, a more characteristic finding would be that the dynamic WAN lease renews but a hard-coded obsolete gateway is still being used; the actual report concerns the link shows carrier but packets are sent toward an incorrect next-hop address at a warehouse where a primary fiber WAN and a standby broadband WAN feed the same firewall.
D:Distinct SD-WAN zones make underlay internet circuits and overlay tunnels separate logical choices, which serves the different requirement to keep ISP transports and IPsec private overlays independently selectable in policy instead of the behavior delivered by ‘Set a static WAN member gateway’. If that component were misconfigured, a more characteristic finding would be that an internal application policy unintentionally steers directly to a public ISP underlay; the actual report concerns the link shows carrier but packets are sent toward an incorrect next-hop address at a warehouse where a primary fiber WAN and a standby broadband WAN feed the same firewall.
E:A default static route whose outgoing interface is the SD-WAN zone supplies route reachability before path steering, which serves the different requirement to provide a route for internet-bound traffic through the SD-WAN aggregate instead of the behavior delivered by ‘Set a static WAN member gateway’. If that component were misconfigured, a more characteristic finding would be that SD-WAN members are healthy but the forwarding table has no matching default route; the actual report concerns the link shows carrier but packets are sent toward an incorrect next-hop address at a warehouse where a primary fiber WAN and a standby broadband WAN feed the same firewall.
Question 595
For a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs, a review of the current state finds that the drained circuit is still chosen for new flows during maintenance. Which configuration area most directly addresses this?
- Investigate: Use an isolated single-member zone
- Investigate: Define the member health-check source
- Investigate: Disable a maintenance member
- Investigate: Move a member between zones
Explanation
Correct Answer
C:The symptom identifies the missing operational behavior: disabling an SD-WAN member removes it from eligible SD-WAN selection without requiring deletion of its configuration. For a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs, a direct diagnostic confirmation would be that member status shows the maintenance circuit disabled and other members eligible; during repair, ensure remaining members provide viable routes and sufficient capacity.
Incorrect Answers
A:A zone can contain one member, allowing special security or routing treatment for that interface, which serves the different requirement to apply a dedicated policy to one exceptional transport while keeping other members grouped instead of the behavior delivered by ‘Disable a maintenance member’. If that component were misconfigured, a more characteristic finding would be that a regulated circuit receives the same outbound policy as every generic ISP member; the actual report concerns the drained circuit is still chosen for new flows during maintenance at a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs.
B:A member health-check source setting controls the source IP used by health probes to a monitored server, which serves the different requirement to send probes using the correct reachable source address on a multiaddress uplink instead of the behavior delivered by ‘Disable a maintenance member’. If that component were misconfigured, a more characteristic finding would be that probes are rejected because they originate from an unexpected secondary interface address; the actual report concerns the drained circuit is still chosen for new flows during maintenance at a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs.
D:Reassigning the member to a different zone changes its logical policy and rule membership, which serves the different requirement to change how one interface is referenced by routes and policies without rebuilding the WAN port instead of the behavior delivered by ‘Disable a maintenance member’. If that component were misconfigured, a more characteristic finding would be that the port works but is reachable only through policies for the old zone; the actual report concerns the drained circuit is still chosen for new flows during maintenance at a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs.
Question 596
During an authorized lab exercise for an onboarding pilot with a small set of managed test laptops, the acceptance criteria require the team to avoid expecting local or RADIUS credentials to work after enabling SAML SSO. Which control meets that requirement?
- Configure RADIUS authentication
- Account for SSO precedence over other methods
- Use preconfigured FortiClient installers
- Maintain FortiClient tenant registration
Explanation
Correct Answer
B:Enabling FortiSASE SSO takes precedence over previously configured user authentication methods; that scope directly serves the goal to avoid expecting local or RADIUS credentials to work after enabling SAML SSO in an onboarding pilot with a small set of managed test laptops. During implementation, plan identity migration and test group mapping before enabling organizational SSO rather than treating the configuration label as proof of working service.
Incorrect Answers
A:RADIUS integration delegates user authentication to a configured authentication server, a mechanism intended to authenticate managed remote agents against a reachable RADIUS infrastructure rather than the requested ‘Account for SSO precedence over other methods’ control. The stated task instead is to avoid expecting local or RADIUS credentials to work after enabling SAML SSO, and adjusting ‘Configure RADIUS authentication’ would not deliver ‘Account for SSO precedence over other methods’. For the ‘Configure RADIUS authentication’ alternative to ‘Account for SSO precedence over other methods’, configure the correct shared secret and reachable authentication service endpoints.
C:The FortiSASE onboarding flow can provide prepared FortiClient installers that users install on their devices, a mechanism intended to enroll a small pilot group with minimal manual agent configuration rather than the requested ‘Account for SSO precedence over other methods’ control. The stated task instead is to avoid expecting local or RADIUS credentials to work after enabling SAML SSO, and adjusting ‘Use preconfigured FortiClient installers’ would not deliver ‘Account for SSO precedence over other methods’. For the ‘Use preconfigured FortiClient installers’ alternative to ‘Account for SSO precedence over other methods’, the device must be supported and permitted to run FortiClient.
D:Registered FortiClient maintains connectivity with FortiSASE endpoint management and supplies identity or posture data, a mechanism intended to preserve endpoint identification and posture exchange for protected access rather than the requested ‘Account for SSO precedence over other methods’ control. The stated task instead is to avoid expecting local or RADIUS credentials to work after enabling SAML SSO, and adjusting ‘Maintain FortiClient tenant registration’ would not deliver ‘Account for SSO precedence over other methods’. For the ‘Maintain FortiClient tenant registration’ alternative to ‘Account for SSO precedence over other methods’, ZTNA decisions may depend on fresh registration and endpoint state.
Question 597
During an authorized lab exercise for a policy owner protecting HTTPS web sessions without blocking business use, the acceptance criteria require the team to apply general internet threat protection separately from SaaS-specific data and tenant controls. Which control meets that requirement?
- Use certificate inspection for metadata-only TLS checks
- Distinguish SIA from SSA policy intent
- Use application category overrides
- Configure file filtering
Explanation
Correct Answer
B:SIA focuses on internet-bound security inspection while SSA adds cloud-application controls such as inline CASB or DLP; that scope directly serves the goal to apply general internet threat protection separately from SaaS-specific data and tenant controls in a policy owner protecting HTTPS web sessions without blocking business use. During implementation, an internet security tunnel does not by itself supply every application-specific SaaS control rather than treating the configuration label as proof of working service.
Incorrect Answers
A:Certificate inspection can evaluate visible TLS metadata but does not expose encrypted HTTP payload contents, a mechanism intended to inspect certificate-related connection metadata without decrypting application bodies rather than the requested ‘Distinguish SIA from SSA policy intent’ control. The stated task instead is to apply general internet threat protection separately from SaaS-specific data and tenant controls, and adjusting ‘Use certificate inspection for metadata-only TLS checks’ would not deliver ‘Distinguish SIA from SSA policy intent’. For the ‘Use certificate inspection for metadata-only TLS checks’ alternative to ‘Distinguish SIA from SSA policy intent’, choose deep inspection when the requirement actually depends on encrypted content visibility.
C:Application Control overrides provide a more specific action than a broad application-category setting, a mechanism intended to deny one high-risk application within an otherwise permitted collaboration category rather than the requested ‘Distinguish SIA from SSA policy intent’ control. The stated task instead is to apply general internet threat protection separately from SaaS-specific data and tenant controls, and adjusting ‘Use application category overrides’ would not deliver ‘Distinguish SIA from SSA policy intent’. For the ‘Use application category overrides’ alternative to ‘Distinguish SIA from SSA policy intent’, specific overrides should be tested against recognized application signatures.
D:File Filter identifies supported file types in inspected sessions and enforces the configured file action, a mechanism intended to block transfer of prohibited file types regardless of benign website category rather than the requested ‘Distinguish SIA from SSA policy intent’ control. The stated task instead is to apply general internet threat protection separately from SaaS-specific data and tenant controls, and adjusting ‘Configure file filtering’ would not deliver ‘Distinguish SIA from SSA policy intent’. For the ‘Configure file filtering’ alternative to ‘Distinguish SIA from SSA policy intent’, encrypted transfers need suitable deep inspection for content-aware file filtering.
Question 598
During an authorized lab exercise for a FortiGate support case concerning an unexpected SD-WAN path, the incident notes state that the administrator sees unexpected carrier billing but has not confirmed the selected member. Which change is most relevant to this symptom?
- Investigate: Correlate a failover event with SLA history
- Investigate: Use SD-WAN service4 diagnostics
- Investigate: Inspect selected member in service diagnostics
- Investigate: Investigate first-session application identification
Explanation
Correct Answer
C:The symptom identifies the missing operational behavior: SD-WAN service diagnostics show selected members, eligibility, and rule selection behavior. For a FortiGate support case concerning an unexpected SD-WAN path, a direct diagnostic confirmation would be that the service diagnostic lists the active selected member and alternate eligible candidates; during repair, displayed member preference is not equivalent to proof that a specific session matched.
Incorrect Answers
A: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 selected member in service diagnostics’. 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 administrator sees unexpected carrier billing but has not confirmed the selected member at a FortiGate support case concerning an unexpected SD-WAN path.
B: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 selected member in service diagnostics’. 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 administrator sees unexpected carrier billing but has not confirmed the selected member at a FortiGate support case concerning an unexpected SD-WAN path.
D:Application-detection learning can populate an app-specific destination tuple after the initial inspected connection, which serves the different requirement to trace why a newly seen application uses a generic rule before subsequent sessions match its signature instead of the behavior delivered by ‘Inspect selected member in service diagnostics’. If that component were misconfigured, a more characteristic finding would be that the first connection to a newly contacted SaaS endpoint uses the implicit path while repeats use its dedicated rule; the actual report concerns the administrator sees unexpected carrier billing but has not confirmed the selected member at a FortiGate support case concerning an unexpected SD-WAN path.
Question 599
At a warehouse where a primary fiber WAN and a standby broadband WAN feed the same firewall, an engineer is preparing ‘Configure an SD-WAN zone’ to use a common logical outgoing interface for two alternate WAN circuits. Which TWO statements identify a pertinent deployment safeguard and a direct post-change validation result? Choose TWO.
- Create the correct member-to-zone mapping before using zones in rules.
- Use the zone as the policy interface instead of individual member ports.
- Path steering and firewall permission are separate decisions.
- The outbound policy selects the zone containing both ISP members.
- The active routing table contains a default path via the intended SD-WAN zone.
Explanation
Correct Answers
B:This safeguard applies to ‘Configure an SD-WAN zone’, which works because a zone groups SD-WAN members for firewall policies, static routes, and service rules without merging the physical circuits. Without the correct deployment condition, operators may see that the firewall policy references one WAN port and does not cover the backup member in a warehouse where a primary fiber WAN and a standby broadband WAN feed the same firewall.
D:The observation follows from the operation of ‘Configure an SD-WAN zone’: a zone groups SD-WAN members for firewall policies, static routes, and service rules without merging the physical circuits. It directly tests the requested ability to use a common logical outgoing interface for two alternate WAN circuits in a warehouse where a primary fiber WAN and a standby broadband WAN feed the same firewall, rather than another policy or network layer.
Incorrect Answers
A:The planning point is associated with ‘Separate underlay and overlay SD-WAN zones’, not ‘Configure an SD-WAN zone’; its real role is to keep ISP transports and IPsec private overlays independently selectable in policy. The required deployment instead centers on ‘Configure an SD-WAN zone’, rather than ‘Separate underlay and overlay SD-WAN zones’; the distinct symptom to guard against is that the firewall policy references one WAN port and does not cover the backup member.
C:The planning point is associated with ‘Allow LAN-to-SD-WAN firewall policy’, not ‘Configure an SD-WAN zone’; its real role is to authorize office clients to reach external destinations over eligible SD-WAN members. The required deployment instead centers on ‘Configure an SD-WAN zone’, rather than ‘Allow LAN-to-SD-WAN firewall policy’; the distinct symptom to guard against is that the firewall policy references one WAN port and does not cover the backup member.
E:This result would validate ‘Install an SD-WAN default route’, not ‘Configure an SD-WAN zone’, because a default static route whose outgoing interface is the SD-WAN zone supplies route reachability before path steering. That separate implementation serves provide a route for internet-bound traffic through the SD-WAN aggregate, whereas the audit needs evidence specifically of ‘Configure an SD-WAN zone’ at a warehouse where a primary fiber WAN and a standby broadband WAN feed the same firewall.
Question 600
Within an off-site workforce where some endpoints fail compliance verification, the administrator must label endpoints dynamically when a specified local security condition is met without redesigning unrelated services. Which option addresses the goal?
- Check endpoint vulnerability severity
- Assign compliant endpoint tags to private policies
- Build a security posture tag rule
- Review the posture tag's allow or deny direction
- Use endpoint-profile assignment for managed groups
Explanation
Correct Answer
C:FortiClient evaluates defined endpoint posture conditions and associates matching endpoints with security tags; that scope directly serves the goal to label endpoints dynamically when a specified local security condition is met in an off-site workforce where some endpoints fail compliance verification. During implementation, the tag logic must accurately represent the actual security requirement rather than treating the configuration label as proof of working service.
Incorrect Answers
A:Vulnerability-related posture information can be used to classify a risky endpoint for conditional access, a mechanism intended to apply stricter access to devices with high-severity unresolved vulnerabilities rather than the requested ‘Build a security posture tag rule’ control. The stated task instead is to label endpoints dynamically when a specified local security condition is met, and adjusting ‘Check endpoint vulnerability severity’ would not deliver ‘Build a security posture tag rule’. For the ‘Check endpoint vulnerability severity’ alternative to ‘Build a security posture tag rule’, posture signals require recent endpoint scanning and successful telemetry exchange.
B:Private access policies can use security posture tags as dynamic matching criteria, a mechanism intended to grant sensitive private access only to managed devices meeting specified security conditions rather than the requested ‘Build a security posture tag rule’ control. The stated task instead is to label endpoints dynamically when a specified local security condition is met, and adjusting ‘Assign compliant endpoint tags to private policies’ would not deliver ‘Build a security posture tag rule’. For the ‘Assign compliant endpoint tags to private policies’ alternative to ‘Build a security posture tag rule’, authentication identity and endpoint posture solve different trust checks.
D:An allow-when-tagged versus deny-when-tagged action determines whether the matched posture condition grants connectivity, a mechanism intended to avoid inverting the policy when a tag specifically denotes a noncompliant endpoint rather than the requested ‘Build a security posture tag rule’ control. The stated task instead is to label endpoints dynamically when a specified local security condition is met, and adjusting ‘Review the posture tag's allow or deny direction’ would not deliver ‘Build a security posture tag rule’. For the ‘Review the posture tag's allow or deny direction’ alternative to ‘Build a security posture tag rule’, define whether a tag means compliant or noncompliant before using it for admission.
E:Endpoint profile assignment determines which device-side checks and tunnel behavior a managed group receives, a mechanism intended to apply a stricter posture and connection configuration to a high-risk user population rather than the requested ‘Build a security posture tag rule’ control. The stated task instead is to label endpoints dynamically when a specified local security condition is met, and adjusting ‘Use endpoint-profile assignment for managed groups’ would not deliver ‘Build a security posture tag rule’. For the ‘Use endpoint-profile assignment for managed groups’ alternative to ‘Build a security posture tag rule’, a cloud traffic policy alone does not deploy settings to FortiClient endpoints.