Fortinet FCP_FCT_AD-7.4 Practice Test 59 - 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 59

Question 580

At fictional Stonebridge Media, the zero trust and Security Fabric team is working during a recorded operations incident review. The FortiClient EMS 7.4 operational issue is: A ZTNA application proxy treats all registered endpoints as compliant even though one has a documented missing critical security patch. The observed evidence is: The EMS posture rule matches only registration presence and the firewall's dynamic group lacks the intended patch or vulnerability requirement. Which combined action AND independent proof BEST fit the incident?

  1. The Stonebridge Media team should pair: Action: Create a supported narrowly defined EMS posture rule for the required update state and use that tag in the FortiGate access decision. Independent confirmation: A patched managed test endpoint accesses the application while a vulnerable enrolled comparison is denied.
  2. The Stonebridge Media 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.
  3. The Stonebridge Media 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.
  4. The Stonebridge Media 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.

Explanation

Correct Answer

A:

Choose the action: Create a supported narrowly defined EMS posture rule for the required update state and use that tag in the FortiGate access decision. Then verify it against a patched managed test endpoint accesses the application while a vulnerable enrolled comparison is denied. Both steps concern the original finding: The EMS posture rule matches only registration presence and the firewall's dynamic group lacks the intended patch or vulnerability requirement.

Incorrect Answers

B:

Another proposal begins with: 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. For this case, apply the specific action: Create a supported narrowly defined EMS posture rule for the required update state and use that tag in the FortiGate access decision. Verify its effect with: A patched managed test endpoint accesses the application while a vulnerable enrolled comparison is denied. For Stonebridge Media, the relevant observation is The EMS posture rule matches only registration presence and the firewall's dynamic group lacks the intended patch or vulnerability requirement.

C:

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 the EMS posture rule matches only registration presence and the firewall's dynamic group lacks the intended patch or vulnerability requirement; the matching check is a patched managed test endpoint accesses the application while a vulnerable enrolled comparison is denied. For Stonebridge Media, the relevant observation is The EMS posture rule matches only registration presence and the firewall's dynamic group lacks the intended patch or vulnerability requirement.

D:

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 the EMS posture rule matches only registration presence and the firewall's dynamic group lacks the intended patch or vulnerability requirement. The corresponding correction is: Create a supported narrowly defined EMS posture rule for the required update state and use that tag in the FortiGate access decision.

Question 581

At fictional Crestwood Medical, 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 client receives the HR application's ZTNA destination from EMS but the published proxy hostname does not route to the intended protected web service. Diagnostic evidence: DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service. Which narrowly scoped response BEST addresses this specific problem?

  1. The Crestwood Medical team should: Enforce the intended managed-device and user authorization conditions on the ZTNA access proxy while maintaining a safe denial response.
  2. The Crestwood Medical team should: Restore supported secure time synchronization and test the current EMS token refresh and trust workflow.
  3. The Crestwood Medical team should: Update the vendor-supported OS condition in the EMS posture tagging rule and validate the resulting gateway dynamic group.
  4. The Crestwood Medical team should: Align the approved public proxy FQDN, matching certificate, access-proxy virtual service and backend mapping for the resource.

Explanation

Correct Answer

D:

DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service. Address the root issue through this bounded action: Align the approved public proxy FQDN, matching certificate, access-proxy virtual service and backend mapping for the resource. Client destination settings, gateway access proxy and protected backend mapping must agree for ZTNA connectivity.

Incorrect Answers

A:

Another option proposes: Enforce the intended managed-device and user authorization conditions on the ZTNA access proxy while maintaining a safe denial response. It does not address the case evidence. DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service. The targeted remedy is: Align the approved public proxy FQDN, matching certificate, access-proxy virtual service and backend mapping for the resource.

B:

That alternative addresses another problem: Restore supported secure time synchronization and test the current EMS token refresh and trust workflow. Here, however, the evidence indicates DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service. Client destination settings, gateway access proxy and protected backend mapping must agree for ZTNA connectivity.

C:

Another proposed operation is: Update the vendor-supported OS condition in the EMS posture tagging rule and validate the resulting gateway dynamic group. That differs from the documented cause: DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service. The specific response should be: Align the approved public proxy FQDN, matching certificate, access-proxy virtual service and backend mapping for the resource.

Question 582

At fictional Crestwood Medical, 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 client receives the HR application's ZTNA destination from EMS but the published proxy hostname does not route to the intended protected web service. Which diagnostic observation MOST specifically supports this problem rather than another FortiClient EMS fault?

  1. The decisive observation for Crestwood Medical is: FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session.
  2. The decisive observation for Crestwood Medical is: EMS and FortiClient logs show an expired token or certificate validation time mismatch and significant client clock drift.
  3. The decisive observation for Crestwood Medical is: The EMS security posture rule references an outdated major version condition and treats the device as meeting its compliance tag.
  4. The decisive observation for Crestwood Medical is: DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service.

Explanation

Correct Answer

D:

Look for DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service. It isolates the condition described in the question rather than an unrelated fault. The relevant principle is: Client destination settings, gateway access proxy and protected backend mapping must agree for ZTNA connectivity.

Incorrect Answers

A:

That observation would suggest a different failure: FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session. Here the record instead identifies DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service.

B:

That observation concerns: EMS and FortiClient logs show an expired token or certificate validation time mismatch and significant client clock drift. It is not the decisive fact in this case. The controlling evidence is: DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service.

C:

Another possible observation is: The EMS security posture rule references an outdated major version condition and treats the device as meeting its compliance tag. The record instead shows DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service. This distinction matters because Client destination settings, gateway access proxy and protected backend mapping must agree for ZTNA connectivity.

Question 583

At fictional Crestwood Medical, 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 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 team has approved this response: Align the approved public proxy FQDN, matching certificate, access-proxy virtual service and backend mapping for the resource. Which independent result BEST verifies the intended fix?

  1. The independent success test at Crestwood Medical is: A tagged authorized user reaches the right HR web service and unauthorized destinations remain unreachable through that proxy.
  2. The independent success test at Crestwood Medical 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 Crestwood Medical is: A corrected client refreshes its accepted token and accesses the permitted application without widening token lifetime unnecessarily.
  4. The independent success test at Crestwood Medical is: A current approved OS receives the compliant tag and the unsupported version is denied without blocking unrelated endpoints.

Explanation

Correct Answer

A:

A separate verification is that a tagged authorized user reaches the right HR web service and unauthorized destinations remain unreachable through that proxy. That outcome tests whether the original condition—DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service—was corrected.

Incorrect Answers

B:

That result tests a separate condition: The unmanaged test device is rejected and a correctly enrolled compliant device with an authorized user reaches the intended application. The case-specific acceptance test is: A tagged authorized user reaches the right HR web service and unauthorized destinations remain unreachable through that proxy.

C:

Another check considers: A corrected client refreshes its accepted token and accesses the permitted application without widening token lifetime unnecessarily. It does not establish that the documented condition has been corrected: DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service. Use this acceptance criterion instead: A tagged authorized user reaches the right HR web service and unauthorized destinations remain unreachable through that proxy.

D:

Even if a current approved OS receives the compliant tag and the unsupported version is denied without blocking unrelated endpoints, the original fault would remain unproven. An independent test must demonstrate a tagged authorized user reaches the right HR web service and unauthorized destinations remain unreachable through that proxy.

Question 584

At fictional Crestwood Medical, 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 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 discriminating evidence is: DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service. Which endpoint management or security principle BEST explains the proper response?

  1. The relevant Fortinet design principle for Crestwood Medical is: Public reachability of a ZTNA listener is not permission to access the protected backend.
  2. The relevant Fortinet design principle for Crestwood Medical is: Client destination settings, gateway access proxy and protected backend mapping must agree for ZTNA connectivity.
  3. The relevant Fortinet design principle for Crestwood Medical is: Short-lived zero-trust credentials require timely renewal and trustworthy time validation.
  4. The relevant Fortinet design principle for Crestwood Medical is: Posture tags are meaningful only when their rules accurately reflect the accepted endpoint requirements.

Explanation

Correct Answer

B:

The evidence that DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service is best explained by this principle: Client destination settings, gateway access proxy and protected backend mapping must agree for ZTNA connectivity.

Incorrect Answers

A:

That competing principle concerns Public reachability of a ZTNA listener is not permission to access the protected backend. The current case is governed by: Client destination settings, gateway access proxy and protected backend mapping must agree for ZTNA connectivity.

C:

This alternative instead invokes: Short-lived zero-trust credentials require timely renewal and trustworthy time validation. The documented evidence instead points to Client destination settings, gateway access proxy and protected backend mapping must agree for ZTNA connectivity.

D:

A different principle is: Posture tags are meaningful only when their rules accurately reflect the accepted endpoint requirements. It does not account for the specific observation: DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service. The applicable principle is: Client destination settings, gateway access proxy and protected backend mapping must agree for ZTNA connectivity.

Question 585

At fictional Crestwood Medical, 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 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 Crestwood Medical 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.
  2. The Crestwood Medical 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.
  3. The Crestwood Medical 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.
  4. The Crestwood Medical 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

C:

Under the documented condition—DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service—the bounded response is: Align the approved public proxy FQDN, matching certificate, access-proxy virtual service and backend mapping for the resource. An independent check is: A tagged authorized user reaches the right HR web service and unauthorized destinations remain unreachable through that proxy.

Incorrect Answers

A:

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.

B:

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.

D:

A different action-and-proof pair is: 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. The evidence here is DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service; the matching check is a tagged authorized user reaches the right HR web service and unauthorized destinations remain unreachable through that proxy.

Question 586

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. Diagnostic evidence: DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service. Which narrowly scoped response BEST addresses this specific problem?

  1. The Lakeshore Community team should: Align the approved public proxy FQDN, matching certificate, access-proxy virtual service and backend mapping for the resource.
  2. The Lakeshore Community team should: Enforce the intended managed-device and user authorization conditions on the ZTNA access proxy while maintaining a safe denial response.
  3. The Lakeshore Community team should: Restore supported secure time synchronization and test the current EMS token refresh and trust workflow.
  4. The Lakeshore Community team should: Update the vendor-supported OS condition in the EMS posture tagging rule and validate the resulting gateway dynamic group.

Explanation

Correct Answer

A:

The case shows DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service. Align the approved public proxy FQDN, matching certificate, access-proxy virtual service and backend mapping for the resource. A separate test should confirm that a tagged authorized user reaches the right HR web service and unauthorized destinations remain unreachable through that proxy.

Incorrect Answers

B:

A different option proposes: Enforce the intended managed-device and user authorization conditions on the ZTNA access proxy while maintaining a safe denial response. It does not correct the recorded finding that DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service. The appropriate scoped change is: Align the approved public proxy FQDN, matching certificate, access-proxy virtual service and backend mapping for the resource.

C:

Another possible response is: Restore supported secure time synchronization and test the current EMS token refresh and trust workflow. The case instead shows: DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service. The matching correction is: Align the approved public proxy FQDN, matching certificate, access-proxy virtual service and backend mapping for the resource.

D:

That option would instead pursue: Update the vendor-supported OS condition in the EMS posture tagging rule and validate the resulting gateway dynamic group. It addresses a different dependency; the deciding observation here is DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service.

Question 587

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. Which diagnostic observation MOST specifically supports this problem rather than another FortiClient EMS fault?

  1. The decisive observation for Lakeshore Community is: FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session.
  2. The decisive observation for Lakeshore Community is: EMS and FortiClient logs show an expired token or certificate validation time mismatch and significant client clock drift.
  3. The decisive observation for Lakeshore Community is: DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service.
  4. The decisive observation for Lakeshore Community is: The EMS security posture rule references an outdated major version condition and treats the device as meeting its compliance tag.

Explanation

Correct Answer

C:

DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service. That finding distinguishes the issue because Client destination settings, gateway access proxy and protected backend mapping must agree for ZTNA connectivity. The matching correction is: Align the approved public proxy FQDN, matching certificate, access-proxy virtual service and backend mapping for the resource.

Incorrect Answers

A:

Even if FortiGate logs show no valid device identity or required EMS posture tag for the contractor's session, it would not establish this cause. The relevant trace is DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service.

B:

That observation would suggest a different failure: EMS and FortiClient logs show an expired token or certificate validation time mismatch and significant client clock drift. Here the record instead identifies DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service.

D:

Another possible observation is: The EMS security posture rule references an outdated major version condition and treats the device as meeting its compliance tag. The record instead shows DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service. This distinction matters because Client destination settings, gateway access proxy and protected backend mapping must agree for ZTNA connectivity. 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.

Question 588

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 team has approved this response: Align the approved public proxy FQDN, matching certificate, access-proxy virtual service and backend mapping for the resource. Which independent result BEST verifies the intended fix?

  1. The independent success test at Lakeshore Community is: The unmanaged test device is rejected and a correctly enrolled compliant device with an authorized user reaches the intended application.
  2. The independent success test at Lakeshore Community is: A corrected client refreshes its accepted token and accesses the permitted application without widening token lifetime unnecessarily.
  3. The independent success test at Lakeshore Community is: A tagged authorized user reaches the right HR web service and unauthorized destinations remain unreachable through that proxy.
  4. The independent success test at Lakeshore Community is: A current approved OS receives the compliant tag and the unsupported version is denied without blocking unrelated endpoints.

Explanation

Correct Answer

C:

Check the result using the following observation: A tagged authorized user reaches the right HR web service and unauthorized destinations remain unreachable through that proxy. A completed configuration alone would not prove the issue behind DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service is resolved.

Incorrect Answers

A:

That result would verify another outcome: The unmanaged test device is rejected and a correctly enrolled compliant device with an authorized user reaches the intended application. It does not test the particular evidence DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service. The needed result is: A tagged authorized user reaches the right HR web service and unauthorized destinations remain unreachable through that proxy.

B:

A different check would show: A corrected client refreshes its accepted token and accesses the permitted application without widening token lifetime unnecessarily. It would not verify the required outcome, which is a tagged authorized user reaches the right HR web service and unauthorized destinations remain unreachable through that proxy.

D:

Another check considers: A current approved OS receives the compliant tag and the unsupported version is denied without blocking unrelated endpoints. It does not establish that the documented condition has been corrected: DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service. Use this acceptance criterion instead: A tagged authorized user reaches the right HR web service and unauthorized destinations remain unreachable through that proxy.

Question 589

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 discriminating evidence is: DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service. Which endpoint management or security principle BEST explains the proper response?

  1. The relevant Fortinet design principle for Lakeshore Community is: Public reachability of a ZTNA listener is not permission to access the protected backend.
  2. The relevant Fortinet design principle for Lakeshore Community is: Short-lived zero-trust credentials require timely renewal and trustworthy time validation.
  3. The relevant Fortinet design principle for Lakeshore Community is: Posture tags are meaningful only when their rules accurately reflect the accepted endpoint requirements.
  4. The relevant Fortinet design principle for Lakeshore Community is: Client destination settings, gateway access proxy and protected backend mapping must agree for ZTNA connectivity.

Explanation

Correct Answer

D:

Client destination settings, gateway access proxy and protected backend mapping must agree for ZTNA connectivity. That is why the reported condition—DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service—needs the specific response: Align the approved public proxy FQDN, matching certificate, access-proxy virtual service and backend mapping for the resource.

Incorrect Answers

A:

A different principle is: Public reachability of a ZTNA listener is not permission to access the protected backend. It does not explain the deciding observation that DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service. The relevant relationship is: Client destination settings, gateway access proxy and protected backend mapping must agree for ZTNA connectivity.

B:

That competing principle concerns Short-lived zero-trust credentials require timely renewal and trustworthy time validation. The current case is governed by: Client destination settings, gateway access proxy and protected backend mapping must agree for ZTNA connectivity.

C:

Another principle states: Posture tags are meaningful only when their rules accurately reflect the accepted endpoint requirements. However, this incident shows DNS and connection traces reach the FortiGate, while the ZTNA access proxy mapping references the wrong backend target or service. The principle that accounts for it is: Client destination settings, gateway access proxy and protected backend mapping must agree for ZTNA connectivity.

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.

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