McAfee Secure

Exam Code: FCP_FCT_AD-7.4

Exam Name: Fortinet NSE 6 - FortiClient EMS 7.4 Administrator

Certification Provider: Fortinet

Corresponding Certification: NSE6

Fortinet FCP_FCT_AD-7.4 Questions & Answers

Study with Up-To-Date REAL Exam Questions and Answers from the ACTUAL Test

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 30

Question 290

At fictional Summit Agriculture, an endpoint security engineer responsible for rural offices is reviewing EMS architecture, operating-system support and server management during a Security Fabric integration test (FCT-7.4-1.2-073). The observed endpoint management issue is: An operations engineer enables broad EMS administrative permissions for a help-desk worker who only needs device status views. Which endpoint-management or security principle best explains the proper response?

  1. Privileged configuration access should follow operational responsibilities rather than convenience.
  2. Server authentication and client device identity solve different parts of a secure management and access design.
  3. Endpoint enrollment and telemetry scale create sustained demands on EMS host resources.
  4. Major EMS 7.4 platform changes can invalidate older server architecture and migration assumptions.

Explanation

Correct Answer

A:

The governing principle is: Privileged configuration access should follow operational responsibilities rather than convenience. Here the appropriate correction is to use supported EMS administrator roles and least-privilege access boundaries for routine support tasks. Confirmation would be that the worker can view authorized endpoint health but cannot change global security policies.

Incorrect Answers

B:

“Server authentication and client device identity solve different parts of a secure management and access design” is not the controlling explanation for an operations engineer enables broad EMS administrative permissions for a help-desk worker who only needs device status views. The cited causal relationship is privileged configuration access should follow operational responsibilities rather than convenience. The matching answer is “Privileged configuration access should follow operational responsibilities rather than convenience”.

C:

“Endpoint enrollment and telemetry scale create sustained demands on EMS host resources” is not the controlling explanation for an operations engineer enables broad EMS administrative permissions for a help-desk worker who only needs device status views. The cited causal relationship is privileged configuration access should follow operational responsibilities rather than convenience. The matching answer is “Privileged configuration access should follow operational responsibilities rather than convenience”.

D:

“Major EMS 7.4 platform changes can invalidate older server architecture and migration assumptions” is not the controlling explanation for an operations engineer enables broad EMS administrative permissions for a help-desk worker who only needs device status views. The cited causal relationship is privileged configuration access should follow operational responsibilities rather than convenience. The matching answer is “Privileged configuration access should follow operational responsibilities rather than convenience”.

Question 291

At fictional Summit Agriculture, an endpoint security engineer responsible for rural offices is reviewing EMS architecture, operating-system support and server management during a Security Fabric integration test (FCT-7.4-1.2-073). The observed endpoint management issue is: An operations engineer enables broad EMS administrative permissions for a help-desk worker who only needs device status views. Which recurring preventive or detective safeguard would best reduce recurrence?

  1. Enforce a reviewed application inventory and resource baseline on EMS hosts.
  2. Record license ownership and post-install setup steps in the EMS server commissioning record.
  3. Review EMS administrative activity and effective privileges regularly.
  4. Include DNS TTL and remote-device verification in every EMS migration plan.

Explanation

Correct Answer

C:

The recurring safeguard is to review EMS administrative activity and effective privileges regularly. It mitigates the actual failure: An operations engineer enables broad EMS administrative permissions for a help-desk worker who only needs device status views. A suitable correction is to use supported EMS administrator roles and least-privilege access boundaries for routine support tasks; its proof is that the worker can view authorized endpoint health but cannot change global security policies.

Incorrect Answers

A:

“Enforce a reviewed application inventory and resource baseline on EMS hosts” checks a different ongoing risk rather than the reported failure: an operations engineer enables broad EMS administrative permissions for a help-desk worker who only needs device status views. The relevant mechanism is privileged configuration access should follow operational responsibilities rather than convenience. The directly matched preventive control is “Review EMS administrative activity and effective privileges regularly”.

B:

“Record license ownership and post-install setup steps in the EMS server commissioning record” checks a different ongoing risk rather than the reported failure: an operations engineer enables broad EMS administrative permissions for a help-desk worker who only needs device status views. The relevant mechanism is privileged configuration access should follow operational responsibilities rather than convenience. The directly matched preventive control is “Review EMS administrative activity and effective privileges regularly”.

D:

“Include DNS TTL and remote-device verification in every EMS migration plan” checks a different ongoing risk rather than the reported failure: an operations engineer enables broad EMS administrative permissions for a help-desk worker who only needs device status views. The relevant mechanism is privileged configuration access should follow operational responsibilities rather than convenience. The directly matched preventive control is “Review EMS administrative activity and effective privileges regularly”.

Question 292

At fictional Summit Agriculture, an endpoint security engineer responsible for rural offices is reviewing EMS architecture, operating-system support and server management during a Security Fabric integration test (FCT-7.4-1.2-073). The observed endpoint management issue is: An operations engineer enables broad EMS administrative permissions for a help-desk worker who only needs device status views. Which corrective engineering action best addresses the specific problem?

  1. Separate staging and production EMS service identities, DNS and endpoint deployment settings.
  2. Plan secure reachable EMS management endpoints and certificate trust for both internal and remote agent connectivity.
  3. Use supported EMS administrator roles and least-privilege access boundaries for routine support tasks.
  4. Define supported tenant or administrator access boundaries appropriate to the EMS deployment and verify scoped rights.

Explanation

Correct Answer

C:

The targeted correction is to use supported EMS administrator roles and least-privilege access boundaries for routine support tasks. The diagnosed issue is: An operations engineer enables broad EMS administrative permissions for a help-desk worker who only needs device status views. Evidence of success is: The worker can view authorized endpoint health but cannot change global security policies. The underlying endpoint-security principle is that privileged configuration access should follow operational responsibilities rather than convenience.

Incorrect Answers

A:

“Separate staging and production EMS service identities, DNS and endpoint deployment settings” would address a different implementation objective; the stated problem is an operations engineer enables broad EMS administrative permissions for a help-desk worker who only needs device status views. The actual control boundary is privileged configuration access should follow operational responsibilities rather than convenience. The directly responsive action is “Use supported EMS administrator roles and least-privilege access boundaries for routine support tasks”.

B:

“Plan secure reachable EMS management endpoints and certificate trust for both internal and remote agent connectivity” would address a different implementation objective; the stated problem is an operations engineer enables broad EMS administrative permissions for a help-desk worker who only needs device status views. The actual control boundary is privileged configuration access should follow operational responsibilities rather than convenience. The directly responsive action is “Use supported EMS administrator roles and least-privilege access boundaries for routine support tasks”.

D:

“Define supported tenant or administrator access boundaries appropriate to the EMS deployment and verify scoped rights” would address a different implementation objective; the stated problem is an operations engineer enables broad EMS administrative permissions for a help-desk worker who only needs device status views. The actual control boundary is privileged configuration access should follow operational responsibilities rather than convenience. The directly responsive action is “Use supported EMS administrator roles and least-privilege access boundaries for routine support tasks”.

Question 293

At fictional Zenith Tourism, an endpoint security engineer responsible for visitor kiosks is reviewing FortiGate integration, posture tags, ZTNA and containment during a device support triage (FCT-7.4-3.2-074). The observed endpoint management issue is: A compromised device is quarantined yet the help desk continues interpreting its loss of network access as a new DHCP failure. Which observation best verifies that the proposed correction worked?

  1. Test network traffic is restricted according to the quarantine behavior, not merely selected web sites.
  2. Both systems report an authorized connector and FortiGate retrieves current EMS security posture tags.
  3. Active protected endpoints match the approved tag while intentionally disabled protection fails posture.
  4. The device's restricted traffic coincides with an explicit active quarantine state.

Explanation

Correct Answer

D:

This is the direct verification evidence: The device's restricted traffic coincides with an explicit active quarantine state. It supports the engineering change to check EMS quarantine status and device-side quarantine notifications before changing IP addressing. The relevant principle is that intentional endpoint containment can appear as ordinary network unreachability without context.

Incorrect Answers

A:

Evidence that “Test network traffic is restricted according to the quarantine behavior, not merely selected web sites” occurred would not by itself establish resolution of the reported problem: a compromised device is quarantined yet the help desk continues interpreting its loss of network access as a new DHCP failure. The specific reason is intentional endpoint containment can appear as ordinary network unreachability without context. The applicable verification is “The device's restricted traffic coincides with an explicit active quarantine state”.

B:

Evidence that “Both systems report an authorized connector and FortiGate retrieves current EMS security posture tags” occurred would not by itself establish resolution of the reported problem: a compromised device is quarantined yet the help desk continues interpreting its loss of network access as a new DHCP failure. The specific reason is intentional endpoint containment can appear as ordinary network unreachability without context. The applicable verification is “The device's restricted traffic coincides with an explicit active quarantine state”.

C:

Evidence that “Active protected endpoints match the approved tag while intentionally disabled protection fails posture” occurred would not by itself establish resolution of the reported problem: a compromised device is quarantined yet the help desk continues interpreting its loss of network access as a new DHCP failure. The specific reason is intentional endpoint containment can appear as ordinary network unreachability without context. The applicable verification is “The device's restricted traffic coincides with an explicit active quarantine state”.

Question 294

At fictional Zenith Tourism, an endpoint security engineer responsible for visitor kiosks is reviewing FortiGate integration, posture tags, ZTNA and containment during a device support triage (FCT-7.4-3.2-074). The observed endpoint management issue is: A compromised device is quarantined yet the help desk continues interpreting its loss of network access as a new DHCP failure. Which corrective engineering action best addresses the specific problem?

  1. Combine the applicable user authentication and managed endpoint posture conditions in authorized ZTNA policy.
  2. Adopt supported dynamic EMS security posture tag objects tied to current endpoint attributes and applicable IP bindings.
  3. Reconcile EMS quarantine requests with current endpoint acknowledgements and investigate unreachable clients separately.
  4. Check EMS quarantine status and device-side quarantine notifications before changing IP addressing.

Explanation

Correct Answer

D:

The targeted correction is to check EMS quarantine status and device-side quarantine notifications before changing IP addressing. The diagnosed issue is: A compromised device is quarantined yet the help desk continues interpreting its loss of network access as a new DHCP failure. Evidence of success is: The device's restricted traffic coincides with an explicit active quarantine state. The underlying endpoint-security principle is that intentional endpoint containment can appear as ordinary network unreachability without context.

Incorrect Answers

A:

“Combine the applicable user authentication and managed endpoint posture conditions in authorized ZTNA policy” would address a different implementation objective; the stated problem is a compromised device is quarantined yet the help desk continues interpreting its loss of network access as a new DHCP failure. The actual control boundary is intentional endpoint containment can appear as ordinary network unreachability without context. The directly responsive action is “Check EMS quarantine status and device-side quarantine notifications before changing IP addressing”.

B:

“Adopt supported dynamic EMS security posture tag objects tied to current endpoint attributes and applicable IP bindings” would address a different implementation objective; the stated problem is a compromised device is quarantined yet the help desk continues interpreting its loss of network access as a new DHCP failure. The actual control boundary is intentional endpoint containment can appear as ordinary network unreachability without context. The directly responsive action is “Check EMS quarantine status and device-side quarantine notifications before changing IP addressing”.

C:

“Reconcile EMS quarantine requests with current endpoint acknowledgements and investigate unreachable clients separately” would address a different implementation objective; the stated problem is a compromised device is quarantined yet the help desk continues interpreting its loss of network access as a new DHCP failure. The actual control boundary is intentional endpoint containment can appear as ordinary network unreachability without context. The directly responsive action is “Check EMS quarantine status and device-side quarantine notifications before changing IP addressing”.

Question 295

At fictional Zenith Tourism, an endpoint security engineer responsible for visitor kiosks is reviewing FortiGate integration, posture tags, ZTNA and containment during a device support triage (FCT-7.4-3.2-074). The observed endpoint management issue is: A compromised device is quarantined yet the help desk continues interpreting its loss of network access as a new DHCP failure. Which endpoint-management or security principle best explains the proper response?

  1. Sending a containment command does not prove that every agent has enforced it.
  2. Dynamic access decisions are only as current as EMS telemetry and Fabric synchronization.
  3. Quarantine release should be an accountable incident decision rather than an uncontrolled user workaround.
  4. Intentional endpoint containment can appear as ordinary network unreachability without context.

Explanation

Correct Answer

D:

The governing principle is: Intentional endpoint containment can appear as ordinary network unreachability without context. Here the appropriate correction is to check EMS quarantine status and device-side quarantine notifications before changing IP addressing. Confirmation would be that the device's restricted traffic coincides with an explicit active quarantine state.

Incorrect Answers

A:

“Sending a containment command does not prove that every agent has enforced it” is not the controlling explanation for a compromised device is quarantined yet the help desk continues interpreting its loss of network access as a new DHCP failure. The cited causal relationship is intentional endpoint containment can appear as ordinary network unreachability without context. The matching answer is “Intentional endpoint containment can appear as ordinary network unreachability without context”.

B:

“Dynamic access decisions are only as current as EMS telemetry and Fabric synchronization” is not the controlling explanation for a compromised device is quarantined yet the help desk continues interpreting its loss of network access as a new DHCP failure. The cited causal relationship is intentional endpoint containment can appear as ordinary network unreachability without context. The matching answer is “Intentional endpoint containment can appear as ordinary network unreachability without context”.

C:

“Quarantine release should be an accountable incident decision rather than an uncontrolled user workaround” is not the controlling explanation for a compromised device is quarantined yet the help desk continues interpreting its loss of network access as a new DHCP failure. The cited causal relationship is intentional endpoint containment can appear as ordinary network unreachability without context. The matching answer is “Intentional endpoint containment can appear as ordinary network unreachability without context”.

Question 296

At fictional Zenith Tourism, an endpoint security engineer responsible for visitor kiosks is reviewing FortiGate integration, posture tags, ZTNA and containment during a device support triage (FCT-7.4-3.2-074). The observed endpoint management issue is: A compromised device is quarantined yet the help desk continues interpreting its loss of network access as a new DHCP failure. Which recurring preventive or detective safeguard would best reduce recurrence?

  1. Include quarantine status in endpoint network troubleshooting intake.
  2. Review connector trust after EMS certificate renewals and migrations.
  3. Track quarantine command and endpoint acknowledgement states during incident response.
  4. Include applied tag and rule-match checks in ZTNA incident troubleshooting.

Explanation

Correct Answer

A:

The recurring safeguard is to include quarantine status in endpoint network troubleshooting intake. It mitigates the actual failure: A compromised device is quarantined yet the help desk continues interpreting its loss of network access as a new DHCP failure. A suitable correction is to check EMS quarantine status and device-side quarantine notifications before changing IP addressing; its proof is that the device's restricted traffic coincides with an explicit active quarantine state.

Incorrect Answers

B:

“Review connector trust after EMS certificate renewals and migrations” checks a different ongoing risk rather than the reported failure: a compromised device is quarantined yet the help desk continues interpreting its loss of network access as a new DHCP failure. The relevant mechanism is intentional endpoint containment can appear as ordinary network unreachability without context. The directly matched preventive control is “Include quarantine status in endpoint network troubleshooting intake”.

C:

“Track quarantine command and endpoint acknowledgement states during incident response” checks a different ongoing risk rather than the reported failure: a compromised device is quarantined yet the help desk continues interpreting its loss of network access as a new DHCP failure. The relevant mechanism is intentional endpoint containment can appear as ordinary network unreachability without context. The directly matched preventive control is “Include quarantine status in endpoint network troubleshooting intake”.

D:

“Include applied tag and rule-match checks in ZTNA incident troubleshooting” checks a different ongoing risk rather than the reported failure: a compromised device is quarantined yet the help desk continues interpreting its loss of network access as a new DHCP failure. The relevant mechanism is intentional endpoint containment can appear as ordinary network unreachability without context. The directly matched preventive control is “Include quarantine status in endpoint network troubleshooting intake”.

Question 297

At fictional Riverstone Travel, an endpoint security engineer responsible for booking service endpoints is reviewing EMS, endpoint and secure-access troubleshooting during a planned incident response rehearsal (FCT-7.4-4.2-075). The observed endpoint management issue is: An offsite FortiClient device reports certificate warnings after EMS hostname change and operators encourage users to ignore the warnings. Which endpoint-management or security principle best explains the proper response?

  1. Observability is limited by collection time and cannot guarantee current offline endpoint posture.
  2. Device trust and application user credentials are different dependencies in ZTNA.
  3. Management telemetry requires permitted network communication even when local endpoint security is healthy.
  4. Trusted certificate identity must follow the advertised management server name.

Explanation

Correct Answer

D:

The governing principle is: Trusted certificate identity must follow the advertised management server name. Here the appropriate correction is to correct EMS TLS identity and certificate trust instead of training users to bypass authentication errors. Confirmation would be that the endpoint connects to the correct named EMS service without certificate warnings or insecure bypass.

Incorrect Answers

A:

“Observability is limited by collection time and cannot guarantee current offline endpoint posture” is not the controlling explanation for an offsite FortiClient device reports certificate warnings after EMS hostname change and operators encourage users to ignore the warnings. The cited causal relationship is trusted certificate identity must follow the advertised management server name. The matching answer is “Trusted certificate identity must follow the advertised management server name”.

B:

“Device trust and application user credentials are different dependencies in ZTNA” is not the controlling explanation for an offsite FortiClient device reports certificate warnings after EMS hostname change and operators encourage users to ignore the warnings. The cited causal relationship is trusted certificate identity must follow the advertised management server name. The matching answer is “Trusted certificate identity must follow the advertised management server name”.

C:

“Management telemetry requires permitted network communication even when local endpoint security is healthy” is not the controlling explanation for an offsite FortiClient device reports certificate warnings after EMS hostname change and operators encourage users to ignore the warnings. The cited causal relationship is trusted certificate identity must follow the advertised management server name. The matching answer is “Trusted certificate identity must follow the advertised management server name”.

Question 298

At fictional Riverstone Travel, an endpoint security engineer responsible for booking service endpoints is reviewing EMS, endpoint and secure-access troubleshooting during a planned incident response rehearsal (FCT-7.4-4.2-075). The observed endpoint management issue is: An offsite FortiClient device reports certificate warnings after EMS hostname change and operators encourage users to ignore the warnings. Which observation best verifies that the proposed correction worked?

  1. Online test clients apply immediately or within normal sync behavior while offline clients update on reconnection.
  2. The accepted endpoint reports the expected active protections and current successful management communication.
  3. The endpoint connects to the correct named EMS service without certificate warnings or insecure bypass.
  4. Connector authorization and posture synchronization resume once the certificate relationship is repaired.

Explanation

Correct Answer

C:

This is the direct verification evidence: The endpoint connects to the correct named EMS service without certificate warnings or insecure bypass. It supports the engineering change to correct EMS TLS identity and certificate trust instead of training users to bypass authentication errors. The relevant principle is that trusted certificate identity must follow the advertised management server name.

Incorrect Answers

A:

Evidence that “Online test clients apply immediately or within normal sync behavior while offline clients update on reconnection” occurred would not by itself establish resolution of the reported problem: an offsite FortiClient device reports certificate warnings after EMS hostname change and operators encourage users to ignore the warnings. The specific reason is trusted certificate identity must follow the advertised management server name. The applicable verification is “The endpoint connects to the correct named EMS service without certificate warnings or insecure bypass”.

B:

Evidence that “The accepted endpoint reports the expected active protections and current successful management communication” occurred would not by itself establish resolution of the reported problem: an offsite FortiClient device reports certificate warnings after EMS hostname change and operators encourage users to ignore the warnings. The specific reason is trusted certificate identity must follow the advertised management server name. The applicable verification is “The endpoint connects to the correct named EMS service without certificate warnings or insecure bypass”.

D:

Evidence that “Connector authorization and posture synchronization resume once the certificate relationship is repaired” occurred would not by itself establish resolution of the reported problem: an offsite FortiClient device reports certificate warnings after EMS hostname change and operators encourage users to ignore the warnings. The specific reason is trusted certificate identity must follow the advertised management server name. The applicable verification is “The endpoint connects to the correct named EMS service without certificate warnings or insecure bypass”.

Question 299

At fictional Riverstone Travel, an endpoint security engineer responsible for booking service endpoints is reviewing EMS, endpoint and secure-access troubleshooting during a planned incident response rehearsal (FCT-7.4-4.2-075). The observed endpoint management issue is: An offsite FortiClient device reports certificate warnings after EMS hostname change and operators encourage users to ignore the warnings. Which recurring preventive or detective safeguard would best reduce recurrence?

  1. Audit policy and group mappings after organizational unit moves.
  2. Alert on endpoint clock drift and expiring trusted management certificates.
  3. Test representative business applications after FortiClient and policy version changes.
  4. Check trusted certificates against expected hostnames during EMS domain changes.

Explanation

Correct Answer

D:

The recurring safeguard is to check trusted certificates against expected hostnames during EMS domain changes. It mitigates the actual failure: An offsite FortiClient device reports certificate warnings after EMS hostname change and operators encourage users to ignore the warnings. A suitable correction is to correct EMS TLS identity and certificate trust instead of training users to bypass authentication errors; its proof is that the endpoint connects to the correct named EMS service without certificate warnings or insecure bypass.

Incorrect Answers

A:

“Audit policy and group mappings after organizational unit moves” checks a different ongoing risk rather than the reported failure: an offsite FortiClient device reports certificate warnings after EMS hostname change and operators encourage users to ignore the warnings. The relevant mechanism is trusted certificate identity must follow the advertised management server name. The directly matched preventive control is “Check trusted certificates against expected hostnames during EMS domain changes”.

B:

“Alert on endpoint clock drift and expiring trusted management certificates” checks a different ongoing risk rather than the reported failure: an offsite FortiClient device reports certificate warnings after EMS hostname change and operators encourage users to ignore the warnings. The relevant mechanism is trusted certificate identity must follow the advertised management server name. The directly matched preventive control is “Check trusted certificates against expected hostnames during EMS domain changes”.

C:

“Test representative business applications after FortiClient and policy version changes” checks a different ongoing risk rather than the reported failure: an offsite FortiClient device reports certificate warnings after EMS hostname change and operators encourage users to ignore the warnings. The relevant mechanism is trusted certificate identity must follow the advertised management server name. The directly matched preventive control is “Check trusted certificates against expected hostnames during EMS domain changes”.

Question 300

At fictional Riverstone Travel, an endpoint security engineer responsible for booking service endpoints is reviewing EMS, endpoint and secure-access troubleshooting during a planned incident response rehearsal (FCT-7.4-4.2-075). The observed endpoint management issue is: An offsite FortiClient device reports certificate warnings after EMS hostname change and operators encourage users to ignore the warnings. Which corrective engineering action best addresses the specific problem?

  1. Recheck the exact EMS posture predicates, endpoint scan state and FortiGate policy outcome together.
  2. Use supported secure diagnostic collection with authorized scoping and confidential evidence handling.
  3. Restore narrowly scoped EMS transport in the relevant host or network policy without disabling broad protection.
  4. Correct EMS TLS identity and certificate trust instead of training users to bypass authentication errors.

Explanation

Correct Answer

D:

The targeted correction is to correct EMS TLS identity and certificate trust instead of training users to bypass authentication errors. The diagnosed issue is: An offsite FortiClient device reports certificate warnings after EMS hostname change and operators encourage users to ignore the warnings. Evidence of success is: The endpoint connects to the correct named EMS service without certificate warnings or insecure bypass. The underlying endpoint-security principle is that trusted certificate identity must follow the advertised management server name.

Incorrect Answers

A:

“Recheck the exact EMS posture predicates, endpoint scan state and FortiGate policy outcome together” would address a different implementation objective; the stated problem is an offsite FortiClient device reports certificate warnings after EMS hostname change and operators encourage users to ignore the warnings. The actual control boundary is trusted certificate identity must follow the advertised management server name. The directly responsive action is “Correct EMS TLS identity and certificate trust instead of training users to bypass authentication errors”.

B:

“Use supported secure diagnostic collection with authorized scoping and confidential evidence handling” would address a different implementation objective; the stated problem is an offsite FortiClient device reports certificate warnings after EMS hostname change and operators encourage users to ignore the warnings. The actual control boundary is trusted certificate identity must follow the advertised management server name. The directly responsive action is “Correct EMS TLS identity and certificate trust instead of training users to bypass authentication errors”.

C:

“Restore narrowly scoped EMS transport in the relevant host or network policy without disabling broad protection” would address a different implementation objective; the stated problem is an offsite FortiClient device reports certificate warnings after EMS hostname change and operators encourage users to ignore the warnings. The actual control boundary is trusted certificate identity must follow the advertised management server name. The directly responsive action is “Correct EMS TLS identity and certificate trust instead of training users to bypass authentication errors”.

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