McAfee-Secured Website

Exam Code: NSE5_SSE_AD-7.6

Exam Name: Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator

Certification Provider: Fortinet

Corresponding Certification: NSE5

100% Fortinet NSE5_SSE_AD-7.6 Guaranteed Success With Testking Training Materials

Get Real NSE5_SSE_AD-7.6 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

54 Questions & Answers with Testing Engine

"Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator Exam", also known as NSE5_SSE_AD-7.6 exam, is a Fortinet certification exam.

Pass your tests with the always up-to-date NSE5_SSE_AD-7.6 Exam Engine. Your NSE5_SSE_AD-7.6 training materials keep you at the head of the pack!

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Was: $137.49
Now: $124.99

Fortinet NSE5_SSE_AD-7.6 Practice Test 44

Question 430

During follow-up testing at a national SOC, the original fault was: Users are assigned to a FortiSASE SAML login profile but the identity provider does not trust the current service provider entity ID. Which measured result demonstrates recovery rather than an unrelated improvement?

  1. A managed user completes SSO and FortiSASE identifies the correct account.
  2. A user in the previously omitted OU is found and permitted according to group rules.
  3. The local user receives only the allowed policy rather than unrestricted default access.
  4. Test web access appears in FortiSASE SWG logs and nonproxy direct browsing is appropriately restricted.

Explanation

Correct Answer

A:

A managed user completes SSO and FortiSASE identifies the correct account. This evidence directly tests the intended corrective action: Update the approved SAML trust, entity ID and assertion configuration on both FortiSASE and IdP. It confirms the failure mechanism—SAML login requires matching service-provider and identity-provider trust metadata.—has been addressed in the actual affected flow.

Incorrect Answers

B:

A user in the previously omitted OU is found and permitted according to group rules. This would verify resolution of a different case: A remote user enters a correct password but FortiSASE authentication against a central LDAP directory fails because the configured base DN excludes that organizational unit. It does not show that the reported issue was fixed or that its intended action—Update the approved SAML trust, entity ID and assertion configuration on both FortiSASE and IdP.—worked.

C:

The local user receives only the allowed policy rather than unrestricted default access. This would verify resolution of a different case: An administrator creates a local FortiSASE user but assumes LDAP group restrictions apply automatically although the account is not mapped to a corresponding local service group. It does not show that the reported issue was fixed or that its intended action—Update the approved SAML trust, entity ID and assertion configuration on both FortiSASE and IdP.—worked.

D:

Test web access appears in FortiSASE SWG logs and nonproxy direct browsing is appropriately restricted. This would verify resolution of a different case: A team deploys an agentless SWG configuration but omits browser or system proxy settings, causing traffic to connect directly to Internet sites. It does not show that the reported issue was fixed or that its intended action—Update the approved SAML trust, entity ID and assertion configuration on both FortiSASE and IdP.—worked.

Question 431

The incident investigation at a national SOC records: Users are assigned to a FortiSASE SAML login profile but the identity provider does not trust the current service provider entity ID. Which mechanism provides the strongest explanation?

  1. Successful federation authentication does not guarantee group-based authorization data is present.
  2. SAML login requires matching service-provider and identity-provider trust metadata.
  3. RADIUS authentication fails when client and server trust secrets no longer match.
  4. Encrypted proxy inspection requires a managed trust relationship with endpoints.

Explanation

Correct Answer

B:

SAML login requires matching service-provider and identity-provider trust metadata. This explains why the reported condition occurs: Users are assigned to a FortiSASE SAML login profile but the identity provider does not trust the current service provider entity ID. The targeted correction is: Update the approved SAML trust, entity ID and assertion configuration on both FortiSASE and IdP.

Incorrect Answers

A:

Successful federation authentication does not guarantee group-based authorization data is present. This mechanism instead explains a separate problem: A FortiSASE SAML integration accepts users but places everyone into a default policy because role and group assertions are missing from the issued claim. The current incident requires the more directly applicable cause stated by the correct option.

C:

RADIUS authentication fails when client and server trust secrets no longer match. This mechanism instead explains a separate problem: A FortiSASE tenant uses RADIUS for user authentication but the RADIUS shared secret was changed on FortiAuthenticator only. The current incident requires the more directly applicable cause stated by the correct option.

D:

Encrypted proxy inspection requires a managed trust relationship with endpoints. This mechanism instead explains a separate problem: A site lets users bypass required certificate trust warnings by manually accepting an unexpected FortiSASE proxy certificate on every device. The current incident requires the more directly applicable cause stated by the correct option.

Question 432

After a corrective change at a national SOC, the team documents: Users are assigned to a FortiSASE SAML login profile but the identity provider does not trust the current service provider entity ID. Which repeatable control BEST prevents a recurrence?

  1. Include group claim refresh and revocation checks in offboarding workflows.
  2. Document the appropriate onboarding method per user/device classification.
  3. Review SAML entity IDs and certificates during every identity-platform migration.
  4. Check client connection destination and applied policy after each profile update.

Explanation

Correct Answer

C:

Review SAML entity IDs and certificates during every identity-platform migration. This control reduces recurrence of the documented mechanism: SAML login requires matching service-provider and identity-provider trust metadata. It creates a repeatable check around the needed response: Update the approved SAML trust, entity ID and assertion configuration on both FortiSASE and IdP.

Incorrect Answers

A:

Include group claim refresh and revocation checks in offboarding workflows. That safeguard addresses another potential failure: A remote worker successfully authenticates to FortiSASE but a stale identity group cache keeps applying a former privileged access policy. It is not the most targeted recurring control for the described cause: SAML login requires matching service-provider and identity-provider trust metadata.

B:

Document the appropriate onboarding method per user/device classification. That safeguard addresses another potential failure: A company plans browser-only secure web gateway use for contractors but distributes an agent-based full-tunnel guide requiring managed endpoint enrollment. It is not the most targeted recurring control for the described cause: SAML login requires matching service-provider and identity-provider trust metadata.

D:

Check client connection destination and applied policy after each profile update. That safeguard addresses another potential failure: FortiClient is installed but its VPN connection uses a direct on-premises FortiGate tunnel instead of the intended FortiSASE service. It is not the most targeted recurring control for the described cause: SAML login requires matching service-provider and identity-provider trust metadata.

Question 433

During a quarterly compliance review at a financial services branch, analysts observe: A FortiSASE administrator applies a broad URL block on a critical payroll portal because its vendor changed categories and no business exception review is in place. Which Fortinet configuration or investigation action BEST corrects the identified issue?

  1. Reclassify or narrowly exempt the approved payroll portal under the supported web policy workflow.
  2. Configure the appropriate supported video filtering controls for the intended categories or channels.
  3. Correct supported IP address allocation or network range mappings used by the relevant FortiSASE policy.
  4. Attach a reviewed security profile group containing the required Antivirus and other relevant inspection profiles to the matching cloud access policy.

Explanation

Correct Answer

A:

Reclassify or narrowly exempt the approved payroll portal under the supported web policy workflow. This is the most direct response to the stated incident: A FortiSASE administrator applies a broad URL block on a critical payroll portal because its vendor changed categories and no business exception review is in place. The technical mechanism is: Dynamic website categorization can change the effect of broad web-filter actions. Confirmation requires: Payroll access resumes with required log evidence and prohibited category examples remain blocked.

Incorrect Answers

B:

Configure the appropriate supported video filtering controls for the intended categories or channels. That could address a different issue in the same blueprint area: A video streaming restriction is requested for a classroom network but the only policy is a bandwidth cap that does not distinguish approved educational video categories. It does not directly correct the given incident, whose decisive mechanism is: Dynamic website categorization can change the effect of broad web-filter actions.

C:

Correct supported IP address allocation or network range mappings used by the relevant FortiSASE policy. That could address a different issue in the same blueprint area: An IPAM allocation contains overlapping corporate and guest address ranges, leading the cloud service to apply the wrong network-specific security policy. It does not directly correct the given incident, whose decisive mechanism is: Dynamic website categorization can change the effect of broad web-filter actions.

D:

Attach a reviewed security profile group containing the required Antivirus and other relevant inspection profiles to the matching cloud access policy. That could address a different issue in the same blueprint area: FortiSASE remote web browsing is allowed under a policy with web filtering but no Antivirus profile, leaving risky downloads without intended malware inspection. It does not directly correct the given incident, whose decisive mechanism is: Dynamic website categorization can change the effect of broad web-filter actions.

Question 434

At a financial services branch, a test team is validating a change after this incident: A FortiSASE administrator applies a broad URL block on a critical payroll portal because its vendor changed categories and no business exception review is in place. What evidence most directly verifies the intended outcome?

  1. Video calls connect reliably under the approved security profile and unrelated risky traffic stays protected.
  2. Payroll access resumes with required log evidence and prohibited category examples remain blocked.
  3. A controlled restricted URL test hits the intended policy and produces a web filter block record.
  4. A synthetic test secret sent over eligible TLS is recognized by the intended DLP profile.

Explanation

Correct Answer

B:

Payroll access resumes with required log evidence and prohibited category examples remain blocked. This evidence directly tests the intended corrective action: Reclassify or narrowly exempt the approved payroll portal under the supported web policy workflow. It confirms the failure mechanism—Dynamic website categorization can change the effect of broad web-filter actions.—has been addressed in the actual affected flow.

Incorrect Answers

A:

Video calls connect reliably under the approved security profile and unrelated risky traffic stays protected. This would verify resolution of a different case: A managed endpoint's FortiSASE SIA policy uses web filtering but sends video conferencing traffic through an unnecessarily intensive inspection profile that breaks media startup. It does not show that the reported issue was fixed or that its intended action—Reclassify or narrowly exempt the approved payroll portal under the supported web policy workflow.—worked.

C:

A controlled restricted URL test hits the intended policy and produces a web filter block record. This would verify resolution of a different case: A FortiSASE profile group includes web filtering but is never attached to the matching remote user access policy. It does not show that the reported issue was fixed or that its intended action—Reclassify or narrowly exempt the approved payroll portal under the supported web policy workflow.—worked.

D:

A synthetic test secret sent over eligible TLS is recognized by the intended DLP profile. This would verify resolution of a different case: A security team expects a cloud DLP policy to inspect private encrypted transfers but has configured only certificate inspection, leaving content unreadable. It does not show that the reported issue was fixed or that its intended action—Reclassify or narrowly exempt the approved payroll portal under the supported web policy workflow.—worked.

Question 435

A Fortinet administrator at a financial services branch is assessing: A FortiSASE administrator applies a broad URL block on a critical payroll portal because its vendor changed categories and no business exception review is in place. What is the most relevant root cause?

  1. An incomplete file-type rule misses formats outside its explicit match list.
  2. Certificate inspection does not expose the encrypted application payload for full content controls.
  3. Dynamic website categorization can change the effect of broad web-filter actions.
  4. An inspection rule configured for downloads does not automatically cover outbound file submissions.

Explanation

Correct Answer

C:

Dynamic website categorization can change the effect of broad web-filter actions. This explains why the reported condition occurs: A FortiSASE administrator applies a broad URL block on a critical payroll portal because its vendor changed categories and no business exception review is in place. The targeted correction is: Reclassify or narrowly exempt the approved payroll portal under the supported web policy workflow.

Incorrect Answers

A:

An incomplete file-type rule misses formats outside its explicit match list. This mechanism instead explains a separate problem: Remote staff can upload executable installers to unapproved file-sharing services because the file-type filter recognizes only archive formats. The current incident requires the more directly applicable cause stated by the correct option.

B:

Certificate inspection does not expose the encrypted application payload for full content controls. This mechanism instead explains a separate problem: A user opens an encrypted file-sharing site and an inspector sees only certificate metadata despite a requirement to inspect web content. The current incident requires the more directly applicable cause stated by the correct option.

D:

An inspection rule configured for downloads does not automatically cover outbound file submissions. This mechanism instead explains a separate problem: An anti-malware profile configured for only downloaded files fails to detect controlled suspicious uploads to a cloud collaboration tool. The current incident requires the more directly applicable cause stated by the correct option.

Question 436

A risk review at a financial services branch focuses on preventing this issue again: A FortiSASE administrator applies a broad URL block on a critical payroll portal because its vendor changed categories and no business exception review is in place. Which recurring control is most suitable?

  1. Test approved and unapproved tenants during SaaS security policy acceptance.
  2. Audit profile group completeness for every Internet allow policy.
  3. Review CASB observe-versus-enforce actions during policy rollout.
  4. Monitor business-critical category changes and validate exceptions with risk owners.

Explanation

Correct Answer

D:

Monitor business-critical category changes and validate exceptions with risk owners. This control reduces recurrence of the documented mechanism: Dynamic website categorization can change the effect of broad web-filter actions. It creates a repeatable check around the needed response: Reclassify or narrowly exempt the approved payroll portal under the supported web policy workflow.

Incorrect Answers

A:

Test approved and unapproved tenants during SaaS security policy acceptance. That safeguard addresses another potential failure: A SaaS application is allowed by FortiSASE but staff must block personal tenants; an admin creates only a generic App Control permit. It is not the most targeted recurring control for the described cause: Dynamic website categorization can change the effect of broad web-filter actions.

B:

Audit profile group completeness for every Internet allow policy. That safeguard addresses another potential failure: FortiSASE remote web browsing is allowed under a policy with web filtering but no Antivirus profile, leaving risky downloads without intended malware inspection. It is not the most targeted recurring control for the described cause: Dynamic website categorization can change the effect of broad web-filter actions.

C:

Review CASB observe-versus-enforce actions during policy rollout. That safeguard addresses another potential failure: An inline CASB policy detects unauthorized cloud storage usage but is configured in monitor-only mode despite a requirement to block uploads. It is not the most targeted recurring control for the described cause: Dynamic website categorization can change the effect of broad web-filter actions.

Question 437

During a production service incident, an administrator reports at a regional data center: An analyst sees one outdated antivirus alert after a profile change and assumes the new policy is still failing without checking its log timestamp. What should the team change or investigate FIRST?

  1. Review supported SaaS or CASB event categories with appropriate user, application and action filters.
  2. Filter security logs by current policy version or session period and run a safe fresh validation.
  3. Determine supported log anonymization and correlatable identity controls under privacy policy.
  4. Correlate DNS resolution and web security events using the relevant time and source fields.

Explanation

Correct Answer

B:

Filter security logs by current policy version or session period and run a safe fresh validation. This is the most direct response to the stated incident: An analyst sees one outdated antivirus alert after a profile change and assumes the new policy is still failing without checking its log timestamp. The technical mechanism is: Historical alerts do not demonstrate the present enforcement state. Confirmation requires: A new event accurately reflects the postchange profile action and timestamp.

Incorrect Answers

A:

Review supported SaaS or CASB event categories with appropriate user, application and action filters. That could address a different issue in the same blueprint area: A suspicious SaaS upload is recorded in inline CASB logs, but investigators search only web filter events and miss it. It does not directly correct the given incident, whose decisive mechanism is: Historical alerts do not demonstrate the present enforcement state.

C:

Determine supported log anonymization and correlatable identity controls under privacy policy. That could address a different issue in the same blueprint area: The SOC receives an external log copy with missing source identities due to anonymization settings and assumes all events came from the same user. It does not directly correct the given incident, whose decisive mechanism is: Historical alerts do not demonstrate the present enforcement state.

D:

Correlate DNS resolution and web security events using the relevant time and source fields. That could address a different issue in the same blueprint area: A FortiSASE security incident is attributed to a blocked malicious domain, but cloud DNS and web events show the domain never resolved for the affected client. It does not directly correct the given incident, whose decisive mechanism is: Historical alerts do not demonstrate the present enforcement state.

Question 438

Following remediation at a regional data center, engineers revisit: An analyst sees one outdated antivirus alert after a profile change and assumes the new policy is still failing without checking its log timestamp. Which observation would BEST prove the specific issue is resolved?

  1. The investigation identifies the affected endpoint and whether malicious content was blocked.
  2. The case documents whether traffic was prevented or only detected by the relevant IPS rule.
  3. A new event accurately reflects the postchange profile action and timestamp.
  4. Authorized investigators can distinguish affected sessions or document appropriately limited attribution.

Explanation

Correct Answer

C:

A new event accurately reflects the postchange profile action and timestamp. This evidence directly tests the intended corrective action: Filter security logs by current policy version or session period and run a safe fresh validation. It confirms the failure mechanism—Historical alerts do not demonstrate the present enforcement state.—has been addressed in the actual affected flow.

Incorrect Answers

A:

The investigation identifies the affected endpoint and whether malicious content was blocked. This would verify resolution of a different case: An administrator sees antivirus detections in FortiSASE but lacks the affected user and device context to decide where containment is needed. It does not show that the reported issue was fixed or that its intended action—Filter security logs by current policy version or session period and run a safe fresh validation.—worked.

B:

The case documents whether traffic was prevented or only detected by the relevant IPS rule. This would verify resolution of a different case: A cloud log shows repeated IPS detections for an untrusted destination, but staff ignore the action field and assume every signature event was blocked. It does not show that the reported issue was fixed or that its intended action—Filter security logs by current policy version or session period and run a safe fresh validation.—worked.

D:

Authorized investigators can distinguish affected sessions or document appropriately limited attribution. This would verify resolution of a different case: The SOC receives an external log copy with missing source identities due to anonymization settings and assumes all events came from the same user. It does not show that the reported issue was fixed or that its intended action—Filter security logs by current policy version or session period and run a safe fresh validation.—worked.

Question 439

During a production service incident, this condition is reported: An analyst sees one outdated antivirus alert after a profile change and assumes the new policy is still failing without checking its log timestamp. Which technical explanation MOST directly accounts for the failure?

  1. Isolated malware events do not provide full scope without identity and session correlation.
  2. Different FortiSASE security profiles generate different evidence about threats.
  3. Login anomalies can matter independently of content filtering categories.
  4. Historical alerts do not demonstrate the present enforcement state.

Explanation

Correct Answer

D:

Historical alerts do not demonstrate the present enforcement state. This explains why the reported condition occurs: An analyst sees one outdated antivirus alert after a profile change and assumes the new policy is still failing without checking its log timestamp. The targeted correction is: Filter security logs by current policy version or session period and run a safe fresh validation.

Incorrect Answers

A:

Isolated malware events do not provide full scope without identity and session correlation. This mechanism instead explains a separate problem: An administrator sees antivirus detections in FortiSASE but lacks the affected user and device context to decide where containment is needed. The current incident requires the more directly applicable cause stated by the correct option.

B:

Different FortiSASE security profiles generate different evidence about threats. This mechanism instead explains a separate problem: An SOC receives a FortiSASE Web Filter log for a blocked phishing category but labels it as an antivirus malware detection. The current incident requires the more directly applicable cause stated by the correct option.

C:

Login anomalies can matter independently of content filtering categories. This mechanism instead explains a separate problem: Cloud security events show successful login attempts from an unexpected country, yet the team closes the case because no web filter block occurred. The current incident requires the more directly applicable cause stated by the correct option.

Question 440

During a post-incident review at a regional data center, the original problem was: An analyst sees one outdated antivirus alert after a profile change and assumes the new policy is still failing without checking its log timestamp. Which preventive practice most directly addresses its cause?

  1. Separate prechange and postchange log samples in cloud policy validation.
  2. Require actual DLP enforcement action and session outcome before assigning incident severity.
  3. Require endpoint confirmation before escalating download detections to executed-malware claims.
  4. Retain authenticated user and SaaS session fields for data-exfiltration investigations.

Explanation

Correct Answer

A:

Separate prechange and postchange log samples in cloud policy validation. This control reduces recurrence of the documented mechanism: Historical alerts do not demonstrate the present enforcement state. It creates a repeatable check around the needed response: Filter security logs by current policy version or session period and run a safe fresh validation.

Incorrect Answers

B:

Require actual DLP enforcement action and session outcome before assigning incident severity. That safeguard addresses another potential failure: A DLP violation is reported for a synthetic payment identifier, but the SOC incorrectly concludes the file was exfiltrated without checking the enforcement action. It is not the most targeted recurring control for the described cause: Historical alerts do not demonstrate the present enforcement state.

C:

Require endpoint confirmation before escalating download detections to executed-malware claims. That safeguard addresses another potential failure: A FortiSASE report lists an endpoint as risky after a prohibited download, but response staff cannot determine whether the antivirus engine blocked the file before execution. It is not the most targeted recurring control for the described cause: Historical alerts do not demonstrate the present enforcement state.

D:

Retain authenticated user and SaaS session fields for data-exfiltration investigations. That safeguard addresses another potential failure: A compliance investigation needs to identify which sanctioned SaaS user moved sensitive files, but the SOC looks only at source public IP shared by many remote clients. It is not the most targeted recurring control for the described cause: Historical alerts do not demonstrate the present enforcement state.

Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests