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 38

Question 370

At fictional Maple Housing, an endpoint security engineer responsible for facilities support is reviewing FortiGate integration, posture tags, ZTNA and containment during a remote access rollout (FCT-7.4-3.3-093). The observed endpoint management issue is: A managed endpoint has a valid security posture tag but an administrator assumes that tag alone is sufficient to authorize every private application. Which observation best verifies that the proposed correction worked?

  1. Both systems report an authorized connector and FortiGate retrieves current EMS security posture tags.
  2. Confirmed high-risk endpoints are contained while benign controlled events follow appropriate handling.
  3. Active protected endpoints match the approved tag while intentionally disabled protection fails posture.
  4. The allowed device reaches only the designated application while other resources remain denied.

Explanation

Correct Answer

D:

This is the direct verification evidence: The allowed device reaches only the designated application while other resources remain denied. It supports the engineering change to configure appropriate FortiGate ZTNA access policy and destination constraints for the approved tag and user context. The relevant principle is that a posture attribute is an input to an access decision, not a blanket network authorization.

Incorrect Answers

A:

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 managed endpoint has a valid security posture tag but an administrator assumes that tag alone is sufficient to authorize every private application. The specific reason is a posture attribute is an input to an access decision, not a blanket network authorization. The applicable verification is “The allowed device reaches only the designated application while other resources remain denied”.

B:

Evidence that “Confirmed high-risk endpoints are contained while benign controlled events follow appropriate handling” occurred would not by itself establish resolution of the reported problem: a managed endpoint has a valid security posture tag but an administrator assumes that tag alone is sufficient to authorize every private application. The specific reason is a posture attribute is an input to an access decision, not a blanket network authorization. The applicable verification is “The allowed device reaches only the designated application while other resources remain denied”.

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 managed endpoint has a valid security posture tag but an administrator assumes that tag alone is sufficient to authorize every private application. The specific reason is a posture attribute is an input to an access decision, not a blanket network authorization. The applicable verification is “The allowed device reaches only the designated application while other resources remain denied”.

Question 371

At fictional Maple Housing, an endpoint security engineer responsible for facilities support is reviewing FortiGate integration, posture tags, ZTNA and containment during a remote access rollout (FCT-7.4-3.3-093). The observed endpoint management issue is: A managed endpoint has a valid security posture tag but an administrator assumes that tag alone is sufficient to authorize every private application. Which endpoint-management or security principle best explains the proper response?

  1. A posture attribute is an input to an access decision, not a blanket network authorization.
  2. ZTNA access requires an application-level gateway object in addition to EMS device posture.
  3. Identity and device trust are complementary access signals rather than interchangeable checks.
  4. Incident detection and endpoint containment are separate actions that require configured enforcement.

Explanation

Correct Answer

A:

The governing principle is: A posture attribute is an input to an access decision, not a blanket network authorization. Here the appropriate correction is to configure appropriate FortiGate ZTNA access policy and destination constraints for the approved tag and user context. Confirmation would be that the allowed device reaches only the designated application while other resources remain denied.

Incorrect Answers

B:

“ZTNA access requires an application-level gateway object in addition to EMS device posture” is not the controlling explanation for a managed endpoint has a valid security posture tag but an administrator assumes that tag alone is sufficient to authorize every private application. The cited causal relationship is a posture attribute is an input to an access decision, not a blanket network authorization. The matching answer is “A posture attribute is an input to an access decision, not a blanket network authorization”.

C:

“Identity and device trust are complementary access signals rather than interchangeable checks” is not the controlling explanation for a managed endpoint has a valid security posture tag but an administrator assumes that tag alone is sufficient to authorize every private application. The cited causal relationship is a posture attribute is an input to an access decision, not a blanket network authorization. The matching answer is “A posture attribute is an input to an access decision, not a blanket network authorization”.

D:

“Incident detection and endpoint containment are separate actions that require configured enforcement” is not the controlling explanation for a managed endpoint has a valid security posture tag but an administrator assumes that tag alone is sufficient to authorize every private application. The cited causal relationship is a posture attribute is an input to an access decision, not a blanket network authorization. The matching answer is “A posture attribute is an input to an access decision, not a blanket network authorization”.

Question 372

At fictional Maple Housing, an endpoint security engineer responsible for facilities support is reviewing FortiGate integration, posture tags, ZTNA and containment during a remote access rollout (FCT-7.4-3.3-093). The observed endpoint management issue is: A managed endpoint has a valid security posture tag but an administrator assumes that tag alone is sufficient to authorize every private application. Which recurring preventive or detective safeguard would best reduce recurrence?

  1. Monitor ZTNA server certificate hostname and expiration against configured resources.
  2. Rehearse logging, alert propagation and containment on a nonproduction test endpoint.
  3. Validate positive and negative application requests against each ZTNA policy.
  4. Include negative device-posture cases before deploying security-tag firewall policies.

Explanation

Correct Answer

C:

The recurring safeguard is to validate positive and negative application requests against each ZTNA policy. It mitigates the actual failure: A managed endpoint has a valid security posture tag but an administrator assumes that tag alone is sufficient to authorize every private application. A suitable correction is to configure appropriate FortiGate ZTNA access policy and destination constraints for the approved tag and user context; its proof is that the allowed device reaches only the designated application while other resources remain denied.

Incorrect Answers

A:

“Monitor ZTNA server certificate hostname and expiration against configured resources” checks a different ongoing risk rather than the reported failure: a managed endpoint has a valid security posture tag but an administrator assumes that tag alone is sufficient to authorize every private application. The relevant mechanism is a posture attribute is an input to an access decision, not a blanket network authorization. The directly matched preventive control is “Validate positive and negative application requests against each ZTNA policy”.

B:

“Rehearse logging, alert propagation and containment on a nonproduction test endpoint” checks a different ongoing risk rather than the reported failure: a managed endpoint has a valid security posture tag but an administrator assumes that tag alone is sufficient to authorize every private application. The relevant mechanism is a posture attribute is an input to an access decision, not a blanket network authorization. The directly matched preventive control is “Validate positive and negative application requests against each ZTNA policy”.

D:

“Include negative device-posture cases before deploying security-tag firewall policies” checks a different ongoing risk rather than the reported failure: a managed endpoint has a valid security posture tag but an administrator assumes that tag alone is sufficient to authorize every private application. The relevant mechanism is a posture attribute is an input to an access decision, not a blanket network authorization. The directly matched preventive control is “Validate positive and negative application requests against each ZTNA policy”.

Question 373

At fictional Granite Distribution, an endpoint security engineer responsible for warehouse endpoints is reviewing EMS, endpoint and secure-access troubleshooting during a supervised production migration (FCT-7.4-4.2-094). The observed endpoint management issue is: An endpoint protection package is upgraded but the old custom antivirus exclusions were not preserved and a business application is blocked. 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. Noncompliant test endpoints remain denied until the relevant verified posture requirements are met.
  3. The authorized application functions while global malware controls and unrelated detections remain active.
  4. The endpoint Web Filter event identifies the actual blocking control and gateway traffic is not misattributed.

Explanation

Correct Answer

C:

This is the direct verification evidence: The authorized application functions while global malware controls and unrelated detections remain active. It supports the engineering change to review actual effective malware profile and approved exceptions after client upgrade, restoring only justified settings. The relevant principle is that client upgrades must be validated against centrally assigned endpoint protection profile behavior.

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 endpoint protection package is upgraded but the old custom antivirus exclusions were not preserved and a business application is blocked. The specific reason is client upgrades must be validated against centrally assigned endpoint protection profile behavior. The applicable verification is “The authorized application functions while global malware controls and unrelated detections remain active”.

B:

Evidence that “Noncompliant test endpoints remain denied until the relevant verified posture requirements are met” occurred would not by itself establish resolution of the reported problem: an endpoint protection package is upgraded but the old custom antivirus exclusions were not preserved and a business application is blocked. The specific reason is client upgrades must be validated against centrally assigned endpoint protection profile behavior. The applicable verification is “The authorized application functions while global malware controls and unrelated detections remain active”.

D:

Evidence that “The endpoint Web Filter event identifies the actual blocking control and gateway traffic is not misattributed” occurred would not by itself establish resolution of the reported problem: an endpoint protection package is upgraded but the old custom antivirus exclusions were not preserved and a business application is blocked. The specific reason is client upgrades must be validated against centrally assigned endpoint protection profile behavior. The applicable verification is “The authorized application functions while global malware controls and unrelated detections remain active”.

Question 374

At fictional Granite Distribution, an endpoint security engineer responsible for warehouse endpoints is reviewing EMS, endpoint and secure-access troubleshooting during a supervised production migration (FCT-7.4-4.2-094). The observed endpoint management issue is: An endpoint protection package is upgraded but the old custom antivirus exclusions were not preserved and a business application is blocked. Which recurring preventive or detective safeguard would best reduce recurrence?

  1. Test representative business applications after FortiClient and policy version changes.
  2. Reconcile required profile features against installed modules during each software rollout.
  3. Include agent connection and certificate status in protected application support checklists.
  4. Check trusted certificates against expected hostnames during EMS domain changes.

Explanation

Correct Answer

A:

The recurring safeguard is to test representative business applications after FortiClient and policy version changes. It mitigates the actual failure: An endpoint protection package is upgraded but the old custom antivirus exclusions were not preserved and a business application is blocked. A suitable correction is to review actual effective malware profile and approved exceptions after client upgrade, restoring only justified settings; its proof is that the authorized application functions while global malware controls and unrelated detections remain active.

Incorrect Answers

B:

“Reconcile required profile features against installed modules during each software rollout” checks a different ongoing risk rather than the reported failure: an endpoint protection package is upgraded but the old custom antivirus exclusions were not preserved and a business application is blocked. The relevant mechanism is client upgrades must be validated against centrally assigned endpoint protection profile behavior. The directly matched preventive control is “Test representative business applications after FortiClient and policy version changes”.

C:

“Include agent connection and certificate status in protected application support checklists” checks a different ongoing risk rather than the reported failure: an endpoint protection package is upgraded but the old custom antivirus exclusions were not preserved and a business application is blocked. The relevant mechanism is client upgrades must be validated against centrally assigned endpoint protection profile behavior. The directly matched preventive control is “Test representative business applications after FortiClient and policy version changes”.

D:

“Check trusted certificates against expected hostnames during EMS domain changes” checks a different ongoing risk rather than the reported failure: an endpoint protection package is upgraded but the old custom antivirus exclusions were not preserved and a business application is blocked. The relevant mechanism is client upgrades must be validated against centrally assigned endpoint protection profile behavior. The directly matched preventive control is “Test representative business applications after FortiClient and policy version changes”.

Question 375

At fictional Granite Distribution, an endpoint security engineer responsible for warehouse endpoints is reviewing EMS, endpoint and secure-access troubleshooting during a supervised production migration (FCT-7.4-4.2-094). The observed endpoint management issue is: An endpoint protection package is upgraded but the old custom antivirus exclusions were not preserved and a business application is blocked. Which endpoint-management or security principle best explains the proper response?

  1. Trusted certificate identity must follow the advertised management server name.
  2. TLS authentication can fail due to client time or certificate validity independent of identity credentials.
  3. Client upgrades must be validated against centrally assigned endpoint protection profile behavior.
  4. Endpoint policy configuration cannot enforce a feature absent from the installed supported agent.

Explanation

Correct Answer

C:

The governing principle is: Client upgrades must be validated against centrally assigned endpoint protection profile behavior. Here the appropriate correction is to review actual effective malware profile and approved exceptions after client upgrade, restoring only justified settings. Confirmation would be that the authorized application functions while global malware controls and unrelated detections remain active.

Incorrect Answers

A:

“Trusted certificate identity must follow the advertised management server name” is not the controlling explanation for an endpoint protection package is upgraded but the old custom antivirus exclusions were not preserved and a business application is blocked. The cited causal relationship is client upgrades must be validated against centrally assigned endpoint protection profile behavior. The matching answer is “Client upgrades must be validated against centrally assigned endpoint protection profile behavior”.

B:

“TLS authentication can fail due to client time or certificate validity independent of identity credentials” is not the controlling explanation for an endpoint protection package is upgraded but the old custom antivirus exclusions were not preserved and a business application is blocked. The cited causal relationship is client upgrades must be validated against centrally assigned endpoint protection profile behavior. The matching answer is “Client upgrades must be validated against centrally assigned endpoint protection profile behavior”.

D:

“Endpoint policy configuration cannot enforce a feature absent from the installed supported agent” is not the controlling explanation for an endpoint protection package is upgraded but the old custom antivirus exclusions were not preserved and a business application is blocked. The cited causal relationship is client upgrades must be validated against centrally assigned endpoint protection profile behavior. The matching answer is “Client upgrades must be validated against centrally assigned endpoint protection profile behavior”.

Question 376

At fictional Granite Distribution, an endpoint security engineer responsible for warehouse endpoints is reviewing EMS, endpoint and secure-access troubleshooting during a supervised production migration (FCT-7.4-4.2-094). The observed endpoint management issue is: An endpoint protection package is upgraded but the old custom antivirus exclusions were not preserved and a business application is blocked. Which corrective engineering action best addresses the specific problem?

  1. Use the supported EMS host diagnostic and service logs or CLI tools to investigate the failed management interface.
  2. Restore narrowly scoped EMS transport in the relevant host or network policy without disabling broad protection.
  3. Allow supported resynchronization after reconnect and compare current versus pending policy version status.
  4. Review actual effective malware profile and approved exceptions after client upgrade, restoring only justified settings.

Explanation

Correct Answer

D:

The targeted correction is to review actual effective malware profile and approved exceptions after client upgrade, restoring only justified settings. The diagnosed issue is: An endpoint protection package is upgraded but the old custom antivirus exclusions were not preserved and a business application is blocked. Evidence of success is: The authorized application functions while global malware controls and unrelated detections remain active. The underlying endpoint-security principle is that client upgrades must be validated against centrally assigned endpoint protection profile behavior.

Incorrect Answers

A:

“Use the supported EMS host diagnostic and service logs or CLI tools to investigate the failed management interface” would address a different implementation objective; the stated problem is an endpoint protection package is upgraded but the old custom antivirus exclusions were not preserved and a business application is blocked. The actual control boundary is client upgrades must be validated against centrally assigned endpoint protection profile behavior. The directly responsive action is “Review actual effective malware profile and approved exceptions after client upgrade, restoring only justified settings”.

B:

“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 endpoint protection package is upgraded but the old custom antivirus exclusions were not preserved and a business application is blocked. The actual control boundary is client upgrades must be validated against centrally assigned endpoint protection profile behavior. The directly responsive action is “Review actual effective malware profile and approved exceptions after client upgrade, restoring only justified settings”.

C:

“Allow supported resynchronization after reconnect and compare current versus pending policy version status” would address a different implementation objective; the stated problem is an endpoint protection package is upgraded but the old custom antivirus exclusions were not preserved and a business application is blocked. The actual control boundary is client upgrades must be validated against centrally assigned endpoint protection profile behavior. The directly responsive action is “Review actual effective malware profile and approved exceptions after client upgrade, restoring only justified settings”.

Question 377

At fictional Northgate Security, an endpoint security engineer responsible for field responders is reviewing EMS, endpoint and secure-access troubleshooting during a device support triage (FCT-7.4-4.1-095). The observed endpoint management issue is: A ZTNA device tag disappears after a policy change and support resets the FortiGate without inspecting the EMS rule evaluation. Which recurring preventive or detective safeguard would best reduce recurrence?

  1. Capture endpoint state, rule evaluation and gateway tag membership during ZTNA failures.
  2. Monitor last agent check-in and policy application timestamps together.
  3. Display and review last-contact age on endpoint risk dashboards.
  4. Review access, retention and sharing of EMS and FortiClient support bundles.

Explanation

Correct Answer

A:

The recurring safeguard is to capture endpoint state, rule evaluation and gateway tag membership during ZTNA failures. It mitigates the actual failure: A ZTNA device tag disappears after a policy change and support resets the FortiGate without inspecting the EMS rule evaluation. A suitable correction is to review the endpoint's posture attributes, EMS tag rule results and Fabric synchronization state; its proof is that the missing tag is traced to a rule mismatch and returns after approved condition correction.

Incorrect Answers

B:

“Monitor last agent check-in and policy application timestamps together” checks a different ongoing risk rather than the reported failure: a ZTNA device tag disappears after a policy change and support resets the FortiGate without inspecting the EMS rule evaluation. The relevant mechanism is posture classification problems can originate at the endpoint or EMS before reaching the gateway. The directly matched preventive control is “Capture endpoint state, rule evaluation and gateway tag membership during ZTNA failures”.

C:

“Display and review last-contact age on endpoint risk dashboards” checks a different ongoing risk rather than the reported failure: a ZTNA device tag disappears after a policy change and support resets the FortiGate without inspecting the EMS rule evaluation. The relevant mechanism is posture classification problems can originate at the endpoint or EMS before reaching the gateway. The directly matched preventive control is “Capture endpoint state, rule evaluation and gateway tag membership during ZTNA failures”.

D:

“Review access, retention and sharing of EMS and FortiClient support bundles” checks a different ongoing risk rather than the reported failure: a ZTNA device tag disappears after a policy change and support resets the FortiGate without inspecting the EMS rule evaluation. The relevant mechanism is posture classification problems can originate at the endpoint or EMS before reaching the gateway. The directly matched preventive control is “Capture endpoint state, rule evaluation and gateway tag membership during ZTNA failures”.

Question 378

At fictional Northgate Security, an endpoint security engineer responsible for field responders is reviewing EMS, endpoint and secure-access troubleshooting during a device support triage (FCT-7.4-4.1-095). The observed endpoint management issue is: A ZTNA device tag disappears after a policy change and support resets the FortiGate without inspecting the EMS rule evaluation. Which endpoint-management or security principle best explains the proper response?

  1. Management telemetry loss and ordinary client network reachability are independent symptoms.
  2. Similar warning messages require scope comparison before attributing an issue to shared infrastructure.
  3. Posture classification problems can originate at the endpoint or EMS before reaching the gateway.
  4. Client upgrades must be validated against centrally assigned endpoint protection profile behavior.

Explanation

Correct Answer

C:

The governing principle is: Posture classification problems can originate at the endpoint or EMS before reaching the gateway. Here the appropriate correction is to review the endpoint's posture attributes, EMS tag rule results and Fabric synchronization state. Confirmation would be that the missing tag is traced to a rule mismatch and returns after approved condition correction.

Incorrect Answers

A:

“Management telemetry loss and ordinary client network reachability are independent symptoms” is not the controlling explanation for a ZTNA device tag disappears after a policy change and support resets the FortiGate without inspecting the EMS rule evaluation. The cited causal relationship is posture classification problems can originate at the endpoint or EMS before reaching the gateway. The matching answer is “Posture classification problems can originate at the endpoint or EMS before reaching the gateway”.

B:

“Similar warning messages require scope comparison before attributing an issue to shared infrastructure” is not the controlling explanation for a ZTNA device tag disappears after a policy change and support resets the FortiGate without inspecting the EMS rule evaluation. The cited causal relationship is posture classification problems can originate at the endpoint or EMS before reaching the gateway. The matching answer is “Posture classification problems can originate at the endpoint or EMS before reaching the gateway”.

D:

“Client upgrades must be validated against centrally assigned endpoint protection profile behavior” is not the controlling explanation for a ZTNA device tag disappears after a policy change and support resets the FortiGate without inspecting the EMS rule evaluation. The cited causal relationship is posture classification problems can originate at the endpoint or EMS before reaching the gateway. The matching answer is “Posture classification problems can originate at the endpoint or EMS before reaching the gateway”.

Question 379

At fictional Northgate Security, an endpoint security engineer responsible for field responders is reviewing EMS, endpoint and secure-access troubleshooting during a device support triage (FCT-7.4-4.1-095). The observed endpoint management issue is: A ZTNA device tag disappears after a policy change and support resets the FortiGate without inspecting the EMS rule evaluation. Which observation best verifies that the proposed correction worked?

  1. Agent registration stabilizes after compatibility correction while unaffected clients retain service.
  2. Freshly connected agents show current state while stale devices are explicitly treated as unevaluated.
  3. Monitoring searches and client telemetry recover after approved server resource remediation.
  4. The missing tag is traced to a rule mismatch and returns after approved condition correction.

Explanation

Correct Answer

D:

This is the direct verification evidence: The missing tag is traced to a rule mismatch and returns after approved condition correction. It supports the engineering change to review the endpoint's posture attributes, EMS tag rule results and Fabric synchronization state. The relevant principle is that posture classification problems can originate at the endpoint or EMS before reaching the gateway.

Incorrect Answers

A:

Evidence that “Agent registration stabilizes after compatibility correction while unaffected clients retain service” occurred would not by itself establish resolution of the reported problem: a ZTNA device tag disappears after a policy change and support resets the FortiGate without inspecting the EMS rule evaluation. The specific reason is posture classification problems can originate at the endpoint or EMS before reaching the gateway. The applicable verification is “The missing tag is traced to a rule mismatch and returns after approved condition correction”.

B:

Evidence that “Freshly connected agents show current state while stale devices are explicitly treated as unevaluated” occurred would not by itself establish resolution of the reported problem: a ZTNA device tag disappears after a policy change and support resets the FortiGate without inspecting the EMS rule evaluation. The specific reason is posture classification problems can originate at the endpoint or EMS before reaching the gateway. The applicable verification is “The missing tag is traced to a rule mismatch and returns after approved condition correction”.

C:

Evidence that “Monitoring searches and client telemetry recover after approved server resource remediation” occurred would not by itself establish resolution of the reported problem: a ZTNA device tag disappears after a policy change and support resets the FortiGate without inspecting the EMS rule evaluation. The specific reason is posture classification problems can originate at the endpoint or EMS before reaching the gateway. The applicable verification is “The missing tag is traced to a rule mismatch and returns after approved condition correction”.

Question 380

At fictional Northgate Security, an endpoint security engineer responsible for field responders is reviewing EMS, endpoint and secure-access troubleshooting during a device support triage (FCT-7.4-4.1-095). The observed endpoint management issue is: A ZTNA device tag disappears after a policy change and support resets the FortiGate without inspecting the EMS rule evaluation. Which corrective engineering action best addresses the specific problem?

  1. Review the endpoint's posture attributes, EMS tag rule results and Fabric synchronization state.
  2. Check EMS disk utilization, database health and relevant log retention before altering endpoint profiles.
  3. Recheck the exact EMS posture predicates, endpoint scan state and FortiGate policy outcome together.
  4. Inspect software deployment status, group assignment, device reachability and permissions in separate stages.

Explanation

Correct Answer

A:

The targeted correction is to review the endpoint's posture attributes, EMS tag rule results and Fabric synchronization state. The diagnosed issue is: A ZTNA device tag disappears after a policy change and support resets the FortiGate without inspecting the EMS rule evaluation. Evidence of success is: The missing tag is traced to a rule mismatch and returns after approved condition correction. The underlying endpoint-security principle is that posture classification problems can originate at the endpoint or EMS before reaching the gateway.

Incorrect Answers

B:

“Check EMS disk utilization, database health and relevant log retention before altering endpoint profiles” would address a different implementation objective; the stated problem is a ZTNA device tag disappears after a policy change and support resets the FortiGate without inspecting the EMS rule evaluation. The actual control boundary is posture classification problems can originate at the endpoint or EMS before reaching the gateway. The directly responsive action is “Review the endpoint's posture attributes, EMS tag rule results and Fabric synchronization state”.

C:

“Recheck the exact EMS posture predicates, endpoint scan state and FortiGate policy outcome together” would address a different implementation objective; the stated problem is a ZTNA device tag disappears after a policy change and support resets the FortiGate without inspecting the EMS rule evaluation. The actual control boundary is posture classification problems can originate at the endpoint or EMS before reaching the gateway. The directly responsive action is “Review the endpoint's posture attributes, EMS tag rule results and Fabric synchronization state”.

D:

“Inspect software deployment status, group assignment, device reachability and permissions in separate stages” would address a different implementation objective; the stated problem is a ZTNA device tag disappears after a policy change and support resets the FortiGate without inspecting the EMS rule evaluation. The actual control boundary is posture classification problems can originate at the endpoint or EMS before reaching the gateway. The directly responsive action is “Review the endpoint's posture attributes, EMS tag rule results and Fabric synchronization state”.

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