100% Latest & Updated Fortinet NSE7_SSE_AR-26 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 750
Select THREE correct elements of a safe remedy-and-evidence plan for the Controlled admin onboarding rollback case. During a scoped eastern region deployment across a staged branch cohort, Cedarline Retail must commission the planned FortiSASE/SD-WAN control. The operational finding is: A new FortiSASE administrator changes access policies before role testing and unintentionally grants excessive privileges. The change ticket limits modifications to one approved pilot tenant and requires a reversible test.
- Sign in with read-only and policy-admin test identities and attempt allowed and denied changes.
- Use DEM path measurements across endpoint, PoP and SaaS service to locate the affected segment.
- Stage administrative role assignment, verify least privilege, and retain a tested rollback path before broad rollout.
- Correlate endpoint posture status, tunnel logs and PoP reachability during the issue.
- Only the intended administrators can alter access policy, with audited rollback available.
- Privileged access has the specified stronger device controls without overblocking ordinary roles.
Explanation
Correct Answers
A:Correct verification element: Sign in with read-only and policy-admin test identities and attempt allowed and denied changes. This independently measures whether the intended change works. [Case R161-C150; Fortinet task D1; anchors EXAM, SASE_SIA, SASE_PROXY.] [Question R161-Q0750.]
C:Correct remediation element: Stage administrative role assignment, verify least privilege, and retain a tested rollback path before broad rollout. It addresses Untested admin role mappings create privilege escalation risk during onboarding. [Case R161-C150; Fortinet task D1; anchors EXAM, SASE_SIA, SASE_PROXY.] [Question R161-Q0750.]
E:Only the intended administrators can alter access policy, with audited rollback available. This confirms the case-specific path or security boundary.
Incorrect Answers
B:That intervention addresses Digital experience monitoring at the endpoint: An endpoint dashboard shows a connected tunnel but users report persistent latency to a SaaS service. The case-specific requirement is: Stage administrative role assignment, verify least privilege, and retain a tested rollback path before broad rollout. Verify it with: Sign in with read-only and policy-admin test identities and attempt allowed and denied changes.
D:That intervention addresses Endpoint health versus connection health: A compliant endpoint shows healthy posture but users still experience intermittent PoP connectivity. The relevant verification here is: Sign in with read-only and policy-admin test identities and attempt allowed and denied changes.
F:Incorrect for this case: Privileged access has the specified stronger device controls without overblocking ordinary roles. concerns the separate issue of High-risk user posture enforcement (Two user roles share the same SASE policy even though privileged admins require stricter endpoint compliance.). It does not directly establish Only the intended administrators can alter access policy, with audited rollback available. The case-specific evidence is Sign in with read-only and policy-admin test identities and attempt allowed and denied changes. [Case R161-C150; Fortinet task D1; anchors EXAM, SASE_SIA, SASE_PROXY.] [Question R161-Q0750.]
Question 751
Which corrective action MOST DIRECTLY addresses the observed Controlled admin onboarding rollback problem within the approved change scope? Following a production change affecting Pinehaven Distribution in its remote campus corridor, a network team receives repeatable user-impact reports. Its fault evidence is: A new FortiSASE administrator changes access policies before role testing and unintentionally grants excessive privileges. Unrelated services are still operating, so the immediate response must isolate the failing control for the new branch group without disabling unrelated protections.
- Stage administrative role assignment, verify least privilege, and retain a tested rollback path before broad rollout.
- Scope an additional posture requirement to the privileged identity group and deny access when the condition fails.
- Pilot the supported endpoint version with profile compatibility and a staged rollback before fleet-wide rollout.
- Use the documented FortiSASE standalone SPA hub/NGFW integration option with scoped route and policy.
Explanation
Correct Answer
A:Correct: A new FortiSASE administrator changes access policies before role testing and unintentionally grants excessive privileges. The targeted remedy is Stage administrative role assignment, verify least privilege, and retain a tested rollback path before broad rollout. This addresses untested admin role mappings create privilege escalation risk during onboarding. Confirm it by: Sign in with read-only and policy-admin test identities and attempt allowed and denied changes. [Case R161-C151; Fortinet task D1; anchors EXAM, SASE_SIA, SASE_PROXY.] [Question R161-Q0751.]
Incorrect Answers
B:That intervention addresses High-risk user posture enforcement: Two user roles share the same SASE policy even though privileged admins require stricter endpoint compliance. The case-specific requirement is: Stage administrative role assignment, verify least privilege, and retain a tested rollback path before broad rollout. Verify it with: Sign in with read-only and policy-admin test identities and attempt allowed and denied changes.
C:That intervention addresses Endpoint upgrade risk control: A fleet upgrade changes FortiClient behavior, and an organization wants to avoid disruption to remote access. The case-specific requirement is: Stage administrative role assignment, verify least privilege, and retain a tested rollback path before broad rollout. Verify it with: Sign in with read-only and policy-admin test identities and attempt allowed and denied changes.
D:Incorrect for this case: Use the documented FortiSASE standalone SPA hub/NGFW integration option with scoped route and policy. concerns the separate issue of Private app behind NGFW hub (The private application is behind a FortiGate that is not already an SD-WAN hub, but users require FortiSASE SPA.). It does not directly establish Stage administrative role assignment, verify least privilege, and retain a tested rollback path before broad rollout. The case-specific evidence is Sign in with read-only and policy-admin test identities and attempt allowed and denied changes. [Case R161-C151; Fortinet task D1; anchors EXAM, SASE_SIA, SASE_PROXY.] [Question R161-Q0751.]
Question 752
Which independent diagnostic check best validates that the Controlled admin onboarding rollback repair works? Following a production change affecting Pinehaven Distribution in its remote campus corridor, a network team receives repeatable user-impact reports. Its fault evidence is: A new FortiSASE administrator changes access policies before role testing and unintentionally grants excessive privileges. Unrelated services are still operating, so the immediate response must isolate the failing control for the new branch group without disabling unrelated protections.
- Compare tunnel, posture tags and application access before and after the pilot upgrade.
- Verify hub registration, protected private service path and denied unrelated destination.
- Sign in with read-only and policy-admin test identities and attempt allowed and denied changes.
- Trace application prefix reachability PoP-to-hub and test a permitted session end-to-end.
Explanation
Correct Answer
C:Correct: Sign in with read-only and policy-admin test identities and attempt allowed and denied changes. This directly tests the failure mechanism and the required acceptance evidence: Only the intended administrators can alter access policy, with audited rollback available. [Case R161-C151; Fortinet task D1; anchors EXAM, SASE_SIA, SASE_PROXY.] [Question R161-Q0752.]
Incorrect Answers
A:That intervention addresses Endpoint upgrade risk control: A fleet upgrade changes FortiClient behavior, and an organization wants to avoid disruption to remote access. The relevant verification here is: Sign in with read-only and policy-admin test identities and attempt allowed and denied changes.
B:That intervention addresses Private app behind NGFW hub: The private application is behind a FortiGate that is not already an SD-WAN hub, but users require FortiSASE SPA. The relevant verification here is: Sign in with read-only and policy-admin test identities and attempt allowed and denied changes.
D:Incorrect for this case: Trace application prefix reachability PoP-to-hub and test a permitted session end-to-end. concerns the separate issue of SPA application reachability through routing (SASE users connect successfully to a PoP and hub, but their protected application prefix has no matching route.). It does not directly establish Sign in with read-only and policy-admin test identities and attempt allowed and denied changes. The case-specific evidence is Sign in with read-only and policy-admin test identities and attempt allowed and denied changes. [Case R161-C151; Fortinet task D1; anchors EXAM, SASE_SIA, SASE_PROXY.] [Question R161-Q0752.]
Question 753
What observable result would show that the intended Controlled admin onboarding rollback behavior has been restored? Following a production change affecting Pinehaven Distribution in its remote campus corridor, a network team receives repeatable user-impact reports. Its fault evidence is: A new FortiSASE administrator changes access policies before role testing and unintentionally grants excessive privileges. Unrelated services are still operating, so the immediate response must isolate the failing control for the new branch group without disabling unrelated protections.
- Privileged access has the specified stronger device controls without overblocking ordinary roles.
- The protected application becomes reachable using its approved private address.
- The incident is attributed to service path health rather than falsely to app authorization.
- Only the intended administrators can alter access policy, with audited rollback available.
Explanation
Correct Answer
D:Correct: Only the intended administrators can alter access policy, with audited rollback available. That result demonstrates the requested controlled repair and avoids the failure mode: Untested admin role mappings create privilege escalation risk during onboarding. [Case R161-C151; Fortinet task D1; anchors EXAM, SASE_SIA, SASE_PROXY.] [Question R161-Q0753.]
Incorrect Answers
A:Incorrect for this case: Privileged access has the specified stronger device controls without overblocking ordinary roles. concerns the separate issue of High-risk user posture enforcement (Two user roles share the same SASE policy even though privileged admins require stricter endpoint compliance.). It does not directly establish Only the intended administrators can alter access policy, with audited rollback available. The case-specific evidence is Sign in with read-only and policy-admin test identities and attempt allowed and denied changes. [Case R161-C151; Fortinet task D1; anchors EXAM, SASE_SIA, SASE_PROXY.] [Question R161-Q0753.]
B:Incorrect for this case: The protected application becomes reachable using its approved private address. concerns the separate issue of SPA application reachability through routing (SASE users connect successfully to a PoP and hub, but their protected application prefix has no matching route.). It does not directly establish Only the intended administrators can alter access policy, with audited rollback available. The case-specific evidence is Sign in with read-only and policy-admin test identities and attempt allowed and denied changes. [Case R161-C151; Fortinet task D1; anchors EXAM, SASE_SIA, SASE_PROXY.] [Question R161-Q0753.]
C:Incorrect for this case: The incident is attributed to service path health rather than falsely to app authorization. concerns the separate issue of Security PoP service health visibility (Users are routed to a PoP that is reachable but experiencing service degradation and app delay.). It does not directly establish Only the intended administrators can alter access policy, with audited rollback available. The case-specific evidence is Sign in with read-only and policy-admin test identities and attempt allowed and denied changes. [Case R161-C151; Fortinet task D1; anchors EXAM, SASE_SIA, SASE_PROXY.] [Question R161-Q0753.]
Question 754
Which failure mechanism BEST explains the Controlled admin onboarding rollback observation before a repair is attempted? Following a production change affecting Pinehaven Distribution in its remote campus corridor, a network team receives repeatable user-impact reports. Its fault evidence is: A new FortiSASE administrator changes access policies before role testing and unintentionally grants excessive privileges. Unrelated services are still operating, so the immediate response must isolate the failing control for the new branch group without disabling unrelated protections.
- Role-based access is not conditioned on appropriate device posture.
- The policy lacks a live vulnerability-derived posture signal.
- Untested admin role mappings create privilege escalation risk during onboarding.
- An SIA path without the relevant security profile does not enforce category policy.
Explanation
Correct Answer
C:Correct: Untested admin role mappings create privilege escalation risk during onboarding. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Sign in with read-only and policy-admin test identities and attempt allowed and denied changes. [Case R161-C151; Fortinet task D1; anchors EXAM, SASE_SIA, SASE_PROXY.] [Question R161-Q0754.]
Incorrect Answers
A:The High-risk user posture enforcement diagnosis does not explain the observed case: A new FortiSASE administrator changes access policies before role testing and unintentionally grants excessive privileges. The supported diagnosis is: Untested admin role mappings create privilege escalation risk during onboarding.
B:The Posture tag from vulnerability signal diagnosis does not explain the observed case: A new FortiSASE administrator changes access policies before role testing and unintentionally grants excessive privileges. The supported diagnosis is: Untested admin role mappings create privilege escalation risk during onboarding.
D:The Secure internet access web-filter category diagnosis does not explain the observed case: A new FortiSASE administrator changes access policies before role testing and unintentionally grants excessive privileges. The supported diagnosis is: Untested admin role mappings create privilege escalation risk during onboarding.
Question 755
Select TWO correct elements of a safe remedy-and-evidence plan for the Controlled admin onboarding rollback case. Following a production change affecting Pinehaven Distribution in its remote campus corridor, a network team receives repeatable user-impact reports. Its fault evidence is: A new FortiSASE administrator changes access policies before role testing and unintentionally grants excessive privileges. Unrelated services are still operating, so the immediate response must isolate the failing control for the new branch group without disabling unrelated protections.
- Trace application prefix reachability PoP-to-hub and test a permitted session end-to-end.
- Check service availability and PoP health telemetry before altering unrelated application policies.
- Stage administrative role assignment, verify least privilege, and retain a tested rollback path before broad rollout.
- Operators can distinguish local access impairment from cloud application-path latency.
- Sign in with read-only and policy-admin test identities and attempt allowed and denied changes.
Explanation
Correct Answers
C:Correct remediation element: Stage administrative role assignment, verify least privilege, and retain a tested rollback path before broad rollout. It addresses Untested admin role mappings create privilege escalation risk during onboarding. [Case R161-C151; Fortinet task D1; anchors EXAM, SASE_SIA, SASE_PROXY.] [Question R161-Q0755.]
E:Correct verification element: Sign in with read-only and policy-admin test identities and attempt allowed and denied changes. This independently measures whether the intended change works. [Case R161-C151; Fortinet task D1; anchors EXAM, SASE_SIA, SASE_PROXY.] [Question R161-Q0755.]
Incorrect Answers
A:Incorrect for this case: Trace application prefix reachability PoP-to-hub and test a permitted session end-to-end. concerns the separate issue of SPA application reachability through routing (SASE users connect successfully to a PoP and hub, but their protected application prefix has no matching route.). It does not directly establish Sign in with read-only and policy-admin test identities and attempt allowed and denied changes. The case-specific evidence is Sign in with read-only and policy-admin test identities and attempt allowed and denied changes. [Case R161-C151; Fortinet task D1; anchors EXAM, SASE_SIA, SASE_PROXY.] [Question R161-Q0755.]
B:Incorrect for this case: Check service availability and PoP health telemetry before altering unrelated application policies. concerns the separate issue of Security PoP service health visibility (Users are routed to a PoP that is reachable but experiencing service degradation and app delay.). It does not directly establish Stage administrative role assignment, verify least privilege, and retain a tested rollback path before broad rollout. The case-specific evidence is Sign in with read-only and policy-admin test identities and attempt allowed and denied changes. [Case R161-C151; Fortinet task D1; anchors EXAM, SASE_SIA, SASE_PROXY.] [Question R161-Q0755.]
D:That intervention addresses Digital experience monitoring at the endpoint: An endpoint dashboard shows a connected tunnel but users report persistent latency to a SaaS service. The case-specific requirement is: Only the intended administrators can alter access policy, with audited rollback available. Verify it with: Sign in with read-only and policy-admin test identities and attempt allowed and denied changes.
Question 756
Which corrective action MOST DIRECTLY addresses the observed Posture tag from vulnerability signal problem within the approved change scope? During a scoped western region deployment across a staged branch cohort, HelioCare Clinics must commission the planned FortiSASE/SD-WAN control. The operational finding is: A managed Windows endpoint with a critical vulnerability continues receiving unrestricted private-app access. The change ticket limits modifications to the designated privileged users and requires a reversible test.
- Check service availability and PoP health telemetry before altering unrelated application policies.
- Apply supported inline-CASB/web security inspection rules to the specific SaaS upload action with appropriate TLS handling.
- Validate protected-prefix advertisement and SPA hub firewall policy in addition to tunnel status.
- Create a supported posture tagging rule for high or critical vulnerabilities and reference the tag in access policy.
Explanation
Correct Answer
D:Correct: A managed Windows endpoint with a critical vulnerability continues receiving unrestricted private-app access. The targeted remedy is Create a supported posture tagging rule for high or critical vulnerabilities and reference the tag in access policy. This addresses the policy lacks a live vulnerability-derived posture signal. Confirm it by: Trigger the matching test condition and inspect endpoint tag assignment and resulting access decision. [Case R161-C152; Fortinet task D2; anchors EXAM, SASE_POSTURE, SASE_DEM.] [Question R161-Q0756.]
Incorrect Answers
A:That intervention addresses Security PoP service health visibility: Users are routed to a PoP that is reachable but experiencing service degradation and app delay. The case-specific requirement is: Create a supported posture tagging rule for high or critical vulnerabilities and reference the tag in access policy. Verify it with: Trigger the matching test condition and inspect endpoint tag assignment and resulting access decision.
B:That intervention addresses Inline-CASB policy for SaaS upload: Users may view sanctioned SaaS content but confidential file uploads must be blocked. The case-specific requirement is: Create a supported posture tagging rule for high or critical vulnerabilities and reference the tag in access policy. Verify it with: Trigger the matching test condition and inspect endpoint tag assignment and resulting access decision.
C:That intervention addresses SPA application reachability through routing: SASE users connect successfully to a PoP and hub, but their protected application prefix has no matching route. The case-specific requirement is: Create a supported posture tagging rule for high or critical vulnerabilities and reference the tag in access policy. Verify it with: Trigger the matching test condition and inspect endpoint tag assignment and resulting access decision.
Question 757
Which independent diagnostic check best validates that the Posture tag from vulnerability signal repair works? During a scoped western region deployment across a staged branch cohort, HelioCare Clinics must commission the planned FortiSASE/SD-WAN control. The operational finding is: A managed Windows endpoint with a critical vulnerability continues receiving unrestricted private-app access. The change ticket limits modifications to the designated privileged users and requires a reversible test.
- Trigger the matching test condition and inspect endpoint tag assignment and resulting access decision.
- Install on a clean supported device and confirm agent registration, version and tunnel establishment.
- Exercise the actual UDP app and trace its authorized PoP/hub path rather than testing HTTPS only.
- Enroll two devices in different policy groups and compare resolved profile settings and access.
Explanation
Correct Answer
A:Correct: Trigger the matching test condition and inspect endpoint tag assignment and resulting access decision. This directly tests the failure mechanism and the required acceptance evidence: The vulnerable device is identified and receives the intended restrictive policy. [Case R161-C152; Fortinet task D2; anchors EXAM, SASE_POSTURE, SASE_DEM.] [Question R161-Q0757.]
Incorrect Answers
B:That intervention addresses Installer selection for device platform: A deployment team distributes an installer intended for a different operating system and remote users cannot connect. The relevant verification here is: Trigger the matching test condition and inspect endpoint tag assignment and resulting access decision.
C:That intervention addresses SPA protocol compatibility: A team attempts to publish a private UDP application through a TCP-only HTTPS access proxy. The relevant verification here is: Trigger the matching test condition and inspect endpoint tag assignment and resulting access decision.
D:Incorrect for this case: Enroll two devices in different policy groups and compare resolved profile settings and access. concerns the separate issue of Endpoint profile assignment precedence (A field laptop receives a generic endpoint profile instead of the restricted high-risk role profile.). It does not directly establish Trigger the matching test condition and inspect endpoint tag assignment and resulting access decision. The case-specific evidence is Trigger the matching test condition and inspect endpoint tag assignment and resulting access decision. [Case R161-C152; Fortinet task D2; anchors EXAM, SASE_POSTURE, SASE_DEM.] [Question R161-Q0757.]
Question 758
What observable result would show that the intended Posture tag from vulnerability signal behavior has been restored? During a scoped western region deployment across a staged branch cohort, HelioCare Clinics must commission the planned FortiSASE/SD-WAN control. The operational finding is: A managed Windows endpoint with a critical vulnerability continues receiving unrestricted private-app access. The change ticket limits modifications to the designated privileged users and requires a reversible test.
- The approved private UDP traffic passes through the supported secure access route.
- Users reach the authorized private service through the designated SPA hub.
- Operations can distinguish monitor-only warnings from actual blocked activity.
- The vulnerable device is identified and receives the intended restrictive policy.
Explanation
Correct Answer
D:Correct: The vulnerable device is identified and receives the intended restrictive policy. That result demonstrates the requested controlled repair and avoids the failure mode: The policy lacks a live vulnerability-derived posture signal. [Case R161-C152; Fortinet task D2; anchors EXAM, SASE_POSTURE, SASE_DEM.] [Question R161-Q0758.]
Incorrect Answers
A:That intervention addresses SPA protocol compatibility: A team attempts to publish a private UDP application through a TCP-only HTTPS access proxy. The case-specific requirement is: The vulnerable device is identified and receives the intended restrictive policy. Verify it with: Trigger the matching test condition and inspect endpoint tag assignment and resulting access decision.
B:That intervention addresses Private app behind NGFW hub: The private application is behind a FortiGate that is not already an SD-WAN hub, but users require FortiSASE SPA. The case-specific requirement is: The vulnerable device is identified and receives the intended restrictive policy. Verify it with: Trigger the matching test condition and inspect endpoint tag assignment and resulting access decision.
C:That intervention addresses SaaS application control evidence: A sanctioned SaaS app triggers unexpected DLP warnings and the team assumes every warning means access was blocked. The case-specific requirement is: The vulnerable device is identified and receives the intended restrictive policy. Verify it with: Trigger the matching test condition and inspect endpoint tag assignment and resulting access decision.
Question 759
Which failure mechanism BEST explains the Posture tag from vulnerability signal observation before a repair is attempted? During a scoped western region deployment across a staged branch cohort, HelioCare Clinics must commission the planned FortiSASE/SD-WAN control. The operational finding is: A managed Windows endpoint with a critical vulnerability continues receiving unrestricted private-app access. The change ticket limits modifications to the designated privileged users and requires a reversible test.
- Alert presence is not equivalent to an enforced deny decision.
- PoP transport reachability alone does not establish healthy cloud service processing.
- The policy lacks a live vulnerability-derived posture signal.
- Authentication proves identity, not universal private network authorization.
Explanation
Correct Answer
C:Correct: The policy lacks a live vulnerability-derived posture signal. This matches the given observation, unlike defects in unrelated SASE or SD-WAN controls. Verify the diagnosis through: Trigger the matching test condition and inspect endpoint tag assignment and resulting access decision. [Case R161-C152; Fortinet task D2; anchors EXAM, SASE_POSTURE, SASE_DEM.] [Question R161-Q0759.]
Incorrect Answers
A:The SaaS application control evidence diagnosis does not explain the observed case: A managed Windows endpoint with a critical vulnerability continues receiving unrestricted private-app access. The supported diagnosis is: The policy lacks a live vulnerability-derived posture signal.
B:The Security PoP service health visibility diagnosis does not explain the observed case: A managed Windows endpoint with a critical vulnerability continues receiving unrestricted private-app access. The supported diagnosis is: The policy lacks a live vulnerability-derived posture signal.
D:The Secure private app authorization after login diagnosis does not explain the observed case: A managed Windows endpoint with a critical vulnerability continues receiving unrestricted private-app access. The supported diagnosis is: The policy lacks a live vulnerability-derived posture signal.
Question 760
Select THREE correct elements of a safe remedy-and-evidence plan for the Posture tag from vulnerability signal case. During a scoped western region deployment across a staged branch cohort, HelioCare Clinics must commission the planned FortiSASE/SD-WAN control. The operational finding is: A managed Windows endpoint with a critical vulnerability continues receiving unrestricted private-app access. The change ticket limits modifications to the designated privileged users and requires a reversible test.
- Trigger the matching test condition and inspect endpoint tag assignment and resulting access decision.
- Enroll two devices in different policy groups and compare resolved profile settings and access.
- Each application uses an authorized access method that supports its traffic type.
- Use the documented FortiSASE standalone SPA hub/NGFW integration option with scoped route and policy.
- The vulnerable device is identified and receives the intended restrictive policy.
- Create a supported posture tagging rule for high or critical vulnerabilities and reference the tag in access policy.
Explanation
Correct Answers
A:Correct verification element: Trigger the matching test condition and inspect endpoint tag assignment and resulting access decision. This independently measures whether the intended change works. [Case R161-C152; Fortinet task D2; anchors EXAM, SASE_POSTURE, SASE_DEM.] [Question R161-Q0760.]
E:The vulnerable device is identified and receives the intended restrictive policy. This confirms the case-specific path or security boundary.
F:Correct remediation element: Create a supported posture tagging rule for high or critical vulnerabilities and reference the tag in access policy. It addresses The policy lacks a live vulnerability-derived posture signal. [Case R161-C152; Fortinet task D2; anchors EXAM, SASE_POSTURE, SASE_DEM.] [Question R161-Q0760.]
Incorrect Answers
B:Incorrect for this case: Enroll two devices in different policy groups and compare resolved profile settings and access. concerns the separate issue of Endpoint profile assignment precedence (A field laptop receives a generic endpoint profile instead of the restricted high-risk role profile.). It does not directly establish Trigger the matching test condition and inspect endpoint tag assignment and resulting access decision. The case-specific evidence is Trigger the matching test condition and inspect endpoint tag assignment and resulting access decision. [Case R161-C152; Fortinet task D2; anchors EXAM, SASE_POSTURE, SASE_DEM.] [Question R161-Q0760.]
C:That intervention addresses Agent tunnel versus proxy troubleshooting: Web traffic works through a configured proxy but nonbrowser applications cannot reach their private destinations. The case-specific requirement is: The vulnerable device is identified and receives the intended restrictive policy. Verify it with: Trigger the matching test condition and inspect endpoint tag assignment and resulting access decision.
D:Incorrect for this case: Use the documented FortiSASE standalone SPA hub/NGFW integration option with scoped route and policy. concerns the separate issue of Private app behind NGFW hub (The private application is behind a FortiGate that is not already an SD-WAN hub, but users require FortiSASE SPA.). It does not directly establish Create a supported posture tagging rule for high or critical vulnerabilities and reference the tag in access policy. The case-specific evidence is Trigger the matching test condition and inspect endpoint tag assignment and resulting access decision. [Case R161-C152; Fortinet task D2; anchors EXAM, SASE_POSTURE, SASE_DEM.] [Question R161-Q0760.]
Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests