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 6

Question 50

Original fictional FortiClient EMS 7.4 practice case R181-CASE-013 — Professional-services firm delegating operations. Observed evidence: Everyone is assigned the highest administrative role to simplify troubleshooting. After the scoped corrective action, which observation best confirms this specific incident was resolved?

  1. An off-site pilot endpoint establishes authenticated telemetry with EMS.
  2. The help desk can view status but cannot change protected system settings.
  3. FortiGate receives the expected EMS-derived endpoint security tags.
  4. Pilot endpoints check in and receive intended profiles on the target EMS.

Explanation

Correct Answer

B:

This is the case-specific acceptance evidence after taking the targeted step: Define least-privilege EMS administrative roles and a break-glass procedure. The initial signal was: Everyone is assigned the highest administrative role to simplify troubleshooting. A generic online indication alone would not prove this particular issue was resolved: The management architecture lacks separation of operational duties.

Incorrect Answers

A:

Incorrect for this incident. This result would support a different diagnosis: Endpoint management requires clients to reach the EMS server's supported services; its warning sign is: The high-level design omits any reachable path from off-site agents to EMS. The current case instead requires verification that: The help desk can view status but cannot change protected system settings. That follows remediation of: The management architecture lacks separation of operational duties.

C:

Incorrect for this incident. This result would support a different diagnosis: The policy enforcement device has no authorized posture-information integration; its warning sign is: The draft diagram says FortiGate automatically reads endpoint posture without an EMS Fabric connector. The current case instead requires verification that: The help desk can view status but cannot change protected system settings. That follows remediation of: The management architecture lacks separation of operational duties.

D:

Incorrect for this incident. This result would support a different diagnosis: The handover lacks a verified agent-registration and configuration cutover; its warning sign is: The migration plan decommissions the old EMS before confirming the replacement can manage the pilot. The current case instead requires verification that: The help desk can view status but cannot change protected system settings. That follows remediation of: The management architecture lacks separation of operational duties.

Question 51

Original fictional FortiClient EMS 7.4 practice case R181-CASE-013 — Professional-services firm delegating operations. Observed evidence: Everyone is assigned the highest administrative role to simplify troubleshooting. Which management, security, or integration failure most directly explains the evidence?

  1. Endpoint management requires clients to reach the EMS server's supported services.
  2. The policy enforcement device has no authorized posture-information integration.
  3. The management architecture lacks separation of operational duties.
  4. The handover lacks a verified agent-registration and configuration cutover.

Explanation

Correct Answer

C:

The supplied evidence — Everyone is assigned the highest administrative role to simplify troubleshooting — most directly supports: The management architecture lacks separation of operational duties. Confirm the explanation by applying the controlled correction: Define least-privilege EMS administrative roles and a break-glass procedure; then checking that: The help desk can view status but cannot change protected system settings. 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 high-level design omits any reachable path from off-site agents to EMS. Here the actual observation — Everyone is assigned the highest administrative role to simplify troubleshooting — most directly indicates: The management architecture lacks separation of operational duties. The scoped correction is: Define least-privilege EMS administrative roles and a break-glass procedure.

B:

Incorrect for the stated evidence. This alternative concern better explains a different situation: The draft diagram says FortiGate automatically reads endpoint posture without an EMS Fabric connector. Here the actual observation — Everyone is assigned the highest administrative role to simplify troubleshooting — most directly indicates: The management architecture lacks separation of operational duties. The scoped correction is: Define least-privilege EMS administrative roles and a break-glass procedure.

D:

Incorrect for the stated evidence. This alternative concern better explains a different situation: The migration plan decommissions the old EMS before confirming the replacement can manage the pilot. Here the actual observation — Everyone is assigned the highest administrative role to simplify troubleshooting — most directly indicates: The management architecture lacks separation of operational duties. The scoped correction is: Define least-privilege EMS administrative roles and a break-glass procedure.

Question 52

Original fictional FortiClient EMS 7.4 practice case R181-CASE-013 — Professional-services firm delegating operations. Observed evidence: Everyone is assigned the highest administrative role to simplify troubleshooting. 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: Pilot endpoints check in and receive intended profiles on the target EMS. Flag any recurrence of this warning sign: The migration plan decommissions the old EMS before confirming the replacement can manage the pilot.
  2. Add a tested post-change acceptance gate requiring this outcome: The help desk can view status but cannot change protected system settings. Flag any recurrence of this warning sign: Everyone is assigned the highest administrative role to simplify troubleshooting.
  3. Add a tested post-change acceptance gate requiring this outcome: FortiGate receives the expected EMS-derived endpoint security tags. Flag any recurrence of this warning sign: The draft diagram says FortiGate automatically reads endpoint posture without an EMS Fabric connector.
  4. Add a tested post-change acceptance gate requiring this outcome: An off-site pilot endpoint establishes authenticated telemetry with EMS. Flag any recurrence of this warning sign: The high-level design omits any reachable path from off-site agents to EMS.

Explanation

Correct Answer

B:

The preventive gate explicitly checks: The help desk can view status but cannot change protected system settings, and escalates recurrence of: Everyone is assigned the highest administrative role to simplify troubleshooting. That pair addresses the identified issue: The management architecture lacks separation of operational duties. 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 migration plan decommissions the old EMS before confirming the replacement can manage the pilot. The current failure to watch for is: Everyone is assigned the highest administrative role to simplify troubleshooting. Use a monitored gate confirming: The help desk can view status but cannot change protected system settings.

C:

Incorrect for this incident. That acceptance gate guards against a different situation: The draft diagram says FortiGate automatically reads endpoint posture without an EMS Fabric connector. The current failure to watch for is: Everyone is assigned the highest administrative role to simplify troubleshooting. Use a monitored gate confirming: The help desk can view status but cannot change protected system settings.

D:

Incorrect for this incident. That acceptance gate guards against a different situation: The high-level design omits any reachable path from off-site agents to EMS. The current failure to watch for is: Everyone is assigned the highest administrative role to simplify troubleshooting. Use a monitored gate confirming: The help desk can view status but cannot change protected system settings.

Question 53

Original fictional FortiClient EMS 7.4 practice case R181-CASE-014 — Healthcare group migrating site-by-site. Observed evidence: The migration plan decommissions the old EMS before confirming the replacement can manage the pilot. Which focused administrator action best resolves the identified problem while preserving unrelated security controls?

  1. Plan a reachable managed FQDN with valid certificates and approved DNS records.
  2. Document who approves policies, who deploys profiles, and who can quarantine endpoints.
  3. Stage EMS migration and validate a test endpoint group before retiring the earlier service.
  4. Document appropriate tenant or instance boundaries and least-privilege operator access.

Explanation

Correct Answer

C:

Correct for this fictional case. The distinguishing signal is: The migration plan decommissions the old EMS before confirming the replacement can manage the pilot. It points to: The handover lacks a verified agent-registration and configuration cutover. The targeted correction is: Stage EMS migration and validate a test endpoint group before retiring the earlier service. Verify success by checking: Pilot endpoints check in and receive intended profiles on the target EMS. 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 design uses only a changing private IP for remote endpoint telemetry. That case concerns: The management identity cannot remain stable across network changes. Here the observed distinction is: The migration plan decommissions the old EMS before confirming the replacement can manage the pilot. A more directly targeted response is: Stage EMS migration and validate a test endpoint group before retiring the earlier service.

B:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: The contract delegates console access but does not define responsibility for profile approval or incident quarantine. That case concerns: Operational ownership between the MSP and customer is ambiguous. Here the observed distinction is: The migration plan decommissions the old EMS before confirming the replacement can manage the pilot. A more directly targeted response is: Stage EMS migration and validate a test endpoint group before retiring the earlier service.

D:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: An engineer proposes putting unrelated customer endpoints in the same administrative scope with unrestricted roles. That case concerns: Administrative isolation and delegated authority have not been designed for multiple customers. Here the observed distinction is: The migration plan decommissions the old EMS before confirming the replacement can manage the pilot. A more directly targeted response is: Stage EMS migration and validate a test endpoint group before retiring the earlier service.

Question 54

Original fictional FortiClient EMS 7.4 practice case R181-CASE-014 — Healthcare group migrating site-by-site. Observed evidence: The migration plan decommissions the old EMS before confirming the replacement can manage the pilot. After the scoped corrective action, which observation best confirms this specific incident was resolved?

  1. Pilot endpoints check in and receive intended profiles on the target EMS.
  2. A tabletop exercise follows the agreed authorization chain without privilege gaps.
  3. The test operator can see only approved customer devices and actions.
  4. Endpoint connections continue to resolve and authenticate after the address change.

Explanation

Correct Answer

A:

This is the case-specific acceptance evidence after taking the targeted step: Stage EMS migration and validate a test endpoint group before retiring the earlier service. The initial signal was: The migration plan decommissions the old EMS before confirming the replacement can manage the pilot. A generic online indication alone would not prove this particular issue was resolved: The handover lacks a verified agent-registration and configuration cutover.

Incorrect Answers

B:

Incorrect for this incident. This result would support a different diagnosis: Operational ownership between the MSP and customer is ambiguous; its warning sign is: The contract delegates console access but does not define responsibility for profile approval or incident quarantine. The current case instead requires verification that: Pilot endpoints check in and receive intended profiles on the target EMS. That follows remediation of: The handover lacks a verified agent-registration and configuration cutover.

C:

Incorrect for this incident. This result would support a different diagnosis: Administrative isolation and delegated authority have not been designed for multiple customers; its warning sign is: An engineer proposes putting unrelated customer endpoints in the same administrative scope with unrestricted roles. The current case instead requires verification that: Pilot endpoints check in and receive intended profiles on the target EMS. That follows remediation of: The handover lacks a verified agent-registration and configuration cutover.

D:

Incorrect for this incident. This result would support a different diagnosis: The management identity cannot remain stable across network changes; its warning sign is: The design uses only a changing private IP for remote endpoint telemetry. The current case instead requires verification that: Pilot endpoints check in and receive intended profiles on the target EMS. That follows remediation of: The handover lacks a verified agent-registration and configuration cutover.

Question 55

Original fictional FortiClient EMS 7.4 practice case R181-CASE-014 — Healthcare group migrating site-by-site. Observed evidence: The migration plan decommissions the old EMS before confirming the replacement can manage the pilot. Which management, security, or integration failure most directly explains the evidence?

  1. The management identity cannot remain stable across network changes.
  2. The handover lacks a verified agent-registration and configuration cutover.
  3. Administrative isolation and delegated authority have not been designed for multiple customers.
  4. Operational ownership between the MSP and customer is ambiguous.

Explanation

Correct Answer

B:

The supplied evidence — The migration plan decommissions the old EMS before confirming the replacement can manage the pilot — most directly supports: The handover lacks a verified agent-registration and configuration cutover. Confirm the explanation by applying the controlled correction: Stage EMS migration and validate a test endpoint group before retiring the earlier service; then checking that: Pilot endpoints check in and receive intended profiles on the target EMS. 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 design uses only a changing private IP for remote endpoint telemetry. Here the actual observation — The migration plan decommissions the old EMS before confirming the replacement can manage the pilot — most directly indicates: The handover lacks a verified agent-registration and configuration cutover. The scoped correction is: Stage EMS migration and validate a test endpoint group before retiring the earlier service.

C:

Incorrect for the stated evidence. This alternative concern better explains a different situation: An engineer proposes putting unrelated customer endpoints in the same administrative scope with unrestricted roles. Here the actual observation — The migration plan decommissions the old EMS before confirming the replacement can manage the pilot — most directly indicates: The handover lacks a verified agent-registration and configuration cutover. The scoped correction is: Stage EMS migration and validate a test endpoint group before retiring the earlier service.

D:

Incorrect for the stated evidence. This alternative concern better explains a different situation: The contract delegates console access but does not define responsibility for profile approval or incident quarantine. Here the actual observation — The migration plan decommissions the old EMS before confirming the replacement can manage the pilot — most directly indicates: The handover lacks a verified agent-registration and configuration cutover. The scoped correction is: Stage EMS migration and validate a test endpoint group before retiring the earlier service.

Question 56

Original fictional FortiClient EMS 7.4 practice case R181-CASE-014 — Healthcare group migrating site-by-site. Observed evidence: The migration plan decommissions the old EMS before confirming the replacement can manage the pilot. 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: Pilot endpoints check in and receive intended profiles on the target EMS. Flag any recurrence of this warning sign: The migration plan decommissions the old EMS before confirming the replacement can manage the pilot.
  2. Add a tested post-change acceptance gate requiring this outcome: Endpoint connections continue to resolve and authenticate after the address change. Flag any recurrence of this warning sign: The design uses only a changing private IP for remote endpoint telemetry.
  3. Add a tested post-change acceptance gate requiring this outcome: The test operator can see only approved customer devices and actions. Flag any recurrence of this warning sign: An engineer proposes putting unrelated customer endpoints in the same administrative scope with unrestricted roles.
  4. Add a tested post-change acceptance gate requiring this outcome: A tabletop exercise follows the agreed authorization chain without privilege gaps. Flag any recurrence of this warning sign: The contract delegates console access but does not define responsibility for profile approval or incident quarantine.

Explanation

Correct Answer

A:

The preventive gate explicitly checks: Pilot endpoints check in and receive intended profiles on the target EMS, and escalates recurrence of: The migration plan decommissions the old EMS before confirming the replacement can manage the pilot. That pair addresses the identified issue: The handover lacks a verified agent-registration and configuration cutover. 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 design uses only a changing private IP for remote endpoint telemetry. The current failure to watch for is: The migration plan decommissions the old EMS before confirming the replacement can manage the pilot. Use a monitored gate confirming: Pilot endpoints check in and receive intended profiles on the target EMS.

C:

Incorrect for this incident. That acceptance gate guards against a different situation: An engineer proposes putting unrelated customer endpoints in the same administrative scope with unrestricted roles. The current failure to watch for is: The migration plan decommissions the old EMS before confirming the replacement can manage the pilot. Use a monitored gate confirming: Pilot endpoints check in and receive intended profiles on the target EMS.

D:

Incorrect for this incident. That acceptance gate guards against a different situation: The contract delegates console access but does not define responsibility for profile approval or incident quarantine. The current failure to watch for is: The migration plan decommissions the old EMS before confirming the replacement can manage the pilot. Use a monitored gate confirming: Pilot endpoints check in and receive intended profiles on the target EMS.

Question 57

Original fictional FortiClient EMS 7.4 practice case R181-CASE-015 — School district choosing a management hostname. Observed evidence: The design uses only a changing private IP for remote endpoint telemetry. Which focused administrator action best resolves the identified problem while preserving unrelated security controls?

  1. Compare supported on-premises or FortiClient Cloud options against reachability and ownership constraints.
  2. Add EMS service, certificate, storage, and telemetry health checks to operational monitoring.
  3. Validate the supported EMS deployment and recovery model for the selected version before introducing failover.
  4. Plan a reachable managed FQDN with valid certificates and approved DNS records.

Explanation

Correct Answer

D:

Correct for this fictional case. The distinguishing signal is: The design uses only a changing private IP for remote endpoint telemetry. It points to: The management identity cannot remain stable across network changes. The targeted correction is: Plan a reachable managed FQDN with valid certificates and approved DNS records. Verify success by checking: Endpoint connections continue to resolve and authenticate after the address change. 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 deployment diagram lacks a decision about on-premises versus hosted management connectivity. That case concerns: EMS placement and connectivity requirements are unresolved before rollout. Here the observed distinction is: The design uses only a changing private IP for remote endpoint telemetry. A more directly targeted response is: Plan a reachable managed FQDN with valid certificates and approved DNS records.

B:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: The monitoring diagram includes endpoint malware alerts but ignores EMS service and connectivity health. That case concerns: Endpoint event feeds alone cannot detect a failed central management plane. Here the observed distinction is: The design uses only a changing private IP for remote endpoint telemetry. A more directly targeted response is: Plan a reachable managed FQDN with valid certificates and approved DNS records.

C:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: The team assumes an arbitrary load balancer alone guarantees full EMS data and certificate recoverability. That case concerns: Management-plane resilience needs supported backup and recovery design rather than just front-end reachability. Here the observed distinction is: The design uses only a changing private IP for remote endpoint telemetry. A more directly targeted response is: Plan a reachable managed FQDN with valid certificates and approved DNS records.

Question 58

Original fictional FortiClient EMS 7.4 practice case R181-CASE-015 — School district choosing a management hostname. Observed evidence: The design uses only a changing private IP for remote endpoint telemetry. After the scoped corrective action, which observation best confirms this specific incident was resolved?

  1. A simulated EMS outage triggers an administration alert independent of endpoint malware.
  2. A controlled recovery restores endpoints' intended management and trust state.
  3. Endpoint connections continue to resolve and authenticate after the address change.
  4. The approved deployment model has an explicit endpoint-to-management communication path.

Explanation

Correct Answer

C:

This is the case-specific acceptance evidence after taking the targeted step: Plan a reachable managed FQDN with valid certificates and approved DNS records. The initial signal was: The design uses only a changing private IP for remote endpoint telemetry. A generic online indication alone would not prove this particular issue was resolved: The management identity cannot remain stable across network changes.

Incorrect Answers

A:

Incorrect for this incident. This result would support a different diagnosis: Endpoint event feeds alone cannot detect a failed central management plane; its warning sign is: The monitoring diagram includes endpoint malware alerts but ignores EMS service and connectivity health. The current case instead requires verification that: Endpoint connections continue to resolve and authenticate after the address change. That follows remediation of: The management identity cannot remain stable across network changes.

B:

Incorrect for this incident. This result would support a different diagnosis: Management-plane resilience needs supported backup and recovery design rather than just front-end reachability; its warning sign is: The team assumes an arbitrary load balancer alone guarantees full EMS data and certificate recoverability. The current case instead requires verification that: Endpoint connections continue to resolve and authenticate after the address change. That follows remediation of: The management identity cannot remain stable across network changes.

D:

Incorrect for this incident. This result would support a different diagnosis: EMS placement and connectivity requirements are unresolved before rollout; its warning sign is: The deployment diagram lacks a decision about on-premises versus hosted management connectivity. The current case instead requires verification that: Endpoint connections continue to resolve and authenticate after the address change. That follows remediation of: The management identity cannot remain stable across network changes.

Question 59

Original fictional FortiClient EMS 7.4 practice case R181-CASE-015 — School district choosing a management hostname. Observed evidence: The design uses only a changing private IP for remote endpoint telemetry. Which management, security, or integration failure most directly explains the evidence?

  1. The management identity cannot remain stable across network changes.
  2. Endpoint event feeds alone cannot detect a failed central management plane.
  3. Management-plane resilience needs supported backup and recovery design rather than just front-end reachability.
  4. EMS placement and connectivity requirements are unresolved before rollout.

Explanation

Correct Answer

A:

The supplied evidence — The design uses only a changing private IP for remote endpoint telemetry — most directly supports: The management identity cannot remain stable across network changes. Confirm the explanation by applying the controlled correction: Plan a reachable managed FQDN with valid certificates and approved DNS records; then checking that: Endpoint connections continue to resolve and authenticate after the address change. 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 monitoring diagram includes endpoint malware alerts but ignores EMS service and connectivity health. Here the actual observation — The design uses only a changing private IP for remote endpoint telemetry — most directly indicates: The management identity cannot remain stable across network changes. The scoped correction is: Plan a reachable managed FQDN with valid certificates and approved DNS records.

C:

Incorrect for the stated evidence. This alternative concern better explains a different situation: The team assumes an arbitrary load balancer alone guarantees full EMS data and certificate recoverability. Here the actual observation — The design uses only a changing private IP for remote endpoint telemetry — most directly indicates: The management identity cannot remain stable across network changes. The scoped correction is: Plan a reachable managed FQDN with valid certificates and approved DNS records.

D:

Incorrect for the stated evidence. This alternative concern better explains a different situation: The deployment diagram lacks a decision about on-premises versus hosted management connectivity. Here the actual observation — The design uses only a changing private IP for remote endpoint telemetry — most directly indicates: The management identity cannot remain stable across network changes. The scoped correction is: Plan a reachable managed FQDN with valid certificates and approved DNS records.

Question 60

Original fictional FortiClient EMS 7.4 practice case R181-CASE-015 — School district choosing a management hostname. Observed evidence: The design uses only a changing private IP for remote endpoint telemetry. 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 simulated EMS outage triggers an administration alert independent of endpoint malware. Flag any recurrence of this warning sign: The monitoring diagram includes endpoint malware alerts but ignores EMS service and connectivity health.
  2. Add a tested post-change acceptance gate requiring this outcome: The approved deployment model has an explicit endpoint-to-management communication path. Flag any recurrence of this warning sign: The deployment diagram lacks a decision about on-premises versus hosted management connectivity.
  3. Add a tested post-change acceptance gate requiring this outcome: Endpoint connections continue to resolve and authenticate after the address change. Flag any recurrence of this warning sign: The design uses only a changing private IP for remote endpoint telemetry.
  4. Add a tested post-change acceptance gate requiring this outcome: A controlled recovery restores endpoints' intended management and trust state. Flag any recurrence of this warning sign: The team assumes an arbitrary load balancer alone guarantees full EMS data and certificate recoverability.

Explanation

Correct Answer

C:

The preventive gate explicitly checks: Endpoint connections continue to resolve and authenticate after the address change, and escalates recurrence of: The design uses only a changing private IP for remote endpoint telemetry. That pair addresses the identified issue: The management identity cannot remain stable across network changes. 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 monitoring diagram includes endpoint malware alerts but ignores EMS service and connectivity health. The current failure to watch for is: The design uses only a changing private IP for remote endpoint telemetry. Use a monitored gate confirming: Endpoint connections continue to resolve and authenticate after the address change.

B:

Incorrect for this incident. That acceptance gate guards against a different situation: The deployment diagram lacks a decision about on-premises versus hosted management connectivity. The current failure to watch for is: The design uses only a changing private IP for remote endpoint telemetry. Use a monitored gate confirming: Endpoint connections continue to resolve and authenticate after the address change.

D:

Incorrect for this incident. That acceptance gate guards against a different situation: The team assumes an arbitrary load balancer alone guarantees full EMS data and certificate recoverability. The current failure to watch for is: The design uses only a changing private IP for remote endpoint telemetry. Use a monitored gate confirming: Endpoint connections continue to resolve and authenticate after the address change.

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