McAfee-Secured Website

Exam Code: FCP_FCT_AD-7.4

Exam Name: Fortinet NSE 6 - FortiClient EMS 7.4 Administrator

Certification Provider: Fortinet

Corresponding Certification: NSE6

100% Fortinet FCP_FCT_AD-7.4 Guaranteed Success With Testking Training Materials

Get Real FCP_FCT_AD-7.4 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

33 Questions & Answers with Testing Engine

"Fortinet NSE 6 - FortiClient EMS 7.4 Administrator Exam", also known as FCP_FCT_AD-7.4 exam, is a Fortinet certification exam.

Pass your tests with the always up-to-date FCP_FCT_AD-7.4 Exam Engine. Your FCP_FCT_AD-7.4 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 FCP_FCT_AD-7.4 Practice Test 45

Question 440

Original fictional FortiClient EMS 7.4 practice case R181-CASE-110 — Manufacturing company inspecting connector logs. Observed evidence: The team troubleshoots endpoint agents before checking the known failed EMS Fabric session. Which follow-up operational gate best detects a recurrence of the same failure after recovery?

  1. Add a tested post-change acceptance gate requiring this outcome: EMS endpoint registrations stay healthy and FortiGate tag sync recovers. Flag any recurrence of this warning sign: The team troubleshoots endpoint agents before checking the known failed EMS Fabric session.
  2. Add a tested post-change acceptance gate requiring this outcome: A noncompliant client is denied while a compliant test client is allowed. Flag any recurrence of this warning sign: A permissive fallback firewall policy shadows the newly created ZTNA tag-based rule.
  3. Add a tested post-change acceptance gate requiring this outcome: All branches select the approved dynamic tag object for the same posture rule. Flag any recurrence of this warning sign: One FortiGate uses different locally edited tag names than the EMS-approved nomenclature.
  4. Add a tested post-change acceptance gate requiring this outcome: The connector is authorized and expected posture tags appear on FortiGate. Flag any recurrence of this warning sign: The firewall has an EMS connector entry but has not completed mutual authorization.

Explanation

Correct Answer

A:

The preventive gate explicitly checks: EMS endpoint registrations stay healthy and FortiGate tag sync recovers, and escalates recurrence of: The team troubleshoots endpoint agents before checking the known failed EMS Fabric session. That pair addresses the identified issue: Endpoint telemetry health and Fabric connector health are different integration paths. The control is derived from the case recovery evidence, not separately certified by a Fortinet subject-matter expert.

Incorrect Answers

B:

Incorrect for this incident. That acceptance gate guards against a different situation: A permissive fallback firewall policy shadows the newly created ZTNA tag-based rule. The current failure to watch for is: The team troubleshoots endpoint agents before checking the known failed EMS Fabric session. Use a monitored gate confirming: EMS endpoint registrations stay healthy and FortiGate tag sync recovers.

C:

Incorrect for this incident. That acceptance gate guards against a different situation: One FortiGate uses different locally edited tag names than the EMS-approved nomenclature. The current failure to watch for is: The team troubleshoots endpoint agents before checking the known failed EMS Fabric session. Use a monitored gate confirming: EMS endpoint registrations stay healthy and FortiGate tag sync recovers.

D:

Incorrect for this incident. That acceptance gate guards against a different situation: The firewall has an EMS connector entry but has not completed mutual authorization. The current failure to watch for is: The team troubleshoots endpoint agents before checking the known failed EMS Fabric session. Use a monitored gate confirming: EMS endpoint registrations stay healthy and FortiGate tag sync recovers.

Question 441

Original fictional FortiClient EMS 7.4 practice case R181-CASE-111 — Law firm refactoring network segmentation. Observed evidence: A permissive fallback firewall policy shadows the newly created ZTNA tag-based rule. Which focused administrator action best resolves the identified problem while preserving unrelated security controls?

  1. Correct the policy sequence and scope so the tag-based condition is enforced.
  2. Validate the renewed EMS certificate and reauthorize affected peers if required.
  3. Import supported EMS security posture tags through the Fabric connector and bind scoped policies.
  4. Map detection, authorization and policy enforcement in an approved incident workflow.

Explanation

Correct Answer

A:

Correct for this fictional case. The distinguishing signal is: A permissive fallback firewall policy shadows the newly created ZTNA tag-based rule. It points to: Rule evaluation order prevents the intended posture-based restriction. The targeted correction is: Correct the policy sequence and scope so the tag-based condition is enforced. Verify success by checking: A noncompliant client is denied while a compliant test client is allowed. The response is scoped to this observed failure and should not weaken other policies.

Incorrect Answers

B:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: EMS server certificate is renewed but the Fabric peer still trusts the prior identity. That case concerns: Connector trust continuity was omitted from certificate maintenance. Here the observed distinction is: A permissive fallback firewall policy shadows the newly created ZTNA tag-based rule. A more directly targeted response is: Correct the policy sequence and scope so the tag-based condition is enforced.

C:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: FortiGate policies reference a manually maintained list of client IPs instead of EMS posture tags. That case concerns: Static address rules cannot reflect changing endpoint security attributes. Here the observed distinction is: A permissive fallback firewall policy shadows the newly created ZTNA tag-based rule. A more directly targeted response is: Correct the policy sequence and scope so the tag-based condition is enforced.

D:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: EMS shows a compromised endpoint but there is no documented process connecting the alert to firewall action. That case concerns: Threat response responsibilities across EMS, FortiGate and monitoring are undefined. Here the observed distinction is: A permissive fallback firewall policy shadows the newly created ZTNA tag-based rule. A more directly targeted response is: Correct the policy sequence and scope so the tag-based condition is enforced.

Question 442

Original fictional FortiClient EMS 7.4 practice case R181-CASE-111 — Law firm refactoring network segmentation. Observed evidence: A permissive fallback firewall policy shadows the newly created ZTNA tag-based rule. After the scoped corrective action, which observation best confirms this specific incident was resolved?

  1. Authorized connectors report healthy trust after the rollover.
  2. A noncompliant client is denied while a compliant test client is allowed.
  3. FortiGate dynamic objects update as test endpoint posture changes.
  4. A tabletop event produces the intended approved response without automatic overreach.

Explanation

Correct Answer

B:

This is the case-specific acceptance evidence after taking the targeted step: Correct the policy sequence and scope so the tag-based condition is enforced. The initial signal was: A permissive fallback firewall policy shadows the newly created ZTNA tag-based rule. A generic online indication alone would not prove this particular issue was resolved: Rule evaluation order prevents the intended posture-based restriction.

Incorrect Answers

A:

Incorrect for this incident. This result would support a different diagnosis: Connector trust continuity was omitted from certificate maintenance; its warning sign is: EMS server certificate is renewed but the Fabric peer still trusts the prior identity. The current case instead requires verification that: A noncompliant client is denied while a compliant test client is allowed. That follows remediation of: Rule evaluation order prevents the intended posture-based restriction.

C:

Incorrect for this incident. This result would support a different diagnosis: Static address rules cannot reflect changing endpoint security attributes; its warning sign is: FortiGate policies reference a manually maintained list of client IPs instead of EMS posture tags. The current case instead requires verification that: A noncompliant client is denied while a compliant test client is allowed. That follows remediation of: Rule evaluation order prevents the intended posture-based restriction.

D:

Incorrect for this incident. This result would support a different diagnosis: Threat response responsibilities across EMS, FortiGate and monitoring are undefined; its warning sign is: EMS shows a compromised endpoint but there is no documented process connecting the alert to firewall action. The current case instead requires verification that: A noncompliant client is denied while a compliant test client is allowed. That follows remediation of: Rule evaluation order prevents the intended posture-based restriction.

Question 443

Original fictional FortiClient EMS 7.4 practice case R181-CASE-111 — Law firm refactoring network segmentation. Observed evidence: A permissive fallback firewall policy shadows the newly created ZTNA tag-based rule. Which management, security, or integration failure most directly explains the evidence?

  1. Connector trust continuity was omitted from certificate maintenance.
  2. Static address rules cannot reflect changing endpoint security attributes.
  3. Rule evaluation order prevents the intended posture-based restriction.
  4. Threat response responsibilities across EMS, FortiGate and monitoring are undefined.

Explanation

Correct Answer

C:

The supplied evidence — A permissive fallback firewall policy shadows the newly created ZTNA tag-based rule — most directly supports: Rule evaluation order prevents the intended posture-based restriction. Confirm the explanation by applying the controlled correction: Correct the policy sequence and scope so the tag-based condition is enforced; then checking that: A noncompliant client is denied while a compliant test client is allowed. Similar symptoms can have other causes in real deployments.

Incorrect Answers

A:

Incorrect for the stated evidence. This alternative concern better explains a different situation: EMS server certificate is renewed but the Fabric peer still trusts the prior identity. Here the actual observation — A permissive fallback firewall policy shadows the newly created ZTNA tag-based rule — most directly indicates: Rule evaluation order prevents the intended posture-based restriction. The scoped correction is: Correct the policy sequence and scope so the tag-based condition is enforced.

B:

Incorrect for the stated evidence. This alternative concern better explains a different situation: FortiGate policies reference a manually maintained list of client IPs instead of EMS posture tags. Here the actual observation — A permissive fallback firewall policy shadows the newly created ZTNA tag-based rule — most directly indicates: Rule evaluation order prevents the intended posture-based restriction. The scoped correction is: Correct the policy sequence and scope so the tag-based condition is enforced.

D:

Incorrect for the stated evidence. This alternative concern better explains a different situation: EMS shows a compromised endpoint but there is no documented process connecting the alert to firewall action. Here the actual observation — A permissive fallback firewall policy shadows the newly created ZTNA tag-based rule — most directly indicates: Rule evaluation order prevents the intended posture-based restriction. The scoped correction is: Correct the policy sequence and scope so the tag-based condition is enforced.

Question 444

Original fictional FortiClient EMS 7.4 practice case R181-CASE-111 — Law firm refactoring network segmentation. Observed evidence: A permissive fallback firewall policy shadows the newly created ZTNA tag-based rule. Which follow-up operational gate best detects a recurrence of the same failure after recovery?

  1. Add a tested post-change acceptance gate requiring this outcome: A noncompliant client is denied while a compliant test client is allowed. Flag any recurrence of this warning sign: A permissive fallback firewall policy shadows the newly created ZTNA tag-based rule.
  2. Add a tested post-change acceptance gate requiring this outcome: A tabletop event produces the intended approved response without automatic overreach. Flag any recurrence of this warning sign: EMS shows a compromised endpoint but there is no documented process connecting the alert to firewall action.
  3. Add a tested post-change acceptance gate requiring this outcome: Authorized connectors report healthy trust after the rollover. Flag any recurrence of this warning sign: EMS server certificate is renewed but the Fabric peer still trusts the prior identity.
  4. Add a tested post-change acceptance gate requiring this outcome: FortiGate dynamic objects update as test endpoint posture changes. Flag any recurrence of this warning sign: FortiGate policies reference a manually maintained list of client IPs instead of EMS posture tags.

Explanation

Correct Answer

A:

The preventive gate explicitly checks: A noncompliant client is denied while a compliant test client is allowed, and escalates recurrence of: A permissive fallback firewall policy shadows the newly created ZTNA tag-based rule. That pair addresses the identified issue: Rule evaluation order prevents the intended posture-based restriction. The control is derived from the case recovery evidence, not separately certified by a Fortinet subject-matter expert.

Incorrect Answers

B:

Incorrect for this incident. That acceptance gate guards against a different situation: EMS shows a compromised endpoint but there is no documented process connecting the alert to firewall action. The current failure to watch for is: A permissive fallback firewall policy shadows the newly created ZTNA tag-based rule. Use a monitored gate confirming: A noncompliant client is denied while a compliant test client is allowed.

C:

Incorrect for this incident. That acceptance gate guards against a different situation: EMS server certificate is renewed but the Fabric peer still trusts the prior identity. The current failure to watch for is: A permissive fallback firewall policy shadows the newly created ZTNA tag-based rule. Use a monitored gate confirming: A noncompliant client is denied while a compliant test client is allowed.

D:

Incorrect for this incident. That acceptance gate guards against a different situation: FortiGate policies reference a manually maintained list of client IPs instead of EMS posture tags. The current failure to watch for is: A permissive fallback firewall policy shadows the newly created ZTNA tag-based rule. Use a monitored gate confirming: A noncompliant client is denied while a compliant test client is allowed.

Question 445

Original fictional FortiClient EMS 7.4 practice case R181-CASE-112 — Healthcare IT planning certificate renewal. Observed evidence: EMS server certificate is renewed but the Fabric peer still trusts the prior identity. Which focused administrator action best resolves the identified problem while preserving unrelated security controls?

  1. Configure and test the supported FortiClient and FortiGate logging path to FortiAnalyzer.
  2. Validate the renewed EMS certificate and reauthorize affected peers if required.
  3. Correct the connector target and revalidate its trust relationship.
  4. Restrict tag-based policy application to the designated protected resources.

Explanation

Correct Answer

B:

Correct for this fictional case. The distinguishing signal is: EMS server certificate is renewed but the Fabric peer still trusts the prior identity. It points to: Connector trust continuity was omitted from certificate maintenance. The targeted correction is: Validate the renewed EMS certificate and reauthorize affected peers if required. Verify success by checking: Authorized connectors report healthy trust after the rollover. The response is scoped to this observed failure and should not weaken other policies.

Incorrect Answers

A:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: An IoC response design omits the required logging and analysis path. That case concerns: The intended Fabric-based compromise response lacks its analysis dependency. Here the observed distinction is: EMS server certificate is renewed but the Fabric peer still trusts the prior identity. A more directly targeted response is: Validate the renewed EMS certificate and reauthorize affected peers if required.

C:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: The Fabric connector still points to the old management FQDN after the migration. That case concerns: EMS connector destination no longer resolves to the active service. Here the observed distinction is: EMS server certificate is renewed but the Fabric peer still trusts the prior identity. A more directly targeted response is: Validate the renewed EMS certificate and reauthorize affected peers if required.

D:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: An endpoint security tag is added to a broad Internet allow rule unintentionally affecting guests. That case concerns: Fabric-derived tags were reused without limiting target-policy scope. Here the observed distinction is: EMS server certificate is renewed but the Fabric peer still trusts the prior identity. A more directly targeted response is: Validate the renewed EMS certificate and reauthorize affected peers if required.

Question 446

Original fictional FortiClient EMS 7.4 practice case R181-CASE-112 — Healthcare IT planning certificate renewal. Observed evidence: EMS server certificate is renewed but the Fabric peer still trusts the prior identity. After the scoped corrective action, which observation best confirms this specific incident was resolved?

  1. FortiGate reconnects to the expected EMS instance without disabling checks.
  2. Only managed eligible devices gain access to the specified service.
  3. A controlled test event reaches the analysis workflow and the intended recipient.
  4. Authorized connectors report healthy trust after the rollover.

Explanation

Correct Answer

D:

This is the case-specific acceptance evidence after taking the targeted step: Validate the renewed EMS certificate and reauthorize affected peers if required. The initial signal was: EMS server certificate is renewed but the Fabric peer still trusts the prior identity. A generic online indication alone would not prove this particular issue was resolved: Connector trust continuity was omitted from certificate maintenance.

Incorrect Answers

A:

Incorrect for this incident. This result would support a different diagnosis: EMS connector destination no longer resolves to the active service; its warning sign is: The Fabric connector still points to the old management FQDN after the migration. The current case instead requires verification that: Authorized connectors report healthy trust after the rollover. That follows remediation of: Connector trust continuity was omitted from certificate maintenance.

B:

Incorrect for this incident. This result would support a different diagnosis: Fabric-derived tags were reused without limiting target-policy scope; its warning sign is: An endpoint security tag is added to a broad Internet allow rule unintentionally affecting guests. The current case instead requires verification that: Authorized connectors report healthy trust after the rollover. That follows remediation of: Connector trust continuity was omitted from certificate maintenance.

C:

Incorrect for this incident. This result would support a different diagnosis: The intended Fabric-based compromise response lacks its analysis dependency; its warning sign is: An IoC response design omits the required logging and analysis path. The current case instead requires verification that: Authorized connectors report healthy trust after the rollover. That follows remediation of: Connector trust continuity was omitted from certificate maintenance.

Question 447

Original fictional FortiClient EMS 7.4 practice case R181-CASE-112 — Healthcare IT planning certificate renewal. Observed evidence: EMS server certificate is renewed but the Fabric peer still trusts the prior identity. Which management, security, or integration failure most directly explains the evidence?

  1. The intended Fabric-based compromise response lacks its analysis dependency.
  2. Fabric-derived tags were reused without limiting target-policy scope.
  3. EMS connector destination no longer resolves to the active service.
  4. Connector trust continuity was omitted from certificate maintenance.

Explanation

Correct Answer

D:

The supplied evidence — EMS server certificate is renewed but the Fabric peer still trusts the prior identity — most directly supports: Connector trust continuity was omitted from certificate maintenance. Confirm the explanation by applying the controlled correction: Validate the renewed EMS certificate and reauthorize affected peers if required; then checking that: Authorized connectors report healthy trust after the rollover. Similar symptoms can have other causes in real deployments.

Incorrect Answers

A:

Incorrect for the stated evidence. This alternative concern better explains a different situation: An IoC response design omits the required logging and analysis path. Here the actual observation — EMS server certificate is renewed but the Fabric peer still trusts the prior identity — most directly indicates: Connector trust continuity was omitted from certificate maintenance. The scoped correction is: Validate the renewed EMS certificate and reauthorize affected peers if required.

B:

Incorrect for the stated evidence. This alternative concern better explains a different situation: An endpoint security tag is added to a broad Internet allow rule unintentionally affecting guests. Here the actual observation — EMS server certificate is renewed but the Fabric peer still trusts the prior identity — most directly indicates: Connector trust continuity was omitted from certificate maintenance. The scoped correction is: Validate the renewed EMS certificate and reauthorize affected peers if required.

C:

Incorrect for the stated evidence. This alternative concern better explains a different situation: The Fabric connector still points to the old management FQDN after the migration. Here the actual observation — EMS server certificate is renewed but the Fabric peer still trusts the prior identity — most directly indicates: Connector trust continuity was omitted from certificate maintenance. The scoped correction is: Validate the renewed EMS certificate and reauthorize affected peers if required.

Question 448

Original fictional FortiClient EMS 7.4 practice case R181-CASE-112 — Healthcare IT planning certificate renewal. Observed evidence: EMS server certificate is renewed but the Fabric peer still trusts the prior identity. Which follow-up operational gate best detects a recurrence of the same failure after recovery?

  1. Add a tested post-change acceptance gate requiring this outcome: Authorized connectors report healthy trust after the rollover. Flag any recurrence of this warning sign: EMS server certificate is renewed but the Fabric peer still trusts the prior identity.
  2. Add a tested post-change acceptance gate requiring this outcome: FortiGate reconnects to the expected EMS instance without disabling checks. Flag any recurrence of this warning sign: The Fabric connector still points to the old management FQDN after the migration.
  3. Add a tested post-change acceptance gate requiring this outcome: Only managed eligible devices gain access to the specified service. Flag any recurrence of this warning sign: An endpoint security tag is added to a broad Internet allow rule unintentionally affecting guests.
  4. Add a tested post-change acceptance gate requiring this outcome: A controlled test event reaches the analysis workflow and the intended recipient. Flag any recurrence of this warning sign: An IoC response design omits the required logging and analysis path.

Explanation

Correct Answer

A:

The preventive gate explicitly checks: Authorized connectors report healthy trust after the rollover, and escalates recurrence of: EMS server certificate is renewed but the Fabric peer still trusts the prior identity. That pair addresses the identified issue: Connector trust continuity was omitted from certificate maintenance. The control is derived from the case recovery evidence, not separately certified by a Fortinet subject-matter expert.

Incorrect Answers

B:

Incorrect for this incident. That acceptance gate guards against a different situation: The Fabric connector still points to the old management FQDN after the migration. The current failure to watch for is: EMS server certificate is renewed but the Fabric peer still trusts the prior identity. Use a monitored gate confirming: Authorized connectors report healthy trust after the rollover.

C:

Incorrect for this incident. That acceptance gate guards against a different situation: An endpoint security tag is added to a broad Internet allow rule unintentionally affecting guests. The current failure to watch for is: EMS server certificate is renewed but the Fabric peer still trusts the prior identity. Use a monitored gate confirming: Authorized connectors report healthy trust after the rollover.

D:

Incorrect for this incident. That acceptance gate guards against a different situation: An IoC response design omits the required logging and analysis path. The current failure to watch for is: EMS server certificate is renewed but the Fabric peer still trusts the prior identity. Use a monitored gate confirming: Authorized connectors report healthy trust after the rollover.

Question 449

Original fictional FortiClient EMS 7.4 practice case R181-CASE-113 — Government agency reviewing guest network access. Observed evidence: An endpoint security tag is added to a broad Internet allow rule unintentionally affecting guests. Which focused administrator action best resolves the identified problem while preserving unrelated security controls?

  1. Verify authorized Fabric connectivity and inspect tag ingestion on both devices.
  2. Restrict tag-based policy application to the designated protected resources.
  3. Replace shared connector access with the supported per-peer authorized relationship.
  4. Replace the static endpoint address dependency with approved dynamic posture tag consumption.

Explanation

Correct Answer

B:

Correct for this fictional case. The distinguishing signal is: An endpoint security tag is added to a broad Internet allow rule unintentionally affecting guests. It points to: Fabric-derived tags were reused without limiting target-policy scope. The targeted correction is: Restrict tag-based policy application to the designated protected resources. Verify success by checking: Only managed eligible devices gain access to the specified service. The response is scoped to this observed failure and should not weaken other policies.

Incorrect Answers

A:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: EMS displays the compliant tag but FortiGate shows no corresponding dynamic address object. That case concerns: EMS tagging and FortiGate synchronization are not completing. Here the observed distinction is: An endpoint security tag is added to a broad Internet allow rule unintentionally affecting guests. A more directly targeted response is: Restrict tag-based policy application to the designated protected resources.

C:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: Another FortiGate is mistakenly trusted using credentials intended for a separate device. That case concerns: Shared integration credentials undermine peer-specific audit and revocation. Here the observed distinction is: An endpoint security tag is added to a broad Internet allow rule unintentionally affecting guests. A more directly targeted response is: Restrict tag-based policy application to the designated protected resources.

D:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: A DHCP-renewed laptop keeps its old static firewall entry despite changing posture. That case concerns: The access policy relies on fixed IP objects rather than dynamic EMS-synced identity. Here the observed distinction is: An endpoint security tag is added to a broad Internet allow rule unintentionally affecting guests. A more directly targeted response is: Restrict tag-based policy application to the designated protected resources.

Question 450

Original fictional FortiClient EMS 7.4 practice case R181-CASE-113 — Government agency reviewing guest network access. Observed evidence: An endpoint security tag is added to a broad Internet allow rule unintentionally affecting guests. After the scoped corrective action, which observation best confirms this specific incident was resolved?

  1. EMS identifies and can revoke only the targeted Fabric peer.
  2. Only managed eligible devices gain access to the specified service.
  3. The tagged test endpoint appears in the FortiGate dynamic policy object.
  4. The tagged device follows the intended policy after its address changes.

Explanation

Correct Answer

B:

This is the case-specific acceptance evidence after taking the targeted step: Restrict tag-based policy application to the designated protected resources. The initial signal was: An endpoint security tag is added to a broad Internet allow rule unintentionally affecting guests. A generic online indication alone would not prove this particular issue was resolved: Fabric-derived tags were reused without limiting target-policy scope.

Incorrect Answers

A:

Incorrect for this incident. This result would support a different diagnosis: Shared integration credentials undermine peer-specific audit and revocation; its warning sign is: Another FortiGate is mistakenly trusted using credentials intended for a separate device. The current case instead requires verification that: Only managed eligible devices gain access to the specified service. That follows remediation of: Fabric-derived tags were reused without limiting target-policy scope.

C:

Incorrect for this incident. This result would support a different diagnosis: EMS tagging and FortiGate synchronization are not completing; its warning sign is: EMS displays the compliant tag but FortiGate shows no corresponding dynamic address object. The current case instead requires verification that: Only managed eligible devices gain access to the specified service. That follows remediation of: Fabric-derived tags were reused without limiting target-policy scope.

D:

Incorrect for this incident. This result would support a different diagnosis: The access policy relies on fixed IP objects rather than dynamic EMS-synced identity; its warning sign is: A DHCP-renewed laptop keeps its old static firewall entry despite changing posture. The current case instead requires verification that: Only managed eligible devices gain access to the specified service. That follows remediation of: Fabric-derived tags were reused without limiting target-policy scope.

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