Fortinet NSE5_SSE_AD-7.6 Practice Test 35
Question 340
An incident review for Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator concerns the following specific environment: A newly configured SSO integration sends successful identity-provider assertions, yet FortiSASE rejects them because service-provider metadata and SAML identifiers do not agree. Which TWO actions form a technically sound fix-and-check plan for this exact incident?
- Test the diagnosis with: Inspect SAML response validation errors, configured entity identifiers and current signing certificate metadata.
- Correct the fault by: Align FortiSASE SAML service-provider and identity-provider configuration, metadata and active trust certificates.
- Use the shortcut: Disable signature validation to make mismatched SAML assertions pass.
- Instead collect: Compare proposed service region, documented provider data-handling terms and organization-specific residency requirements.
- Instead configure: Assign the least-privileged supported administrative role and scope needed for the approved monitoring tasks.
Explanation
Correct Answer
A:SAML federation requires mutually matching identity identifiers, endpoints, and trusted signatures; a functioning IdP alone is insufficient. This is one of the two complementary steps: apply the directed corrective action and gather the discriminating evidence.
B:SAML federation requires mutually matching identity identifiers, endpoints, and trusted signatures; a functioning IdP alone is insufficient. The expected result is: A test user completes SSO and reaches the intended FortiSASE group and access policy.
Incorrect Answers
C:The direct remedial step is: Align FortiSASE SAML service-provider and identity-provider configuration, metadata and active trust certificates.
D:This concerns a different operational control (Data residency review) and can be sensible in its own incident, but the reported saml identity-provider mapping problem requires a more direct response. Check the relevant evidence instead: Inspect SAML response validation errors, configured entity identifiers and current signing certificate metadata.
E:This concerns a different operational control (Administrative role boundaries) and can be sensible in its own incident, but the reported saml identity-provider mapping problem requires a more direct response. Instead configure: Assign the least-privileged supported administrative role and scope needed for the approved monitoring tasks.
Question 341
A regional branch uses RADIUS for remote-user validation, but the SASE service gets timeouts after an upstream firewall change. An initial suggestion was to add more SASE web-filter exceptions to compensate for failed RADIUS authentication. Which implementation or configuration decision most directly corrects the stated problem? Select ONE best answer.
- Assign the least-privileged supported administrative role and scope needed for the approved monitoring tasks.
- Verify the FortiSASE service entitlement and provision or associate it with the correct tenant/account before onboarding users.
- Restore supported RADIUS reachability and shared-secret consistency between FortiSASE integration and the identity service.
- Add more SASE web-filter exceptions to compensate for failed RADIUS authentication.
Explanation
Correct Answer
C:RADIUS authentication needs an accessible server and matching trust parameters; active user accounts do not bypass transport or secret failures.
Incorrect Answers
A:Administrative separation reduces unintended configuration changes while still permitting operational visibility. That addresses an alternative control; the reported Fortinet requirement instead calls for: Restore supported RADIUS reachability and shared-secret consistency between FortiSASE integration and the identity service.
B:Possessing a subscription record alone does not activate service for an unrelated or unprovisioned tenant. That addresses an alternative control; the reported Fortinet requirement instead calls for: Restore supported RADIUS reachability and shared-secret consistency between FortiSASE integration and the identity service.
D:That option would add more SASE web-filter exceptions to compensate for failed RADIUS authentication, but it addresses a different concern. RADIUS authentication needs an accessible server and matching trust parameters; active user accounts do not bypass transport or secret failures. The deciding evidence is: Correlate RADIUS request/response records, reachability checks and shared-secret configuration on both endpoints.
Question 342
Consider this FortiSASE/SD-WAN 7.6 operational report: A regional branch uses RADIUS for remote-user validation, but the SASE service gets timeouts after an upstream firewall change. The engineering proposal is: Restore supported RADIUS reachability and shared-secret consistency between FortiSASE integration and the identity service. Which technical principle best explains the expected behavior and why the direct correction is necessary? Select ONE best answer.
- SASE delivery has two separate prerequisites: network service reachability and authorization through the intended security rule.
- RADIUS authentication needs an accessible server and matching trust parameters; active user accounts do not bypass transport or secret failures.
- Healthy internet underlay does not imply an overlay or service tunnel is established and selectable for secure branch traffic.
- Service location and data processing/residency constraints require explicit design review; routing endpoints to a nearby location is not a legal assurance.
Explanation
Correct Answer
B:Evidence that tests the explanation: Correlate RADIUS request/response records, reachability checks and shared-secret configuration on both endpoints.
Incorrect Answers
A:Applied to the observed case: A branch tunnel reaches FortiSASE, but users still see a default deny because no matching authenticated identity is associated with their protected flow. That addresses an alternative control; the reported Fortinet requirement instead calls for: RADIUS authentication needs an accessible server and matching trust parameters; active user accounts do not bypass transport or secret failures.
C:Applied to the observed case: A regional headquarters loses protected outbound paths after the secure SD-WAN-to-SASE tunnel fails, but its ordinary ISP link health looks normal. That addresses an alternative control; the reported Fortinet requirement instead calls for: RADIUS authentication needs an accessible server and matching trust parameters; active user accounts do not bypass transport or secret failures.
D:Applied to the observed case: A healthcare organization is configuring its SASE service and cannot demonstrate that selected cloud processing locations meet its contracted data-residency requirements. That addresses an alternative control; the reported Fortinet requirement instead calls for: RADIUS authentication needs an accessible server and matching trust parameters; active user accounts do not bypass transport or secret failures.
Question 343
The on-call engineer is evaluating the following behavior before changing production configuration: A regional branch uses RADIUS for remote-user validation, but the SASE service gets timeouts after an upstream firewall change. What evidence should the engineer gather FIRST to distinguish the suspected fault from unrelated issues? Select ONE best answer.
- Correlate a controlled branch flow's SD-WAN/tunnel details with FortiSASE user, group and matched-policy logs.
- Check tunnel establishment and reachability, route references and the presence or absence of corresponding SASE sessions.
- Check tenant identity, provisioned service state and linked FortiSASE entitlement in the authorized administrative view.
- Correlate RADIUS request/response records, reachability checks and shared-secret configuration on both endpoints.
Explanation
Correct Answer
D:RADIUS authentication needs an accessible server and matching trust parameters; active user accounts do not bypass transport or secret failures. This observation directly distinguishes the reported radius authentication reachability problem from unrelated network or SASE symptoms.
Incorrect Answers
A:Applied to the observed case: A branch tunnel reaches FortiSASE, but users still see a default deny because no matching authenticated identity is associated with their protected flow. That addresses an alternative control; the reported Fortinet requirement instead calls for: Correlate RADIUS request/response records, reachability checks and shared-secret configuration on both endpoints.
B:Healthy internet underlay does not imply an overlay or service tunnel is established and selectable for secure branch traffic. That addresses an alternative control; the reported Fortinet requirement instead calls for: Correlate RADIUS request/response records, reachability checks and shared-secret configuration on both endpoints.
C:Possessing a subscription record alone does not activate service for an unrelated or unprovisioned tenant. That addresses an alternative control; the reported Fortinet requirement instead calls for: Correlate RADIUS request/response records, reachability checks and shared-secret configuration on both endpoints.
Question 344
After the authorized response to this incident, the operator must validate the effect: A regional branch uses RADIUS for remote-user validation, but the SASE service gets timeouts after an upstream firewall change. Which result would most directly demonstrate that the change achieved its intended outcome? Select ONE best answer.
- Branch users are recognized under the intended policy and their permitted sessions traverse the secure path.
- A controlled protected branch flow crosses the established integration path and is visible in FortiSASE logs.
- The intended tenant is provisioned and authorized administrators can access its configured security service.
- Approved test credentials receive valid RADIUS responses and users enter their assigned policy.
Explanation
Correct Answer
D:The required mechanism is: RADIUS authentication needs an accessible server and matching trust parameters; active user accounts do not bypass transport or secret failures.
Incorrect Answers
A:This concerns a different operational control (Routing and authentication integration) and can be sensible in its own incident, but the reported radius authentication reachability problem requires a more direct response.
B:This concerns a different operational control (SASE integration tunnel availability) and can be sensible in its own incident, but the reported radius authentication reachability problem requires a more direct response.
C:This concerns a different operational control (Tenant entitlement activation) and can be sensible in its own incident, but the reported radius authentication reachability problem requires a more direct response.
Question 345
An operations ticket describes this condition: A regional branch uses RADIUS for remote-user validation, but the SASE service gets timeouts after an upstream firewall change. The team needs to address the underlying fault and gather conclusive evidence. Which proposed correction-and-evidence pair offers the most defensible way to close this case? Select ONE best answer.
- Correct: Separate managed-agent and agentless access policy requirements according to available identity and device signals. Verify: Compare the policy's required endpoint attributes against actual endpoint enrollment and SWG session telemetry for each population.
- Correct: Repair the supported branch-to-SASE connectivity/tunnel and its route eligibility before judging the SASE inspection policy. Verify: Check tunnel establishment and reachability, route references and the presence or absence of corresponding SASE sessions.
- Correct: Verify both the connectivity path and the matching identity/security policy for branch traffic, correcting the missing association. Verify: Correlate a controlled branch flow's SD-WAN/tunnel details with FortiSASE user, group and matched-policy logs.
- Correct: Restore supported RADIUS reachability and shared-secret consistency between FortiSASE integration and the identity service. Verify: Correlate RADIUS request/response records, reachability checks and shared-secret configuration on both endpoints.
Explanation
Correct Answer
D:RADIUS authentication needs an accessible server and matching trust parameters; active user accounts do not bypass transport or secret failures. Correlate RADIUS request/response records, reachability checks and shared-secret configuration on both endpoints.
Incorrect Answers
A:Correct: Separate managed-agent and agentless access policy requirements according to available identity and device signals.
B:Healthy internet underlay does not imply an overlay or service tunnel is established and selectable for secure branch traffic. That addresses an alternative control; the reported Fortinet requirement instead calls for: Correct: Restore supported RADIUS reachability and shared-secret consistency between FortiSASE integration and the identity service. Verify: Correlate RADIUS request/response records, reachability checks and shared-secret configuration on both endpoints.
C:SASE delivery has two separate prerequisites: network service reachability and authorization through the intended security rule. That addresses an alternative control; the reported Fortinet requirement instead calls for: Correct: Restore supported RADIUS reachability and shared-secret consistency between FortiSASE integration and the identity service. Verify: Correlate RADIUS request/response records, reachability checks and shared-secret configuration on both endpoints.
Question 346
A security team changed the RADIUS server secret, causing otherwise valid FortiSASE user authentication requests to fail. An initial suggestion was to add more SASE web-filter exceptions to compensate for failed RADIUS authentication. What is the most appropriate targeted intervention before expanding the incident scope? Select ONE best answer.
- Add more SASE web-filter exceptions to compensate for failed RADIUS authentication.
- Review FortiSASE-supported deployment geography and data-handling options with compliance owners before selecting the service configuration.
- Restore supported RADIUS reachability and shared-secret consistency between FortiSASE integration and the identity service.
- Verify the FortiSASE service entitlement and provision or associate it with the correct tenant/account before onboarding users.
Explanation
Correct Answer
C:RADIUS authentication needs an accessible server and matching trust parameters; active user accounts do not bypass transport or secret failures. Confirm the issue by: Correlate RADIUS request/response records, reachability checks and shared-secret configuration on both endpoints.
Incorrect Answers
A:That option would add more SASE web-filter exceptions to compensate for failed RADIUS authentication, but it addresses a different concern. RADIUS authentication needs an accessible server and matching trust parameters; active user accounts do not bypass transport or secret failures. The direct remedial step is: Restore supported RADIUS reachability and shared-secret consistency between FortiSASE integration and the identity service.
B:Service location and data processing/residency constraints require explicit design review; routing endpoints to a nearby location is not a legal assurance. That addresses an alternative control; the reported Fortinet requirement instead calls for: Restore supported RADIUS reachability and shared-secret consistency between FortiSASE integration and the identity service.
D:This concerns a different operational control (Tenant entitlement activation) and can be sensible in its own incident, but the reported radius authentication reachability problem requires a more direct response.
Question 347
Consider this FortiSASE/SD-WAN 7.6 operational report: A security team changed the RADIUS server secret, causing otherwise valid FortiSASE user authentication requests to fail. The engineering proposal is: Restore supported RADIUS reachability and shared-secret consistency between FortiSASE integration and the identity service. Which mechanism most directly accounts for the reported failure? Select ONE best answer.
- A functioning SASE tenant alone does not make branch traffic traverse it; routing and SD-WAN policy must select the integration path.
- Service location and data processing/residency constraints require explicit design review; routing endpoints to a nearby location is not a legal assurance.
- RADIUS authentication needs an accessible server and matching trust parameters; active user accounts do not bypass transport or secret failures.
- Healthy internet underlay does not imply an overlay or service tunnel is established and selectable for secure branch traffic.
Explanation
Correct Answer
C:Evidence that tests the explanation: Correlate RADIUS request/response records, reachability checks and shared-secret configuration on both endpoints. A satisfactory result would be: Approved test credentials receive valid RADIUS responses and users enter their assigned policy.
Incorrect Answers
A:Applied to the observed case: A branch's internet breakout is meant to traverse FortiSASE security, but generic direct-internet SD-WAN steering bypasses the configured SASE-bound path. That addresses an alternative control; the reported Fortinet requirement instead calls for: RADIUS authentication needs an accessible server and matching trust parameters; active user accounts do not bypass transport or secret failures.
B:Applied to the observed case: A healthcare organization is configuring its SASE service and cannot demonstrate that selected cloud processing locations meet its contracted data-residency requirements. That addresses an alternative control; the reported Fortinet requirement instead calls for: RADIUS authentication needs an accessible server and matching trust parameters; active user accounts do not bypass transport or secret failures.
D:Applied to the observed case: A regional headquarters loses protected outbound paths after the secure SD-WAN-to-SASE tunnel fails, but its ordinary ISP link health looks normal. That addresses an alternative control; the reported Fortinet requirement instead calls for: RADIUS authentication needs an accessible server and matching trust parameters; active user accounts do not bypass transport or secret failures.
Question 348
The on-call engineer is evaluating the following behavior before changing production configuration: A security team changed the RADIUS server secret, causing otherwise valid FortiSASE user authentication requests to fail. Which targeted prechange observation would test the working diagnosis most decisively? Select ONE best answer.
- Compare the account's effective role permissions with its approved support duties and recent admin audit activity.
- Check tenant identity, provisioned service state and linked FortiSASE entitlement in the authorized administrative view.
- Compare proposed service region, documented provider data-handling terms and organization-specific residency requirements.
- Correlate RADIUS request/response records, reachability checks and shared-secret configuration on both endpoints.
Explanation
Correct Answer
D:RADIUS authentication needs an accessible server and matching trust parameters; active user accounts do not bypass transport or secret failures.
Incorrect Answers
A:Applied to the observed case: A contractor needs to review SASE user reports but is given broad tenant-configuration privileges that exceed the job requirement. That addresses an alternative control; the reported Fortinet requirement instead calls for: Correlate RADIUS request/response records, reachability checks and shared-secret configuration on both endpoints.
B:Possessing a subscription record alone does not activate service for an unrelated or unprovisioned tenant. That addresses an alternative control; the reported Fortinet requirement instead calls for: Correlate RADIUS request/response records, reachability checks and shared-secret configuration on both endpoints.
C:This concerns a different operational control (Data residency review) and can be sensible in its own incident, but the reported radius authentication reachability problem requires a more direct response.
Question 349
After the authorized response to this incident, the operator must validate the effect: A security team changed the RADIUS server secret, causing otherwise valid FortiSASE user authentication requests to fail. What should be recorded as the strongest postchange acceptance evidence? Select ONE best answer.
- A controlled protected branch flow crosses the established integration path and is visible in FortiSASE logs.
- The intended tenant is provisioned and authorized administrators can access its configured security service.
- Approved test credentials receive valid RADIUS responses and users enter their assigned policy.
- Traffic designated for SASE appears at the secure service and receives the assigned inspection policy.
Explanation
Correct Answer
C:The required mechanism is: RADIUS authentication needs an accessible server and matching trust parameters; active user accounts do not bypass transport or secret failures. This is an outcome-level acceptance check rather than a proxy such as link light or portal sign-in.
Incorrect Answers
A:This concerns a different operational control (SASE integration tunnel availability) and can be sensible in its own incident, but the reported radius authentication reachability problem requires a more direct response.
B:The required mechanism is: Possessing a subscription record alone does not activate service for an unrelated or unprovisioned tenant. That addresses an alternative control; the reported Fortinet requirement instead calls for: Approved test credentials receive valid RADIUS responses and users enter their assigned policy.
D:The required mechanism is: A functioning SASE tenant alone does not make branch traffic traverse it; routing and SD-WAN policy must select the integration path. That addresses an alternative control; the reported Fortinet requirement instead calls for: Approved test credentials receive valid RADIUS responses and users enter their assigned policy.
Question 350
An incident review for Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator concerns the following specific environment: A security team changed the RADIUS server secret, causing otherwise valid FortiSASE user authentication requests to fail. Which TWO actions form a technically sound fix-and-check plan for this exact incident?
- Instead collect: Compare the policy's required endpoint attributes against actual endpoint enrollment and SWG session telemetry for each population.
- Test the diagnosis with: Correlate RADIUS request/response records, reachability checks and shared-secret configuration on both endpoints.
- Instead configure: Review FortiSASE-supported deployment geography and data-handling options with compliance owners before selecting the service configuration.
- Use the shortcut: Add more SASE web-filter exceptions to compensate for failed RADIUS authentication.
- Correct the fault by: Restore supported RADIUS reachability and shared-secret consistency between FortiSASE integration and the identity service.
Explanation
Correct Answer
B:RADIUS authentication needs an accessible server and matching trust parameters; active user accounts do not bypass transport or secret failures. This is one of the two complementary steps: apply the directed corrective action and gather the discriminating evidence.
E:RADIUS authentication needs an accessible server and matching trust parameters; active user accounts do not bypass transport or secret failures. The expected result is: Approved test credentials receive valid RADIUS responses and users enter their assigned policy.
Incorrect Answers
A:This concerns a different operational control (Split population onboarding) and can be sensible in its own incident, but the reported radius authentication reachability problem requires a more direct response. Check the relevant evidence instead: Correlate RADIUS request/response records, reachability checks and shared-secret configuration on both endpoints.
C:This concerns a different operational control (Data residency review) and can be sensible in its own incident, but the reported radius authentication reachability problem requires a more direct response. Instead configure: Review FortiSASE-supported deployment geography and data-handling options with compliance owners before selecting the service configuration.
D:The direct remedial step is: Restore supported RADIUS reachability and shared-secret consistency between FortiSASE integration and the identity service.