Fortinet FCP_FCT_AD-7.4 Practice Test 60 - Prepaway
Practice Exams:

Pass Fortinet FCP_FCT_AD-7.4 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium File
$69.99 $76.99

FCP_FCT_AD-7.4 Premium ETE File


  • Premium File 33 Questions & Answers. Last Update: Nov 12, 2026
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Fortinet FCP_FCT_AD-7.4 Practice Test 60

Question 590

At fictional Lakeshore Community, the zero trust and Security Fabric team is working during a recorded operations incident review. The FortiClient EMS 7.4 operational issue is: A client receives the HR application's ZTNA destination from EMS but the published proxy hostname does not route to the intended protected web service. The observed evidence is: DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service. Which combined action AND independent proof BEST fit the incident?

  1. The Lakeshore Community team should pair: Action: Align the approved public proxy FQDN, matching certificate, access-proxy virtual service and backend mapping for the resource. Independent confirmation: A tagged authorized user reaches the right HR web service and unauthorized destinations remain unreachable through that proxy.
  2. The Lakeshore Community team should pair: Action: Enforce the intended managed-device and user authorization conditions on the ZTNA access proxy while maintaining a safe denial response. Independent confirmation: The unmanaged test device is rejected and a correctly enrolled compliant device with an authorized user reaches the intended application.
  3. The Lakeshore Community team should pair: Action: Restore supported secure time synchronization and test the current EMS token refresh and trust workflow. Independent confirmation: A corrected client refreshes its accepted token and accesses the permitted application without widening token lifetime unnecessarily.
  4. The Lakeshore Community team should pair: Action: Update the vendor-supported OS condition in the EMS posture tagging rule and validate the resulting gateway dynamic group. Independent confirmation: A current approved OS receives the compliant tag and the unsupported version is denied without blocking unrelated endpoints.

Explanation

Correct Answer

A:

The recorded cause is DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service. The appropriate change is: Align the approved public proxy FQDN, matching certificate, access-proxy virtual service and backend mapping for the resource. Its separate proof is: A tagged authorized user reaches the right HR web service and unauthorized destinations remain unreachable through that proxy.

Incorrect Answers

B:

Another action-and-proof combination is: Enforce the intended managed-device and user authorization conditions on the ZTNA access proxy while maintaining a safe denial response. Independent confirmation: The unmanaged test device is rejected and a correctly enrolled compliant device with an authorized user reaches the intended application. It does not prove recovery from the documented condition: DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service. For Lakeshore Community, the relevant observation is DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service.

C:

An alternative action-and-proof pair is: Restore supported secure time synchronization and test the current EMS token refresh and trust workflow. Independent confirmation: A corrected client refreshes its accepted token and accesses the permitted application without widening token lifetime unnecessarily. It does not resolve the specific finding that DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service. The needed confirmation is a tagged authorized user reaches the right HR web service and unauthorized destinations remain unreachable through that proxy. For Lakeshore Community, the relevant observation is DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service.

D:

Another proposal begins with: Update the vendor-supported OS condition in the EMS posture tagging rule and validate the resulting gateway dynamic group. Independent confirmation: A current approved OS receives the compliant tag and the unsupported version is denied without blocking unrelated endpoints. For this case, apply the specific action: Align the approved public proxy FQDN, matching certificate, access-proxy virtual service and backend mapping for the resource. Verify its effect with: A tagged authorized user reaches the right HR web service and unauthorized destinations remain unreachable through that proxy.

Question 591

At fictional Brookfield Public Services, the zero trust and Security Fabric team is working while validating an approved endpoint security change. The FortiClient EMS 7.4 operational issue is: A contractor without EMS enrollment can reach the internet-facing FortiGate ZTNA listener and assumes it grants private application access by default. Diagnostic evidence: FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session. Which narrowly scoped response BEST addresses this specific problem?

  1. The Brookfield Public Services team should: Investigate and remediate the endpoint's genuine posture condition rather than weakening the ZTNA rule for every authenticated employee.
  2. The Brookfield Public Services team should: Provide a supported remote-reachable ZTNA gateway name and certificate for off-network clients without exposing internal backend servers.
  3. The Brookfield Public Services team should: Verify supported EMS certificate provisioning, endpoint connection state and trusted ZTNA configuration before retrying resource access.
  4. The Brookfield Public Services team should: Enforce the intended managed-device and user authorization conditions on the ZTNA access proxy while maintaining a safe denial response.

Explanation

Correct Answer

D:

FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session. Address the root issue through this bounded action: Enforce the intended managed-device and user authorization conditions on the ZTNA access proxy while maintaining a safe denial response. Public reachability of a ZTNA listener is not permission to access the protected backend.

Incorrect Answers

A:

That option would instead pursue: Investigate and remediate the endpoint's genuine posture condition rather than weakening the ZTNA rule for every authenticated employee. It addresses a different dependency; the deciding observation here is FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session.

B:

Another proposed step is: Provide a supported remote-reachable ZTNA gateway name and certificate for off-network clients without exposing internal backend servers. That step does not resolve the stated condition: FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session. The required intervention is: Enforce the intended managed-device and user authorization conditions on the ZTNA access proxy while maintaining a safe denial response.

C:

Another option proposes: Verify supported EMS certificate provisioning, endpoint connection state and trusted ZTNA configuration before retrying resource access. It does not address the case evidence. FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session. The targeted remedy is: Enforce the intended managed-device and user authorization conditions on the ZTNA access proxy while maintaining a safe denial response.

Question 592

At fictional Brookfield Public Services, the zero trust and Security Fabric team is working while validating an approved endpoint security change. The FortiClient EMS 7.4 operational issue is: A contractor without EMS enrollment can reach the internet-facing FortiGate ZTNA listener and assumes it grants private application access by default. Which diagnostic observation MOST specifically supports this problem rather than another FortiClient EMS fault?

  1. The decisive observation for Brookfield Public Services is: Authentication logs show a valid user session while the FortiGate EMS posture match fails for the same device.
  2. The decisive observation for Brookfield Public Services is: External DNS for the resource returns an internal-only address while EMS endpoint profile lists the destination correctly.
  3. The decisive observation for Brookfield Public Services is: FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session.
  4. The decisive observation for Brookfield Public Services is: Client diagnostics show enrollment completed but no valid EMS-issued or supported ZTNA client certificate for the proxy handshake.

Explanation

Correct Answer

C:

The diagnostic record shows FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session. The cause is consistent with Public reachability of a ZTNA listener is not permission to access the protected backend.

Incorrect Answers

A:

A different observation is: Authentication logs show a valid user session while the FortiGate EMS posture match fails for the same device. That describes a different condition; the one documented here is: FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session.

B:

Even if External DNS for the resource returns an internal-only address while EMS endpoint profile lists the destination correctly, it would not establish this cause. The relevant trace is FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session.

D:

That observation concerns: Client diagnostics show enrollment completed but no valid EMS-issued or supported ZTNA client certificate for the proxy handshake. It is not the decisive fact in this case. The controlling evidence is: FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session.

Question 593

At fictional Brookfield Public Services, the zero trust and Security Fabric team is working while validating an approved endpoint security change. The FortiClient EMS 7.4 operational issue is: A contractor without EMS enrollment can reach the internet-facing FortiGate ZTNA listener and assumes it grants private application access by default. The team has approved this response: Enforce the intended managed-device and user authorization conditions on the ZTNA access proxy while maintaining a safe denial response. Which independent result BEST verifies the intended fix?

  1. The independent success test at Brookfield Public Services is: An eligible compliant device for the same user is allowed, while the original noncompliant state remains rejected until fixed.
  2. The independent success test at Brookfield Public Services is: An approved remote test reaches the protected app through the authenticated proxy while internal clients retain approved routes.
  3. The independent success test at Brookfield Public Services is: The eligible managed test device presents a valid trusted client identity and reaches only its permitted ZTNA application.
  4. The independent success test at Brookfield Public Services is: The unmanaged test device is rejected and a correctly enrolled compliant device with an authorized user reaches the intended application.

Explanation

Correct Answer

D:

Check the result using the following observation: The unmanaged test device is rejected and a correctly enrolled compliant device with an authorized user reaches the intended application. A completed configuration alone would not prove the issue behind FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session is resolved.

Incorrect Answers

A:

Another test would be: An eligible compliant device for the same user is allowed, while the original noncompliant state remains rejected until fixed. The intended correction should instead be judged by the unmanaged test device is rejected and a correctly enrolled compliant device with an authorized user reaches the intended application.

B:

That result would verify another outcome: An approved remote test reaches the protected app through the authenticated proxy while internal clients retain approved routes. It does not test the particular evidence FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session. The needed result is: The unmanaged test device is rejected and a correctly enrolled compliant device with an authorized user reaches the intended application.

C:

A different check would show: The eligible managed test device presents a valid trusted client identity and reaches only its permitted ZTNA application. It would not verify the required outcome, which is the unmanaged test device is rejected and a correctly enrolled compliant device with an authorized user reaches the intended application.

Question 594

At fictional Brookfield Public Services, the zero trust and Security Fabric team is working while validating an approved endpoint security change. The FortiClient EMS 7.4 operational issue is: A contractor without EMS enrollment can reach the internet-facing FortiGate ZTNA listener and assumes it grants private application access by default. The discriminating evidence is: FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session. Which endpoint management or security principle BEST explains the proper response?

  1. The relevant Fortinet design principle for Brookfield Public Services is: Zero-trust authorization can combine user identity and device security state as independent policy conditions.
  2. The relevant Fortinet design principle for Brookfield Public Services is: Distributing a ZTNA destination does not guarantee the correct routed path or DNS view from every client location.
  3. The relevant Fortinet design principle for Brookfield Public Services is: ZTNA policies typically require device trust evidence in addition to destination visibility.
  4. The relevant Fortinet design principle for Brookfield Public Services is: Public reachability of a ZTNA listener is not permission to access the protected backend.

Explanation

Correct Answer

D:

The evidence that FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session is best explained by this principle: Public reachability of a ZTNA listener is not permission to access the protected backend.

Incorrect Answers

A:

A different relationship is: Zero-trust authorization can combine user identity and device security state as independent policy conditions. The distinction in the case is that Public reachability of a ZTNA listener is not permission to access the protected backend.

B:

A different principle is: Distributing a ZTNA destination does not guarantee the correct routed path or DNS view from every client location. It does not explain the deciding observation that FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session. The relevant relationship is: Public reachability of a ZTNA listener is not permission to access the protected backend.

C:

That competing principle concerns ZTNA policies typically require device trust evidence in addition to destination visibility. The current case is governed by: Public reachability of a ZTNA listener is not permission to access the protected backend.

Question 595

At fictional Brookfield Public Services, the zero trust and Security Fabric team is working while validating an approved endpoint security change. The FortiClient EMS 7.4 operational issue is: A contractor without EMS enrollment can reach the internet-facing FortiGate ZTNA listener and assumes it grants private application access by default. The observed evidence is: FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session. Which combined action AND independent proof BEST fit the incident?

  1. The Brookfield Public Services team should pair: Action: Investigate and remediate the endpoint's genuine posture condition rather than weakening the ZTNA rule for every authenticated employee. Independent confirmation: An eligible compliant device for the same user is allowed, while the original noncompliant state remains rejected until fixed.
  2. The Brookfield Public Services team should pair: Action: Enforce the intended managed-device and user authorization conditions on the ZTNA access proxy while maintaining a safe denial response. Independent confirmation: The unmanaged test device is rejected and a correctly enrolled compliant device with an authorized user reaches the intended application.
  3. The Brookfield Public Services team should pair: Action: Provide a supported remote-reachable ZTNA gateway name and certificate for off-network clients without exposing internal backend servers. Independent confirmation: An approved remote test reaches the protected app through the authenticated proxy while internal clients retain approved routes.
  4. The Brookfield Public Services team should pair: Action: Verify supported EMS certificate provisioning, endpoint connection state and trusted ZTNA configuration before retrying resource access. Independent confirmation: The eligible managed test device presents a valid trusted client identity and reaches only its permitted ZTNA application.

Explanation

Correct Answer

B:

The recorded cause is FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session. The appropriate change is: Enforce the intended managed-device and user authorization conditions on the ZTNA access proxy while maintaining a safe denial response. Its separate proof is: The unmanaged test device is rejected and a correctly enrolled compliant device with an authorized user reaches the intended application. Keep the scope controlled: Test fail-closed behavior and consider approved alternative access paths for exceptional user populations.

Incorrect Answers

A:

Another action-and-test combination is: Action: Investigate and remediate the endpoint's genuine posture condition rather than weakening the ZTNA rule for every authenticated employee. Independent confirmation: An eligible compliant device for the same user is allowed, while the original noncompliant state remains rejected until fixed. The pair does not directly address the record that FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session. The corresponding correction is: Enforce the intended managed-device and user authorization conditions on the ZTNA access proxy while maintaining a safe denial response.

C:

Another action-and-proof combination is: Provide a supported remote-reachable ZTNA gateway name and certificate for off-network clients without exposing internal backend servers. Independent confirmation: An approved remote test reaches the protected app through the authenticated proxy while internal clients retain approved routes. It does not prove recovery from the documented condition: FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session.

D:

An alternative action-and-proof pair is: Verify supported EMS certificate provisioning, endpoint connection state and trusted ZTNA configuration before retrying resource access. Independent confirmation: The eligible managed test device presents a valid trusted client identity and reaches only its permitted ZTNA application. It does not resolve the specific finding that FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session. The needed confirmation is the unmanaged test device is rejected and a correctly enrolled compliant device with an authorized user reaches the intended application.

Question 596

At fictional Westhaven Research, the zero trust and Security Fabric team is working during a recorded operations incident review. The FortiClient EMS 7.4 operational issue is: A contractor without EMS enrollment can reach the internet-facing FortiGate ZTNA listener and assumes it grants private application access by default. Diagnostic evidence: FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session. Which narrowly scoped response BEST addresses this specific problem?

  1. The Westhaven Research team should: Investigate and remediate the endpoint's genuine posture condition rather than weakening the ZTNA rule for every authenticated employee.
  2. The Westhaven Research team should: Provide a supported remote-reachable ZTNA gateway name and certificate for off-network clients without exposing internal backend servers.
  3. The Westhaven Research team should: Verify supported EMS certificate provisioning, endpoint connection state and trusted ZTNA configuration before retrying resource access.
  4. The Westhaven Research team should: Enforce the intended managed-device and user authorization conditions on the ZTNA access proxy while maintaining a safe denial response.

Explanation

Correct Answer

D:

FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session. The relevant mechanism is that Public reachability of a ZTNA listener is not permission to access the protected backend. The intended change is: Enforce the intended managed-device and user authorization conditions on the ZTNA access proxy while maintaining a safe denial response.

Incorrect Answers

A:

That alternative addresses another problem: Investigate and remediate the endpoint's genuine posture condition rather than weakening the ZTNA rule for every authenticated employee. Here, however, the evidence indicates FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session. Public reachability of a ZTNA listener is not permission to access the protected backend.

B:

Another proposed operation is: Provide a supported remote-reachable ZTNA gateway name and certificate for off-network clients without exposing internal backend servers. That differs from the documented cause: FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session. The specific response should be: Enforce the intended managed-device and user authorization conditions on the ZTNA access proxy while maintaining a safe denial response.

C:

This choice concerns another issue: Verify supported EMS certificate provisioning, endpoint connection state and trusted ZTNA configuration before retrying resource access. The fault actually shown is FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session. Verify the focused fix by checking the unmanaged test device is rejected and a correctly enrolled compliant device with an authorized user reaches the intended application.

Question 597

At fictional Westhaven Research, the zero trust and Security Fabric team is working during a recorded operations incident review. The FortiClient EMS 7.4 operational issue is: A contractor without EMS enrollment can reach the internet-facing FortiGate ZTNA listener and assumes it grants private application access by default. Which diagnostic observation MOST specifically supports this problem rather than another FortiClient EMS fault?

  1. The decisive observation for Westhaven Research is: Authentication logs show a valid user session while the FortiGate EMS posture match fails for the same device.
  2. The decisive observation for Westhaven Research is: External DNS for the resource returns an internal-only address while EMS endpoint profile lists the destination correctly.
  3. The decisive observation for Westhaven Research is: Client diagnostics show enrollment completed but no valid EMS-issued or supported ZTNA client certificate for the proxy handshake.
  4. The decisive observation for Westhaven Research is: FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session.

Explanation

Correct Answer

D:

The diagnostic record shows FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session. The cause is consistent with Public reachability of a ZTNA listener is not permission to access the protected backend. For Westhaven Research, the relevant observation is FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session.

Incorrect Answers

A:

Another possible finding is: Authentication logs show a valid user session while the FortiGate EMS posture match fails for the same device. For this incident, the direct diagnostic clue is FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session.

B:

A different observation is: External DNS for the resource returns an internal-only address while EMS endpoint profile lists the destination correctly. That describes a different condition; the one documented here is: FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session.

C:

Even if Client diagnostics show enrollment completed but no valid EMS-issued or supported ZTNA client certificate for the proxy handshake, it would not establish this cause. The relevant trace is FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session.

Question 598

At fictional Westhaven Research, the zero trust and Security Fabric team is working during a recorded operations incident review. The FortiClient EMS 7.4 operational issue is: A contractor without EMS enrollment can reach the internet-facing FortiGate ZTNA listener and assumes it grants private application access by default. The team has approved this response: Enforce the intended managed-device and user authorization conditions on the ZTNA access proxy while maintaining a safe denial response. Which independent result BEST verifies the intended fix?

  1. The independent success test at Westhaven Research is: An eligible compliant device for the same user is allowed, while the original noncompliant state remains rejected until fixed.
  2. The independent success test at Westhaven Research is: The unmanaged test device is rejected and a correctly enrolled compliant device with an authorized user reaches the intended application.
  3. The independent success test at Westhaven Research is: An approved remote test reaches the protected app through the authenticated proxy while internal clients retain approved routes.
  4. The independent success test at Westhaven Research is: The eligible managed test device presents a valid trusted client identity and reaches only its permitted ZTNA application.

Explanation

Correct Answer

B:

An independent postchange test demonstrates that the unmanaged test device is rejected and a correctly enrolled compliant device with an authorized user reaches the intended application. It is linked to the original evidence: FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session.

Incorrect Answers

A:

Even if an eligible compliant device for the same user is allowed, while the original noncompliant state remains rejected until fixed, the original fault would remain unproven. An independent test must demonstrate the unmanaged test device is rejected and a correctly enrolled compliant device with an authorized user reaches the intended application.

C:

That result would verify another outcome: An approved remote test reaches the protected app through the authenticated proxy while internal clients retain approved routes. It does not test the particular evidence FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session. The needed result is: The unmanaged test device is rejected and a correctly enrolled compliant device with an authorized user reaches the intended application. For Westhaven Research, the relevant observation is FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session.

D:

A different check would show: The eligible managed test device presents a valid trusted client identity and reaches only its permitted ZTNA application. It would not verify the required outcome, which is the unmanaged test device is rejected and a correctly enrolled compliant device with an authorized user reaches the intended application. For Westhaven Research, the relevant observation is FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session.

Question 599

At fictional Westhaven Research, the zero trust and Security Fabric team is working during a recorded operations incident review. The FortiClient EMS 7.4 operational issue is: A contractor without EMS enrollment can reach the internet-facing FortiGate ZTNA listener and assumes it grants private application access by default. The discriminating evidence is: FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session. Which endpoint management or security principle BEST explains the proper response?

  1. The relevant Fortinet design principle for Westhaven Research is: Zero-trust authorization can combine user identity and device security state as independent policy conditions.
  2. The relevant Fortinet design principle for Westhaven Research is: Distributing a ZTNA destination does not guarantee the correct routed path or DNS view from every client location.
  3. The relevant Fortinet design principle for Westhaven Research is: ZTNA policies typically require device trust evidence in addition to destination visibility.
  4. The relevant Fortinet design principle for Westhaven Research is: Public reachability of a ZTNA listener is not permission to access the protected backend.

Explanation

Correct Answer

D:

The relevant distinction is: Public reachability of a ZTNA listener is not permission to access the protected backend. Here the evidence is FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session.

Incorrect Answers

A:

A different principle is: Zero-trust authorization can combine user identity and device security state as independent policy conditions. It does not account for the specific observation: FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session. The applicable principle is: Public reachability of a ZTNA listener is not permission to access the protected backend.

B:

A different relationship is: Distributing a ZTNA destination does not guarantee the correct routed path or DNS view from every client location. The distinction in the case is that Public reachability of a ZTNA listener is not permission to access the protected backend.

C:

A different principle is: ZTNA policies typically require device trust evidence in addition to destination visibility. It does not explain the deciding observation that FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session. The relevant relationship is: Public reachability of a ZTNA listener is not permission to access the protected backend.

Question 600

At fictional Westhaven Research, the zero trust and Security Fabric team is working during a recorded operations incident review. The FortiClient EMS 7.4 operational issue is: A contractor without EMS enrollment can reach the internet-facing FortiGate ZTNA listener and assumes it grants private application access by default. The observed evidence is: FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session. Which combined action AND independent proof BEST fit the incident?

  1. The Westhaven Research team should pair: Action: Investigate and remediate the endpoint's genuine posture condition rather than weakening the ZTNA rule for every authenticated employee. Independent confirmation: An eligible compliant device for the same user is allowed, while the original noncompliant state remains rejected until fixed.
  2. The Westhaven Research team should pair: Action: Provide a supported remote-reachable ZTNA gateway name and certificate for off-network clients without exposing internal backend servers. Independent confirmation: An approved remote test reaches the protected app through the authenticated proxy while internal clients retain approved routes.
  3. The Westhaven Research team should pair: Action: Enforce the intended managed-device and user authorization conditions on the ZTNA access proxy while maintaining a safe denial response. Independent confirmation: The unmanaged test device is rejected and a correctly enrolled compliant device with an authorized user reaches the intended application.
  4. The Westhaven Research team should pair: Action: Verify supported EMS certificate provisioning, endpoint connection state and trusted ZTNA configuration before retrying resource access. Independent confirmation: The eligible managed test device presents a valid trusted client identity and reaches only its permitted ZTNA application.

Explanation

Correct Answer

C:

The recorded cause is FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session. The appropriate change is: Enforce the intended managed-device and user authorization conditions on the ZTNA access proxy while maintaining a safe denial response. Its separate proof is: The unmanaged test device is rejected and a correctly enrolled compliant device with an authorized user reaches the intended application.

Incorrect Answers

A:

A different action-and-proof pair is: Investigate and remediate the endpoint's genuine posture condition rather than weakening the ZTNA rule for every authenticated employee. Independent confirmation: An eligible compliant device for the same user is allowed, while the original noncompliant state remains rejected until fixed. The evidence here is FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session; the matching check is the unmanaged test device is rejected and a correctly enrolled compliant device with an authorized user reaches the intended application.

B:

Another action-and-test combination is: Action: Provide a supported remote-reachable ZTNA gateway name and certificate for off-network clients without exposing internal backend servers. Independent confirmation: An approved remote test reaches the protected app through the authenticated proxy while internal clients retain approved routes. The pair does not directly address the record that FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session. The corresponding correction is: Enforce the intended managed-device and user authorization conditions on the ZTNA access proxy while maintaining a safe denial response.

D:

Another action-and-proof combination is: Verify supported EMS certificate provisioning, endpoint connection state and trusted ZTNA configuration before retrying resource access. Independent confirmation: The eligible managed test device presents a valid trusted client identity and reaches only its permitted ZTNA application. It does not prove recovery from the documented condition: FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session.

Fortinet NSE 6 - FortiClient EMS 7.4 Administrator (FCP_FCT_AD-7.4) Practice Tests