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 43

Question 420

Original fictional FortiClient EMS 7.4 practice case R181-CASE-105 — Healthcare group hardening trust. Observed evidence: A connector prompts for acceptance of an unexpected EMS certificate after infrastructure changes. 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: 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.
  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 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.

Explanation

Correct Answer

C:

The preventive gate explicitly checks: Authorization succeeds with the verified trusted certificate and correct EMS hostname, and escalates recurrence of: A connector prompts for acceptance of an unexpected EMS certificate after infrastructure changes. That pair addresses the identified issue: The Fabric peer's certificate identity has not been reconciled against the approved server. 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 team troubleshoots endpoint agents before checking the known failed EMS Fabric session. The current failure to watch for is: A connector prompts for acceptance of an unexpected EMS certificate after infrastructure changes. Use a monitored gate confirming: Authorization succeeds with the verified trusted certificate and correct EMS hostname.

B:

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: A connector prompts for acceptance of an unexpected EMS certificate after infrastructure changes. Use a monitored gate confirming: Authorization succeeds with the verified trusted certificate and correct EMS hostname.

D:

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 connector prompts for acceptance of an unexpected EMS certificate after infrastructure changes. Use a monitored gate confirming: Authorization succeeds with the verified trusted certificate and correct EMS hostname.

Question 421

Original fictional FortiClient EMS 7.4 practice case R181-CASE-106 — Logistics enterprise deploying a new branch. Observed evidence: A FortiGate in the branch has no route or firewall allowance toward EMS Fabric services. Which focused administrator action best resolves the identified problem while preserving unrelated security controls?

  1. Repair routing and narrowly permit the documented EMS connector service.
  2. Verify EMS tag rule evaluation and synchronization freshness on FortiGate.
  3. Configure and test the supported FortiClient and FortiGate logging path to FortiAnalyzer.
  4. Correct the policy sequence and scope so the tag-based condition is enforced.

Explanation

Correct Answer

A:

Correct for this fictional case. The distinguishing signal is: A FortiGate in the branch has no route or firewall allowance toward EMS Fabric services. It points to: The required FortiGate-to-EMS management session cannot reach its destination. The targeted correction is: Repair routing and narrowly permit the documented EMS connector service. Verify success by checking: The branch firewall connects and receives the expected dynamic tags. 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: 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: A FortiGate in the branch has no route or firewall allowance toward EMS Fabric services. A more directly targeted response is: Repair routing and narrowly permit the documented EMS connector service.

C:

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: A FortiGate in the branch has no route or firewall allowance toward EMS Fabric services. A more directly targeted response is: Repair routing and narrowly permit the documented EMS connector service.

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: A FortiGate in the branch has no route or firewall allowance toward EMS Fabric services. A more directly targeted response is: Repair routing and narrowly permit the documented EMS connector service.

Question 422

Original fictional FortiClient EMS 7.4 practice case R181-CASE-106 — Logistics enterprise deploying a new branch. Observed evidence: A FortiGate in the branch has no route or firewall allowance toward EMS Fabric services. After the scoped corrective action, which observation best confirms this specific incident was resolved?

  1. A posture change updates the FortiGate tag and the access decision.
  2. A controlled test event reaches the analysis workflow and the intended recipient.
  3. The branch firewall connects and receives the expected dynamic tags.
  4. A noncompliant client is denied while a compliant test client is allowed.

Explanation

Correct Answer

C:

This is the case-specific acceptance evidence after taking the targeted step: Repair routing and narrowly permit the documented EMS connector service. The initial signal was: A FortiGate in the branch has no route or firewall allowance toward EMS Fabric services. A generic online indication alone would not prove this particular issue was resolved: The required FortiGate-to-EMS management session cannot reach its destination.

Incorrect Answers

A:

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: The branch firewall connects and receives the expected dynamic tags. That follows remediation of: The required FortiGate-to-EMS management session cannot reach its destination.

B:

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: The branch firewall connects and receives the expected dynamic tags. That follows remediation of: The required FortiGate-to-EMS management session cannot reach its destination.

D:

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: The branch firewall connects and receives the expected dynamic tags. That follows remediation of: The required FortiGate-to-EMS management session cannot reach its destination.

Question 423

Original fictional FortiClient EMS 7.4 practice case R181-CASE-106 — Logistics enterprise deploying a new branch. Observed evidence: A FortiGate in the branch has no route or firewall allowance toward EMS Fabric services. Which management, security, or integration failure most directly explains the evidence?

  1. The required FortiGate-to-EMS management session cannot reach its destination.
  2. Rule evaluation order prevents the intended posture-based restriction.
  3. The intended Fabric-based compromise response lacks its analysis dependency.
  4. The downstream policy uses stale or unsynchronized posture data.

Explanation

Correct Answer

A:

The supplied evidence — A FortiGate in the branch has no route or firewall allowance toward EMS Fabric services — most directly supports: The required FortiGate-to-EMS management session cannot reach its destination. Confirm the explanation by applying the controlled correction: Repair routing and narrowly permit the documented EMS connector service; then checking that: The branch firewall connects and receives the expected dynamic tags. 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 permissive fallback firewall policy shadows the newly created ZTNA tag-based rule. Here the actual observation — A FortiGate in the branch has no route or firewall allowance toward EMS Fabric services — most directly indicates: The required FortiGate-to-EMS management session cannot reach its destination. The scoped correction is: Repair routing and narrowly permit the documented EMS connector service.

C:

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 — A FortiGate in the branch has no route or firewall allowance toward EMS Fabric services — most directly indicates: The required FortiGate-to-EMS management session cannot reach its destination. The scoped correction is: Repair routing and narrowly permit the documented EMS connector service.

D:

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 — A FortiGate in the branch has no route or firewall allowance toward EMS Fabric services — most directly indicates: The required FortiGate-to-EMS management session cannot reach its destination. The scoped correction is: Repair routing and narrowly permit the documented EMS connector service.

Question 424

Original fictional FortiClient EMS 7.4 practice case R181-CASE-106 — Logistics enterprise deploying a new branch. Observed evidence: A FortiGate in the branch has no route or firewall allowance toward EMS Fabric services. 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 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.
  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: 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.
  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

C:

The preventive gate explicitly checks: The branch firewall connects and receives the expected dynamic tags, and escalates recurrence of: A FortiGate in the branch has no route or firewall allowance toward EMS Fabric services. That pair addresses the identified issue: The required FortiGate-to-EMS management session cannot reach its destination. 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: A test laptop remains tagged trusted on FortiGate after it stops meeting EMS security requirements. The current failure to watch for is: A FortiGate in the branch has no route or firewall allowance toward EMS Fabric services. Use a monitored gate confirming: The branch firewall connects and receives the expected dynamic tags.

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: A FortiGate in the branch has no route or firewall allowance toward EMS Fabric services. Use a monitored gate confirming: The branch firewall connects and receives the expected dynamic tags.

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: A FortiGate in the branch has no route or firewall allowance toward EMS Fabric services. Use a monitored gate confirming: The branch firewall connects and receives the expected dynamic tags.

Question 425

Original fictional FortiClient EMS 7.4 practice case R181-CASE-107 — Regional insurer reviewing endpoint posture. Observed evidence: A test laptop remains tagged trusted on FortiGate after it stops meeting EMS security requirements. Which focused administrator action best resolves the identified problem while preserving unrelated security controls?

  1. Require reviewed connector registration and least-privilege authorization.
  2. Verify EMS tag rule evaluation and synchronization freshness on FortiGate.
  3. Validate the renewed EMS certificate and reauthorize affected peers if required.
  4. Replace shared connector access with the supported per-peer authorized relationship.

Explanation

Correct Answer

B:

Correct for this fictional case. The distinguishing signal is: A test laptop remains tagged trusted on FortiGate after it stops meeting EMS security requirements. It points to: The downstream policy uses stale or unsynchronized posture data. The targeted correction is: Verify EMS tag rule evaluation and synchronization freshness on FortiGate. Verify success by checking: A posture change updates the FortiGate tag and the access decision. 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: A test laptop remains tagged trusted on FortiGate after it stops meeting EMS security requirements. A more directly targeted response is: Verify EMS tag rule evaluation and synchronization freshness on FortiGate.

C:

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 test laptop remains tagged trusted on FortiGate after it stops meeting EMS security requirements. A more directly targeted response is: Verify EMS tag rule evaluation and synchronization freshness on FortiGate.

D:

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: A test laptop remains tagged trusted on FortiGate after it stops meeting EMS security requirements. A more directly targeted response is: Verify EMS tag rule evaluation and synchronization freshness on FortiGate.

Question 426

Original fictional FortiClient EMS 7.4 practice case R181-CASE-107 — Regional insurer reviewing endpoint posture. Observed evidence: A test laptop remains tagged trusted on FortiGate after it stops meeting EMS security requirements. 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 posture change updates the FortiGate tag and the access decision.
  3. EMS identifies and can revoke only the targeted Fabric peer.
  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: Verify EMS tag rule evaluation and synchronization freshness on FortiGate. The initial signal was: A test laptop remains tagged trusted on FortiGate after it stops meeting EMS security requirements. A generic online indication alone would not prove this particular issue was resolved: The downstream policy uses stale or unsynchronized posture data.

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 posture change updates the FortiGate tag and the access decision. That follows remediation of: The downstream policy uses stale or unsynchronized posture data.

C:

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: A posture change updates the FortiGate tag and the access decision. That follows remediation of: The downstream policy uses stale or unsynchronized posture data.

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: A posture change updates the FortiGate tag and the access decision. That follows remediation of: The downstream policy uses stale or unsynchronized posture data.

Question 427

Original fictional FortiClient EMS 7.4 practice case R181-CASE-107 — Regional insurer reviewing endpoint posture. Observed evidence: A test laptop remains tagged trusted on FortiGate after it stops meeting EMS security requirements. Which management, security, or integration failure most directly explains the evidence?

  1. The downstream policy uses stale or unsynchronized posture data.
  2. Fabric registration workflow lacks peer approval and change control.
  3. Connector trust continuity was omitted from certificate maintenance.
  4. Shared integration credentials undermine peer-specific audit and revocation.

Explanation

Correct Answer

A:

The supplied evidence — A test laptop remains tagged trusted on FortiGate after it stops meeting EMS security requirements — most directly supports: The downstream policy uses stale or unsynchronized posture data. Confirm the explanation by applying the controlled correction: Verify EMS tag rule evaluation and synchronization freshness on FortiGate; then checking that: A posture change updates the FortiGate tag and the access decision. 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: Multiple administrators can independently authorize unknown FortiGates to EMS. Here the actual observation — A test laptop remains tagged trusted on FortiGate after it stops meeting EMS security requirements — most directly indicates: The downstream policy uses stale or unsynchronized posture data. The scoped correction is: Verify EMS tag rule evaluation and synchronization freshness on FortiGate.

C:

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 test laptop remains tagged trusted on FortiGate after it stops meeting EMS security requirements — most directly indicates: The downstream policy uses stale or unsynchronized posture data. The scoped correction is: Verify EMS tag rule evaluation and synchronization freshness on FortiGate.

D:

Incorrect for the stated evidence. This alternative concern better explains a different situation: Another FortiGate is mistakenly trusted using credentials intended for a separate device. Here the actual observation — A test laptop remains tagged trusted on FortiGate after it stops meeting EMS security requirements — most directly indicates: The downstream policy uses stale or unsynchronized posture data. The scoped correction is: Verify EMS tag rule evaluation and synchronization freshness on FortiGate.

Question 428

Original fictional FortiClient EMS 7.4 practice case R181-CASE-107 — Regional insurer reviewing endpoint posture. Observed evidence: A test laptop remains tagged trusted on FortiGate after it stops meeting EMS security requirements. 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: 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.
  3. Add a tested post-change acceptance gate requiring this outcome: Only the explicitly approved firewall joins EMS Fabric devices. Flag any recurrence of this warning sign: Multiple administrators can independently authorize unknown FortiGates to EMS.
  4. 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.

Explanation

Correct Answer

D:

The preventive gate explicitly checks: A posture change updates the FortiGate tag and the access decision, and escalates recurrence of: A test laptop remains tagged trusted on FortiGate after it stops meeting EMS security requirements. That pair addresses the identified issue: The downstream policy uses stale or unsynchronized posture data. 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: EMS server certificate is renewed but the Fabric peer still trusts the prior identity. The current failure to watch for is: A test laptop remains tagged trusted on FortiGate after it stops meeting EMS security requirements. Use a monitored gate confirming: A posture change updates the FortiGate tag and the access decision.

B:

Incorrect for this incident. That acceptance gate guards against a different situation: Another FortiGate is mistakenly trusted using credentials intended for a separate device. The current failure to watch for is: A test laptop remains tagged trusted on FortiGate after it stops meeting EMS security requirements. Use a monitored gate confirming: A posture change updates the FortiGate tag and the access decision.

C:

Incorrect for this incident. That acceptance gate guards against a different situation: Multiple administrators can independently authorize unknown FortiGates to EMS. The current failure to watch for is: A test laptop remains tagged trusted on FortiGate after it stops meeting EMS security requirements. Use a monitored gate confirming: A posture change updates the FortiGate tag and the access decision.

Question 429

Original fictional FortiClient EMS 7.4 practice case R181-CASE-108 — Engineering group defining Fabric ownership. Observed evidence: Multiple administrators can independently authorize unknown FortiGates to EMS. Which focused administrator action best resolves the identified problem while preserving unrelated security controls?

  1. Establish and verify the second firewall's independent EMS connector.
  2. Require reviewed connector registration and least-privilege authorization.
  3. Restrict tag-based policy application to the designated protected resources.
  4. Select the intended compliance tag and verify its assignment rules.

Explanation

Correct Answer

B:

Correct for this fictional case. The distinguishing signal is: Multiple administrators can independently authorize unknown FortiGates to EMS. It points to: Fabric registration workflow lacks peer approval and change control. The targeted correction is: Require reviewed connector registration and least-privilege authorization. Verify success by checking: Only the explicitly approved firewall joins EMS Fabric devices. 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: Tags work on headquarters firewall but not on the new regional firewall. That case concerns: Fabric pairing is per authorized peer and was not completed for the second device. Here the observed distinction is: Multiple administrators can independently authorize unknown FortiGates to EMS. A more directly targeted response is: Require reviewed connector registration and least-privilege authorization.

C:

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: Multiple administrators can independently authorize unknown FortiGates to EMS. A more directly targeted response is: Require reviewed connector registration and least-privilege authorization.

D:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: A firewall policy grants access based solely on the existence of any EMS tag without checking the correct compliance tag. That case concerns: The policy is not bound to the specific security posture condition. Here the observed distinction is: Multiple administrators can independently authorize unknown FortiGates to EMS. A more directly targeted response is: Require reviewed connector registration and least-privilege authorization.

Question 430

Original fictional FortiClient EMS 7.4 practice case R181-CASE-108 — Engineering group defining Fabric ownership. Observed evidence: Multiple administrators can independently authorize unknown FortiGates to EMS. After the scoped corrective action, which observation best confirms this specific incident was resolved?

  1. Only the explicitly approved firewall joins EMS Fabric devices.
  2. Both authorized firewalls display the correct test posture tags.
  3. Only endpoints meeting the required posture are included in the rule.
  4. Only managed eligible devices gain access to the specified service.

Explanation

Correct Answer

A:

This is the case-specific acceptance evidence after taking the targeted step: Require reviewed connector registration and least-privilege authorization. The initial signal was: Multiple administrators can independently authorize unknown FortiGates to EMS. A generic online indication alone would not prove this particular issue was resolved: Fabric registration workflow lacks peer approval and change control.

Incorrect Answers

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: Only the explicitly approved firewall joins EMS Fabric devices. That follows remediation of: Fabric registration workflow lacks peer approval and change control.

C:

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: Only the explicitly approved firewall joins EMS Fabric devices. That follows remediation of: Fabric registration workflow lacks peer approval and change control.

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: Only the explicitly approved firewall joins EMS Fabric devices. That follows remediation of: Fabric registration workflow lacks peer approval and change control.

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