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 48

Question 470

Original fictional FortiClient EMS 7.4 practice case R181-CASE-118 — Consultancy validating shared certificates. Observed evidence: Another FortiGate is mistakenly trusted using credentials intended for a separate device. After the scoped corrective action, which observation best confirms this specific incident was resolved?

  1. Only endpoints meeting the required posture are included in the rule.
  2. Both authorized firewalls display the correct test posture tags.
  3. EMS identifies and can revoke only the targeted Fabric peer.
  4. FortiGate reconnects to the expected EMS instance without disabling checks.

Explanation

Correct Answer

C:

This is the case-specific acceptance evidence after taking the targeted step: Replace shared connector access with the supported per-peer authorized relationship. The initial signal was: Another FortiGate is mistakenly trusted using credentials intended for a separate device. A generic online indication alone would not prove this particular issue was resolved: Shared integration credentials undermine peer-specific audit and revocation.

Incorrect Answers

A:

Incorrect for this incident. This result would support a different diagnosis: The policy is not bound to the specific security posture condition; its warning sign is: A firewall policy grants access based solely on the existence of any EMS tag without checking the correct compliance tag. The current case instead requires verification that: EMS identifies and can revoke only the targeted Fabric peer. That follows remediation of: Shared integration credentials undermine peer-specific audit and revocation.

B:

Incorrect for this incident. This result would support a different diagnosis: Fabric pairing is per authorized peer and was not completed for the second device; its warning sign is: Tags work on headquarters firewall but not on the new regional firewall. The current case instead requires verification that: EMS identifies and can revoke only the targeted Fabric peer. That follows remediation of: Shared integration credentials undermine peer-specific audit and revocation.

D:

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: EMS identifies and can revoke only the targeted Fabric peer. That follows remediation of: Shared integration credentials undermine peer-specific audit and revocation.

Question 471

Original fictional FortiClient EMS 7.4 practice case R181-CASE-118 — Consultancy validating shared certificates. Observed evidence: Another FortiGate is mistakenly trusted using credentials intended for a separate device. Which management, security, or integration failure most directly explains the evidence?

  1. The policy is not bound to the specific security posture condition.
  2. Shared integration credentials undermine peer-specific audit and revocation.
  3. Fabric pairing is per authorized peer and was not completed for the second device.
  4. EMS connector destination no longer resolves to the active service.

Explanation

Correct Answer

B:

The supplied evidence — Another FortiGate is mistakenly trusted using credentials intended for a separate device — most directly supports: Shared integration credentials undermine peer-specific audit and revocation. Confirm the explanation by applying the controlled correction: Replace shared connector access with the supported per-peer authorized relationship; then checking that: EMS identifies and can revoke only the targeted Fabric peer. 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: A firewall policy grants access based solely on the existence of any EMS tag without checking the correct compliance tag. Here the actual observation — Another FortiGate is mistakenly trusted using credentials intended for a separate device — most directly indicates: Shared integration credentials undermine peer-specific audit and revocation. The scoped correction is: Replace shared connector access with the supported per-peer authorized relationship.

C:

Incorrect for the stated evidence. This alternative concern better explains a different situation: Tags work on headquarters firewall but not on the new regional firewall. Here the actual observation — Another FortiGate is mistakenly trusted using credentials intended for a separate device — most directly indicates: Shared integration credentials undermine peer-specific audit and revocation. The scoped correction is: Replace shared connector access with the supported per-peer authorized relationship.

D:

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 — Another FortiGate is mistakenly trusted using credentials intended for a separate device — most directly indicates: Shared integration credentials undermine peer-specific audit and revocation. The scoped correction is: Replace shared connector access with the supported per-peer authorized relationship.

Question 472

Original fictional FortiClient EMS 7.4 practice case R181-CASE-118 — Consultancy validating shared certificates. Observed evidence: Another FortiGate is mistakenly trusted using credentials intended for a separate device. 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: 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.
  2. Add a tested post-change acceptance gate requiring this outcome: Only endpoints meeting the required posture are included in the rule. Flag any recurrence of this warning sign: A firewall policy grants access based solely on the existence of any EMS tag without checking the correct compliance tag.
  3. Add a tested post-change acceptance gate requiring this outcome: EMS identifies and can revoke only the targeted Fabric peer. Flag any recurrence of this warning sign: Another FortiGate is mistakenly trusted using credentials intended for a separate device.
  4. Add a tested post-change acceptance gate requiring this outcome: Both authorized firewalls display the correct test posture tags. Flag any recurrence of this warning sign: Tags work on headquarters firewall but not on the new regional firewall.

Explanation

Correct Answer

C:

The preventive gate explicitly checks: EMS identifies and can revoke only the targeted Fabric peer, and escalates recurrence of: Another FortiGate is mistakenly trusted using credentials intended for a separate device. That pair addresses the identified issue: Shared integration credentials undermine peer-specific audit and revocation. The control is derived from the case recovery evidence, not separately certified by a Fortinet subject-matter expert.

Incorrect Answers

A:

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: Another FortiGate is mistakenly trusted using credentials intended for a separate device. Use a monitored gate confirming: EMS identifies and can revoke only the targeted Fabric peer.

B:

Incorrect for this incident. That acceptance gate guards against a different situation: A firewall policy grants access based solely on the existence of any EMS tag without checking the correct compliance tag. The current failure to watch for is: Another FortiGate is mistakenly trusted using credentials intended for a separate device. Use a monitored gate confirming: EMS identifies and can revoke only the targeted Fabric peer.

D:

Incorrect for this incident. That acceptance gate guards against a different situation: Tags work on headquarters firewall but not on the new regional firewall. The current failure to watch for is: Another FortiGate is mistakenly trusted using credentials intended for a separate device. Use a monitored gate confirming: EMS identifies and can revoke only the targeted Fabric peer.

Question 473

Original fictional FortiClient EMS 7.4 practice case R181-CASE-119 — School district onboarding endpoints. Observed evidence: A firewall policy grants access based solely on the existence of any EMS tag without checking the correct compliance tag. 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. Isolate and repair the FortiGate-to-EMS connector failure.
  3. Select the intended compliance tag and verify its assignment rules.
  4. Rebind the authorized new Fabric connector and verify policy object synchronization.

Explanation

Correct Answer

C:

Correct for this fictional case. The distinguishing signal is: A firewall policy grants access based solely on the existence of any EMS tag without checking the correct compliance tag. It points to: The policy is not bound to the specific security posture condition. The targeted correction is: Select the intended compliance tag and verify its assignment rules. Verify success by checking: Only endpoints meeting the required posture are included in the rule. 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: A firewall policy grants access based solely on the existence of any EMS tag without checking the correct compliance tag. A more directly targeted response is: Select the intended compliance tag and verify its assignment rules.

B:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: The team troubleshoots endpoint agents before checking the known failed EMS Fabric session. That case concerns: Endpoint telemetry health and Fabric connector health are different integration paths. Here the observed distinction is: A firewall policy grants access based solely on the existence of any EMS tag without checking the correct compliance tag. A more directly targeted response is: Select the intended compliance tag and verify its assignment rules.

D:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: Old dynamic address objects remain on FortiGate after moving to a new EMS management instance. That case concerns: The connector and policy still reference stale EMS-generated objects. Here the observed distinction is: A firewall policy grants access based solely on the existence of any EMS tag without checking the correct compliance tag. A more directly targeted response is: Select the intended compliance tag and verify its assignment rules.

Question 474

Original fictional FortiClient EMS 7.4 practice case R181-CASE-119 — School district onboarding endpoints. Observed evidence: A firewall policy grants access based solely on the existence of any EMS tag without checking the correct compliance tag. After the scoped corrective action, which observation best confirms this specific incident was resolved?

  1. The tagged test endpoint appears in the FortiGate dynamic policy object.
  2. EMS endpoint registrations stay healthy and FortiGate tag sync recovers.
  3. Only endpoints meeting the required posture are included in the rule.
  4. New and changed endpoint posture is represented correctly without obsolete objects.

Explanation

Correct Answer

C:

This is the case-specific acceptance evidence after taking the targeted step: Select the intended compliance tag and verify its assignment rules. The initial signal was: A firewall policy grants access based solely on the existence of any EMS tag without checking the correct compliance tag. A generic online indication alone would not prove this particular issue was resolved: The policy is not bound to the specific security posture condition.

Incorrect Answers

A:

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 endpoints meeting the required posture are included in the rule. That follows remediation of: The policy is not bound to the specific security posture condition.

B:

Incorrect for this incident. This result would support a different diagnosis: Endpoint telemetry health and Fabric connector health are different integration paths; its warning sign is: The team troubleshoots endpoint agents before checking the known failed EMS Fabric session. The current case instead requires verification that: Only endpoints meeting the required posture are included in the rule. That follows remediation of: The policy is not bound to the specific security posture condition.

D:

Incorrect for this incident. This result would support a different diagnosis: The connector and policy still reference stale EMS-generated objects; its warning sign is: Old dynamic address objects remain on FortiGate after moving to a new EMS management instance. The current case instead requires verification that: Only endpoints meeting the required posture are included in the rule. That follows remediation of: The policy is not bound to the specific security posture condition.

Question 475

Original fictional FortiClient EMS 7.4 practice case R181-CASE-119 — School district onboarding endpoints. Observed evidence: A firewall policy grants access based solely on the existence of any EMS tag without checking the correct compliance tag. Which management, security, or integration failure most directly explains the evidence?

  1. Endpoint telemetry health and Fabric connector health are different integration paths.
  2. The connector and policy still reference stale EMS-generated objects.
  3. EMS tagging and FortiGate synchronization are not completing.
  4. The policy is not bound to the specific security posture condition.

Explanation

Correct Answer

D:

The supplied evidence — A firewall policy grants access based solely on the existence of any EMS tag without checking the correct compliance tag — most directly supports: The policy is not bound to the specific security posture condition. Confirm the explanation by applying the controlled correction: Select the intended compliance tag and verify its assignment rules; then checking that: Only endpoints meeting the required posture are included in the rule. 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: The team troubleshoots endpoint agents before checking the known failed EMS Fabric session. Here the actual observation — A firewall policy grants access based solely on the existence of any EMS tag without checking the correct compliance tag — most directly indicates: The policy is not bound to the specific security posture condition. The scoped correction is: Select the intended compliance tag and verify its assignment rules.

B:

Incorrect for the stated evidence. This alternative concern better explains a different situation: Old dynamic address objects remain on FortiGate after moving to a new EMS management instance. Here the actual observation — A firewall policy grants access based solely on the existence of any EMS tag without checking the correct compliance tag — most directly indicates: The policy is not bound to the specific security posture condition. The scoped correction is: Select the intended compliance tag and verify its assignment rules.

C:

Incorrect for the stated evidence. This alternative concern better explains a different situation: EMS displays the compliant tag but FortiGate shows no corresponding dynamic address object. Here the actual observation — A firewall policy grants access based solely on the existence of any EMS tag without checking the correct compliance tag — most directly indicates: The policy is not bound to the specific security posture condition. The scoped correction is: Select the intended compliance tag and verify its assignment rules.

Question 476

Original fictional FortiClient EMS 7.4 practice case R181-CASE-119 — School district onboarding endpoints. Observed evidence: A firewall policy grants access based solely on the existence of any EMS tag without checking the correct compliance tag. 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: New and changed endpoint posture is represented correctly without obsolete objects. Flag any recurrence of this warning sign: Old dynamic address objects remain on FortiGate after moving to a new EMS management instance.
  2. Add a tested post-change acceptance gate requiring this outcome: Only endpoints meeting the required posture are included in the rule. Flag any recurrence of this warning sign: A firewall policy grants access based solely on the existence of any EMS tag without checking the correct compliance tag.
  3. Add a tested post-change acceptance gate requiring this outcome: The tagged test endpoint appears in the FortiGate dynamic policy object. Flag any recurrence of this warning sign: EMS displays the compliant tag but FortiGate shows no corresponding dynamic address object.
  4. 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.

Explanation

Correct Answer

B:

The preventive gate explicitly checks: Only endpoints meeting the required posture are included in the rule, and escalates recurrence of: A firewall policy grants access based solely on the existence of any EMS tag without checking the correct compliance tag. That pair addresses the identified issue: The policy is not bound to the specific security posture condition. The control is derived from the case recovery evidence, not separately certified by a Fortinet subject-matter expert.

Incorrect Answers

A:

Incorrect for this incident. That acceptance gate guards against a different situation: Old dynamic address objects remain on FortiGate after moving to a new EMS management instance. The current failure to watch for is: A firewall policy grants access based solely on the existence of any EMS tag without checking the correct compliance tag. Use a monitored gate confirming: Only endpoints meeting the required posture are included in the rule.

C:

Incorrect for this incident. That acceptance gate guards against a different situation: EMS displays the compliant tag but FortiGate shows no corresponding dynamic address object. The current failure to watch for is: A firewall policy grants access based solely on the existence of any EMS tag without checking the correct compliance tag. Use a monitored gate confirming: Only endpoints meeting the required posture are included in the rule.

D:

Incorrect for this incident. That acceptance gate guards against a different situation: The team troubleshoots endpoint agents before checking the known failed EMS Fabric session. The current failure to watch for is: A firewall policy grants access based solely on the existence of any EMS tag without checking the correct compliance tag. Use a monitored gate confirming: Only endpoints meeting the required posture are included in the rule.

Question 477

Original fictional FortiClient EMS 7.4 practice case R181-CASE-120 — E-commerce company migrating EMS. Observed evidence: Old dynamic address objects remain on FortiGate after moving to a new EMS management instance. Which focused administrator action best resolves the identified problem while preserving unrelated security controls?

  1. Approve the FortiGate connection in EMS and verify the permitted FortiOS-side authorization.
  2. Check the EMS certificate and peer identity before reauthorizing the connector.
  3. Rebind the authorized new Fabric connector and verify policy object synchronization.
  4. Correct the policy sequence and scope so the tag-based condition is enforced.

Explanation

Correct Answer

C:

Correct for this fictional case. The distinguishing signal is: Old dynamic address objects remain on FortiGate after moving to a new EMS management instance. It points to: The connector and policy still reference stale EMS-generated objects. The targeted correction is: Rebind the authorized new Fabric connector and verify policy object synchronization. Verify success by checking: New and changed endpoint posture is represented correctly without obsolete objects. 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: The firewall has an EMS connector entry but has not completed mutual authorization. That case concerns: Connector configuration alone does not establish trusted Fabric integration. Here the observed distinction is: Old dynamic address objects remain on FortiGate after moving to a new EMS management instance. A more directly targeted response is: Rebind the authorized new Fabric connector and verify policy object synchronization.

B:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: A connector prompts for acceptance of an unexpected EMS certificate after infrastructure changes. That case concerns: The Fabric peer's certificate identity has not been reconciled against the approved server. Here the observed distinction is: Old dynamic address objects remain on FortiGate after moving to a new EMS management instance. A more directly targeted response is: Rebind the authorized new Fabric connector and verify policy object synchronization.

D:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: A permissive fallback firewall policy shadows the newly created ZTNA tag-based rule. That case concerns: Rule evaluation order prevents the intended posture-based restriction. Here the observed distinction is: Old dynamic address objects remain on FortiGate after moving to a new EMS management instance. A more directly targeted response is: Rebind the authorized new Fabric connector and verify policy object synchronization.

Question 478

Original fictional FortiClient EMS 7.4 practice case R181-CASE-120 — E-commerce company migrating EMS. Observed evidence: Old dynamic address objects remain on FortiGate after moving to a new EMS management instance. After the scoped corrective action, which observation best confirms this specific incident was resolved?

  1. The connector is authorized and expected posture tags appear on FortiGate.
  2. A noncompliant client is denied while a compliant test client is allowed.
  3. Authorization succeeds with the verified trusted certificate and correct EMS hostname.
  4. New and changed endpoint posture is represented correctly without obsolete objects.

Explanation

Correct Answer

D:

This is the case-specific acceptance evidence after taking the targeted step: Rebind the authorized new Fabric connector and verify policy object synchronization. The initial signal was: Old dynamic address objects remain on FortiGate after moving to a new EMS management instance. A generic online indication alone would not prove this particular issue was resolved: The connector and policy still reference stale EMS-generated objects.

Incorrect Answers

A:

Incorrect for this incident. This result would support a different diagnosis: Connector configuration alone does not establish trusted Fabric integration; its warning sign is: The firewall has an EMS connector entry but has not completed mutual authorization. The current case instead requires verification that: New and changed endpoint posture is represented correctly without obsolete objects. That follows remediation of: The connector and policy still reference stale EMS-generated objects.

B:

Incorrect for this incident. This result would support a different diagnosis: Rule evaluation order prevents the intended posture-based restriction; its warning sign is: A permissive fallback firewall policy shadows the newly created ZTNA tag-based rule. The current case instead requires verification that: New and changed endpoint posture is represented correctly without obsolete objects. That follows remediation of: The connector and policy still reference stale EMS-generated objects.

C:

Incorrect for this incident. This result would support a different diagnosis: The Fabric peer's certificate identity has not been reconciled against the approved server; its warning sign is: A connector prompts for acceptance of an unexpected EMS certificate after infrastructure changes. The current case instead requires verification that: New and changed endpoint posture is represented correctly without obsolete objects. That follows remediation of: The connector and policy still reference stale EMS-generated objects.

Question 479

Original fictional FortiClient EMS 7.4 practice case R181-CASE-120 — E-commerce company migrating EMS. Observed evidence: Old dynamic address objects remain on FortiGate after moving to a new EMS management instance. Which management, security, or integration failure most directly explains the evidence?

  1. The connector and policy still reference stale EMS-generated objects.
  2. Connector configuration alone does not establish trusted Fabric integration.
  3. The Fabric peer's certificate identity has not been reconciled against the approved server.
  4. Rule evaluation order prevents the intended posture-based restriction.

Explanation

Correct Answer

A:

The supplied evidence — Old dynamic address objects remain on FortiGate after moving to a new EMS management instance — most directly supports: The connector and policy still reference stale EMS-generated objects. Confirm the explanation by applying the controlled correction: Rebind the authorized new Fabric connector and verify policy object synchronization; then checking that: New and changed endpoint posture is represented correctly without obsolete objects. Similar symptoms can have other causes in real deployments.

Incorrect Answers

B:

Incorrect for the stated evidence. This alternative concern better explains a different situation: The firewall has an EMS connector entry but has not completed mutual authorization. Here the actual observation — Old dynamic address objects remain on FortiGate after moving to a new EMS management instance — most directly indicates: The connector and policy still reference stale EMS-generated objects. The scoped correction is: Rebind the authorized new Fabric connector and verify policy object synchronization.

C:

Incorrect for the stated evidence. This alternative concern better explains a different situation: A connector prompts for acceptance of an unexpected EMS certificate after infrastructure changes. Here the actual observation — Old dynamic address objects remain on FortiGate after moving to a new EMS management instance — most directly indicates: The connector and policy still reference stale EMS-generated objects. The scoped correction is: Rebind the authorized new Fabric connector and verify policy object synchronization.

D:

Incorrect for the stated evidence. This alternative concern better explains a different situation: A permissive fallback firewall policy shadows the newly created ZTNA tag-based rule. Here the actual observation — Old dynamic address objects remain on FortiGate after moving to a new EMS management instance — most directly indicates: The connector and policy still reference stale EMS-generated objects. The scoped correction is: Rebind the authorized new Fabric connector and verify policy object synchronization.

Question 480

Original fictional FortiClient EMS 7.4 practice case R181-CASE-120 — E-commerce company migrating EMS. Observed evidence: Old dynamic address objects remain on FortiGate after moving to a new EMS management instance. 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: New and changed endpoint posture is represented correctly without obsolete objects. Flag any recurrence of this warning sign: Old dynamic address objects remain on FortiGate after moving to a new EMS management instance.
  2. 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.
  3. Add a tested post-change acceptance gate requiring this outcome: Authorization succeeds with the verified trusted certificate and correct EMS hostname. Flag any recurrence of this warning sign: A connector prompts for acceptance of an unexpected EMS certificate after infrastructure changes.
  4. 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.

Explanation

Correct Answer

A:

The preventive gate explicitly checks: New and changed endpoint posture is represented correctly without obsolete objects, and escalates recurrence of: Old dynamic address objects remain on FortiGate after moving to a new EMS management instance. That pair addresses the identified issue: The connector and policy still reference stale EMS-generated objects. 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 firewall has an EMS connector entry but has not completed mutual authorization. The current failure to watch for is: Old dynamic address objects remain on FortiGate after moving to a new EMS management instance. Use a monitored gate confirming: New and changed endpoint posture is represented correctly without obsolete objects.

C:

Incorrect for this incident. That acceptance gate guards against a different situation: A connector prompts for acceptance of an unexpected EMS certificate after infrastructure changes. The current failure to watch for is: Old dynamic address objects remain on FortiGate after moving to a new EMS management instance. Use a monitored gate confirming: New and changed endpoint posture is represented correctly without obsolete objects.

D:

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: Old dynamic address objects remain on FortiGate after moving to a new EMS management instance. Use a monitored gate confirming: New and changed endpoint posture is represented correctly without obsolete objects.

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