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 41

Question 400

Original fictional FortiClient EMS 7.4 practice case R181-CASE-100 — Nonprofit planning protection updates. Observed evidence: All endpoints receive an untested security configuration change at the same time. 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: The incident log records the disposition and confirmed endpoint status. Flag any recurrence of this warning sign: An endpoint alert is visible but the case owner closes it without inspecting event details.
  2. Add a tested post-change acceptance gate requiring this outcome: A pilot endpoint reports active antivirus protection and the intended configuration. Flag any recurrence of this warning sign: EMS lists several endpoints as managed but their required antivirus protection is not active.
  3. Add a tested post-change acceptance gate requiring this outcome: The pilot shows successful updates and no unacceptable business impact. Flag any recurrence of this warning sign: All endpoints receive an untested security configuration change at the same time.
  4. Add a tested post-change acceptance gate requiring this outcome: A controlled test reaches the security team with the relevant endpoint identifier. Flag any recurrence of this warning sign: A test malicious file generates a detection but the device owner receives no required notification.

Explanation

Correct Answer

C:

The preventive gate explicitly checks: The pilot shows successful updates and no unacceptable business impact, and escalates recurrence of: All endpoints receive an untested security configuration change at the same time. That pair addresses the identified issue: Endpoint security changes lack staged validation and rollback readiness. 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: An endpoint alert is visible but the case owner closes it without inspecting event details. The current failure to watch for is: All endpoints receive an untested security configuration change at the same time. Use a monitored gate confirming: The pilot shows successful updates and no unacceptable business impact.

B:

Incorrect for this incident. That acceptance gate guards against a different situation: EMS lists several endpoints as managed but their required antivirus protection is not active. The current failure to watch for is: All endpoints receive an untested security configuration change at the same time. Use a monitored gate confirming: The pilot shows successful updates and no unacceptable business impact.

D:

Incorrect for this incident. That acceptance gate guards against a different situation: A test malicious file generates a detection but the device owner receives no required notification. The current failure to watch for is: All endpoints receive an untested security configuration change at the same time. Use a monitored gate confirming: The pilot shows successful updates and no unacceptable business impact.

Question 401

Original fictional FortiClient EMS 7.4 practice case R181-CASE-101 — Bank onboarding a new FortiGate. Observed evidence: The firewall has an EMS connector entry but has not completed mutual authorization. Which focused administrator action best resolves the identified problem while preserving unrelated security controls?

  1. Validate the renewed EMS certificate and reauthorize affected peers if required.
  2. Repair routing and narrowly permit the documented EMS connector service.
  3. Import supported EMS security posture tags through the Fabric connector and bind scoped policies.
  4. Approve the FortiGate connection in EMS and verify the permitted FortiOS-side authorization.

Explanation

Correct Answer

D:

Correct for this fictional case. The distinguishing signal is: The firewall has an EMS connector entry but has not completed mutual authorization. It points to: Connector configuration alone does not establish trusted Fabric integration. The targeted correction is: Approve the FortiGate connection in EMS and verify the permitted FortiOS-side authorization. Verify success by checking: The connector is authorized and expected posture tags appear on FortiGate. 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 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: The firewall has an EMS connector entry but has not completed mutual authorization. A more directly targeted response is: Approve the FortiGate connection in EMS and verify the permitted FortiOS-side authorization.

B:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: A FortiGate in the branch has no route or firewall allowance toward EMS Fabric services. That case concerns: The required FortiGate-to-EMS management session cannot reach its destination. Here the observed distinction is: The firewall has an EMS connector entry but has not completed mutual authorization. A more directly targeted response is: Approve the FortiGate connection in EMS and verify the permitted FortiOS-side authorization.

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: The firewall has an EMS connector entry but has not completed mutual authorization. A more directly targeted response is: Approve the FortiGate connection in EMS and verify the permitted FortiOS-side authorization.

Question 402

Original fictional FortiClient EMS 7.4 practice case R181-CASE-101 — Bank onboarding a new FortiGate. Observed evidence: The firewall has an EMS connector entry but has not completed mutual authorization. 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. The branch firewall connects and receives the expected dynamic tags.
  3. Authorized connectors report healthy trust after the rollover.
  4. FortiGate dynamic objects update as test endpoint posture changes.

Explanation

Correct Answer

A:

This is the case-specific acceptance evidence after taking the targeted step: Approve the FortiGate connection in EMS and verify the permitted FortiOS-side authorization. The initial signal was: The firewall has an EMS connector entry but has not completed mutual authorization. A generic online indication alone would not prove this particular issue was resolved: Connector configuration alone does not establish trusted Fabric integration.

Incorrect Answers

B:

Incorrect for this incident. This result would support a different diagnosis: The required FortiGate-to-EMS management session cannot reach its destination; its warning sign is: A FortiGate in the branch has no route or firewall allowance toward EMS Fabric services. The current case instead requires verification that: The connector is authorized and expected posture tags appear on FortiGate. That follows remediation of: Connector configuration alone does not establish trusted Fabric integration.

C:

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: The connector is authorized and expected posture tags appear on FortiGate. That follows remediation of: Connector configuration alone does not establish trusted Fabric integration.

D:

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: The connector is authorized and expected posture tags appear on FortiGate. That follows remediation of: Connector configuration alone does not establish trusted Fabric integration.

Question 403

Original fictional FortiClient EMS 7.4 practice case R181-CASE-101 — Bank onboarding a new FortiGate. Observed evidence: The firewall has an EMS connector entry but has not completed mutual authorization. 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. Connector configuration alone does not establish trusted Fabric integration.
  4. The required FortiGate-to-EMS management session cannot reach its destination.

Explanation

Correct Answer

C:

The supplied evidence — The firewall has an EMS connector entry but has not completed mutual authorization — most directly supports: Connector configuration alone does not establish trusted Fabric integration. Confirm the explanation by applying the controlled correction: Approve the FortiGate connection in EMS and verify the permitted FortiOS-side authorization; then checking that: The connector is authorized and expected posture tags appear on FortiGate. 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 — The firewall has an EMS connector entry but has not completed mutual authorization — most directly indicates: Connector configuration alone does not establish trusted Fabric integration. The scoped correction is: Approve the FortiGate connection in EMS and verify the permitted FortiOS-side authorization.

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 — The firewall has an EMS connector entry but has not completed mutual authorization — most directly indicates: Connector configuration alone does not establish trusted Fabric integration. The scoped correction is: Approve the FortiGate connection in EMS and verify the permitted FortiOS-side authorization.

D:

Incorrect for the stated evidence. This alternative concern better explains a different situation: A FortiGate in the branch has no route or firewall allowance toward EMS Fabric services. Here the actual observation — The firewall has an EMS connector entry but has not completed mutual authorization — most directly indicates: Connector configuration alone does not establish trusted Fabric integration. The scoped correction is: Approve the FortiGate connection in EMS and verify the permitted FortiOS-side authorization.

Question 404

Original fictional FortiClient EMS 7.4 practice case R181-CASE-101 — Bank onboarding a new FortiGate. Observed evidence: The firewall has an EMS connector entry but has not completed mutual authorization. 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: 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.
  2. 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.
  3. 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.
  4. Add a tested post-change acceptance gate requiring this outcome: The branch firewall connects and receives the expected dynamic tags. Flag any recurrence of this warning sign: A FortiGate in the branch has no route or firewall allowance toward EMS Fabric services.

Explanation

Correct Answer

A:

The preventive gate explicitly checks: The connector is authorized and expected posture tags appear on FortiGate, and escalates recurrence of: The firewall has an EMS connector entry but has not completed mutual authorization. That pair addresses the identified issue: Connector configuration alone does not establish trusted Fabric integration. 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 server certificate is renewed but the Fabric peer still trusts the prior identity. The current failure to watch for is: The firewall has an EMS connector entry but has not completed mutual authorization. Use a monitored gate confirming: The connector is authorized and expected posture tags appear on FortiGate.

C:

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: The firewall has an EMS connector entry but has not completed mutual authorization. Use a monitored gate confirming: The connector is authorized and expected posture tags appear on FortiGate.

D:

Incorrect for this incident. That acceptance gate guards against a different situation: A FortiGate in the branch has no route or firewall allowance toward EMS Fabric services. The current failure to watch for is: The firewall has an EMS connector entry but has not completed mutual authorization. Use a monitored gate confirming: The connector is authorized and expected posture tags appear on FortiGate.

Question 405

Original fictional FortiClient EMS 7.4 practice case R181-CASE-102 — Public hospital creating dynamic access rules. Observed evidence: FortiGate policies reference a manually maintained list of client IPs instead of EMS posture tags. Which focused administrator action best resolves the identified problem while preserving unrelated security controls?

  1. Import supported EMS security posture tags through the Fabric connector and bind scoped policies.
  2. Correct the connector target and revalidate its trust relationship.
  3. Verify EMS tag rule evaluation and synchronization freshness on FortiGate.
  4. Restrict tag-based policy application to the designated protected resources.

Explanation

Correct Answer

A:

Correct for this fictional case. The distinguishing signal is: FortiGate policies reference a manually maintained list of client IPs instead of EMS posture tags. It points to: Static address rules cannot reflect changing endpoint security attributes. The targeted correction is: Import supported EMS security posture tags through the Fabric connector and bind scoped policies. Verify success by checking: FortiGate dynamic objects update as test endpoint posture changes. 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: 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: FortiGate policies reference a manually maintained list of client IPs instead of EMS posture tags. A more directly targeted response is: Import supported EMS security posture tags through the Fabric connector and bind scoped policies.

C:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: A test laptop remains tagged trusted on FortiGate after it stops meeting EMS security requirements. That case concerns: The downstream policy uses stale or unsynchronized posture data. Here the observed distinction is: FortiGate policies reference a manually maintained list of client IPs instead of EMS posture tags. A more directly targeted response is: Import supported EMS security posture tags through the Fabric connector and bind scoped policies.

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: FortiGate policies reference a manually maintained list of client IPs instead of EMS posture tags. A more directly targeted response is: Import supported EMS security posture tags through the Fabric connector and bind scoped policies.

Question 406

Original fictional FortiClient EMS 7.4 practice case R181-CASE-102 — Public hospital creating dynamic access rules. Observed evidence: FortiGate policies reference a manually maintained list of client IPs instead of EMS posture tags. 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. A posture change updates the FortiGate tag and the access decision.
  3. FortiGate dynamic objects update as test endpoint posture changes.
  4. Only managed eligible devices gain access to the specified service.

Explanation

Correct Answer

C:

This is the case-specific acceptance evidence after taking the targeted step: Import supported EMS security posture tags through the Fabric connector and bind scoped policies. The initial signal was: FortiGate policies reference a manually maintained list of client IPs instead of EMS posture tags. A generic online indication alone would not prove this particular issue was resolved: Static address rules cannot reflect changing endpoint security attributes.

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: FortiGate dynamic objects update as test endpoint posture changes. That follows remediation of: Static address rules cannot reflect changing endpoint security attributes.

B:

Incorrect for this incident. This result would support a different diagnosis: The downstream policy uses stale or unsynchronized posture data; its warning sign is: A test laptop remains tagged trusted on FortiGate after it stops meeting EMS security requirements. The current case instead requires verification that: FortiGate dynamic objects update as test endpoint posture changes. That follows remediation of: Static address rules cannot reflect changing endpoint security attributes.

D:

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: FortiGate dynamic objects update as test endpoint posture changes. That follows remediation of: Static address rules cannot reflect changing endpoint security attributes.

Question 407

Original fictional FortiClient EMS 7.4 practice case R181-CASE-102 — Public hospital creating dynamic access rules. Observed evidence: FortiGate policies reference a manually maintained list of client IPs instead of EMS posture tags. Which management, security, or integration failure most directly explains the evidence?

  1. Static address rules cannot reflect changing endpoint security attributes.
  2. The downstream policy uses stale or unsynchronized posture data.
  3. Fabric-derived tags were reused without limiting target-policy scope.
  4. EMS connector destination no longer resolves to the active service.

Explanation

Correct Answer

A:

The supplied evidence — FortiGate policies reference a manually maintained list of client IPs instead of EMS posture tags — most directly supports: Static address rules cannot reflect changing endpoint security attributes. Confirm the explanation by applying the controlled correction: Import supported EMS security posture tags through the Fabric connector and bind scoped policies; then checking that: FortiGate dynamic objects update as test endpoint posture changes. 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: A test laptop remains tagged trusted on FortiGate after it stops meeting EMS security requirements. Here the actual observation — FortiGate policies reference a manually maintained list of client IPs instead of EMS posture tags — most directly indicates: Static address rules cannot reflect changing endpoint security attributes. The scoped correction is: Import supported EMS security posture tags through the Fabric connector and bind scoped policies.

C:

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 — FortiGate policies reference a manually maintained list of client IPs instead of EMS posture tags — most directly indicates: Static address rules cannot reflect changing endpoint security attributes. The scoped correction is: Import supported EMS security posture tags through the Fabric connector and bind scoped policies.

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 — FortiGate policies reference a manually maintained list of client IPs instead of EMS posture tags — most directly indicates: Static address rules cannot reflect changing endpoint security attributes. The scoped correction is: Import supported EMS security posture tags through the Fabric connector and bind scoped policies.

Question 408

Original fictional FortiClient EMS 7.4 practice case R181-CASE-102 — Public hospital creating dynamic access rules. Observed evidence: FortiGate policies reference a manually maintained list of client IPs instead of EMS posture tags. 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 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.
  2. Add a tested post-change acceptance gate requiring this outcome: A posture change updates the FortiGate tag and the access decision. Flag any recurrence of this warning sign: A test laptop remains tagged trusted on FortiGate after it stops meeting EMS security requirements.
  3. 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.
  4. 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.

Explanation

Correct Answer

A:

The preventive gate explicitly checks: FortiGate dynamic objects update as test endpoint posture changes, and escalates recurrence of: FortiGate policies reference a manually maintained list of client IPs instead of EMS posture tags. That pair addresses the identified issue: Static address rules cannot reflect changing endpoint security attributes. 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 test laptop remains tagged trusted on FortiGate after it stops meeting EMS security requirements. The current failure to watch for is: FortiGate policies reference a manually maintained list of client IPs instead of EMS posture tags. Use a monitored gate confirming: FortiGate dynamic objects update as test endpoint posture changes.

C:

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: FortiGate policies reference a manually maintained list of client IPs instead of EMS posture tags. Use a monitored gate confirming: FortiGate dynamic objects update as test endpoint posture changes.

D:

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: FortiGate policies reference a manually maintained list of client IPs instead of EMS posture tags. Use a monitored gate confirming: FortiGate dynamic objects update as test endpoint posture changes.

Question 409

Original fictional FortiClient EMS 7.4 practice case R181-CASE-103 — Retail branch rotating the EMS hostname. Observed evidence: The Fabric connector still points to the old management FQDN after the migration. Which focused administrator action best resolves the identified problem while preserving unrelated security controls?

  1. Require reviewed connector registration and least-privilege authorization.
  2. Replace the static endpoint address dependency with approved dynamic posture tag consumption.
  3. Correct the connector target and revalidate its trust relationship.
  4. Verify authorized Fabric connectivity and inspect tag ingestion on both devices.

Explanation

Correct Answer

C:

Correct for this fictional case. The distinguishing signal is: The Fabric connector still points to the old management FQDN after the migration. It points to: EMS connector destination no longer resolves to the active service. The targeted correction is: Correct the connector target and revalidate its trust relationship. Verify success by checking: FortiGate reconnects to the expected EMS instance without disabling checks. 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: Multiple administrators can independently authorize unknown FortiGates to EMS. That case concerns: Fabric registration workflow lacks peer approval and change control. Here the observed distinction is: The Fabric connector still points to the old management FQDN after the migration. A more directly targeted response is: Correct the connector target and revalidate its trust relationship.

B:

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: The Fabric connector still points to the old management FQDN after the migration. A more directly targeted response is: Correct the connector target and revalidate its trust relationship.

D:

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: The Fabric connector still points to the old management FQDN after the migration. A more directly targeted response is: Correct the connector target and revalidate its trust relationship.

Question 410

Original fictional FortiClient EMS 7.4 practice case R181-CASE-103 — Retail branch rotating the EMS hostname. Observed evidence: The Fabric connector still points to the old management FQDN after the migration. After the scoped corrective action, which observation best confirms this specific incident was resolved?

  1. The tagged device follows the intended policy after its address changes.
  2. FortiGate reconnects to the expected EMS instance without disabling checks.
  3. The tagged test endpoint appears in the FortiGate dynamic policy object.
  4. Only the explicitly approved firewall joins EMS Fabric devices.

Explanation

Correct Answer

B:

This is the case-specific acceptance evidence after taking the targeted step: Correct the connector target and revalidate its trust relationship. The initial signal was: The Fabric connector still points to the old management FQDN after the migration. A generic online indication alone would not prove this particular issue was resolved: EMS connector destination no longer resolves to the active service.

Incorrect Answers

A:

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: FortiGate reconnects to the expected EMS instance without disabling checks. That follows remediation of: EMS connector destination no longer resolves to the active service.

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: FortiGate reconnects to the expected EMS instance without disabling checks. That follows remediation of: EMS connector destination no longer resolves to the active service.

D:

Incorrect for this incident. This result would support a different diagnosis: Fabric registration workflow lacks peer approval and change control; its warning sign is: Multiple administrators can independently authorize unknown FortiGates to EMS. The current case instead requires verification that: FortiGate reconnects to the expected EMS instance without disabling checks. That follows remediation of: EMS connector destination no longer resolves to the active service.

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