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 59

Question 580

At fictional Quayside Education, an endpoint security engineer responsible for instructor tablets is reviewing FortiGate integration, posture tags, ZTNA and containment during a supervised production migration (FCT-7.4-3.3-145). The observed endpoint management issue is: An endpoint cannot connect to its ZTNA destination and administrators replace all SSL settings without checking whether the desired posture tag is present. Which recurring preventive or detective safeguard would best reduce recurrence?

  1. Include backend service health and route tests when commissioning ZTNA applications.
  2. Audit tag coverage and false negatives after endpoint operating system upgrades.
  3. Test endpoint posture transitions through EMS and FortiGate after connector maintenance.
  4. Include applied tag and rule-match checks in ZTNA incident troubleshooting.

Explanation

Correct Answer

D:

The recurring safeguard is to include applied tag and rule-match checks in ZTNA incident troubleshooting. It mitigates the actual failure: An endpoint cannot connect to its ZTNA destination and administrators replace all SSL settings without checking whether the desired posture tag is present. A suitable correction is to compare FortiClient enrollment, effective posture tags, destination profile and gateway policy match first; its proof is that diagnostics identify a missing policy tag and access succeeds after authorized posture correction.

Incorrect Answers

A:

“Include backend service health and route tests when commissioning ZTNA applications” checks a different ongoing risk rather than the reported failure: an endpoint cannot connect to its ZTNA destination and administrators replace all SSL settings without checking whether the desired posture tag is present. The relevant mechanism is zTNA denial can arise from management posture and authorization rather than transport encryption. The directly matched preventive control is “Include applied tag and rule-match checks in ZTNA incident troubleshooting”.

B:

“Audit tag coverage and false negatives after endpoint operating system upgrades” checks a different ongoing risk rather than the reported failure: an endpoint cannot connect to its ZTNA destination and administrators replace all SSL settings without checking whether the desired posture tag is present. The relevant mechanism is zTNA denial can arise from management posture and authorization rather than transport encryption. The directly matched preventive control is “Include applied tag and rule-match checks in ZTNA incident troubleshooting”.

C:

“Test endpoint posture transitions through EMS and FortiGate after connector maintenance” checks a different ongoing risk rather than the reported failure: an endpoint cannot connect to its ZTNA destination and administrators replace all SSL settings without checking whether the desired posture tag is present. The relevant mechanism is zTNA denial can arise from management posture and authorization rather than transport encryption. The directly matched preventive control is “Include applied tag and rule-match checks in ZTNA incident troubleshooting”.

Question 581

At fictional Maple Housing, an endpoint security engineer responsible for facilities support is reviewing endpoint provisioning, security modules and profile delivery during a fleet compliance inspection (FCT-7.4-2.2-146). The observed endpoint management issue is: An enterprise copies a laboratory default malware profile to production without evaluating different risk exposures. Which corrective engineering action best addresses the specific problem?

  1. Add the intended profile to an applicable EMS endpoint policy and ensure the policy targets the correct group.
  2. Place the endpoint in the appropriate EMS group and verify the effective policy and feature profiles after movement.
  3. Create appropriate distinct feature profiles and bind them to the correct endpoint policies.
  4. Build product-supported malware protection profiles based on the approved endpoint risk and software environment.

Explanation

Correct Answer

D:

The targeted correction is to build product-supported malware protection profiles based on the approved endpoint risk and software environment. The diagnosed issue is: An enterprise copies a laboratory default malware profile to production without evaluating different risk exposures. Evidence of success is: Production pilot endpoints apply the desired protection features without indiscriminate test exclusions. The underlying endpoint-security principle is that default profiles should be reviewed against deployment requirements rather than treated as universal production policy.

Incorrect Answers

A:

“Add the intended profile to an applicable EMS endpoint policy and ensure the policy targets the correct group” would address a different implementation objective; the stated problem is an enterprise copies a laboratory default malware profile to production without evaluating different risk exposures. The actual control boundary is default profiles should be reviewed against deployment requirements rather than treated as universal production policy. The directly responsive action is “Build product-supported malware protection profiles based on the approved endpoint risk and software environment”.

B:

“Place the endpoint in the appropriate EMS group and verify the effective policy and feature profiles after movement” would address a different implementation objective; the stated problem is an enterprise copies a laboratory default malware profile to production without evaluating different risk exposures. The actual control boundary is default profiles should be reviewed against deployment requirements rather than treated as universal production policy. The directly responsive action is “Build product-supported malware protection profiles based on the approved endpoint risk and software environment”.

C:

“Create appropriate distinct feature profiles and bind them to the correct endpoint policies” would address a different implementation objective; the stated problem is an enterprise copies a laboratory default malware profile to production without evaluating different risk exposures. The actual control boundary is default profiles should be reviewed against deployment requirements rather than treated as universal production policy. The directly responsive action is “Build product-supported malware protection profiles based on the approved endpoint risk and software environment”.

Question 582

At fictional Maple Housing, an endpoint security engineer responsible for facilities support is reviewing endpoint provisioning, security modules and profile delivery during a fleet compliance inspection (FCT-7.4-2.2-146). The observed endpoint management issue is: An enterprise copies a laboratory default malware profile to production without evaluating different risk exposures. Which observation best verifies that the proposed correction worked?

  1. Only the intended user/device population registers under the approved policy scope.
  2. After normal supported synchronization the endpoint reports the intended scan settings.
  3. Production pilot endpoints apply the desired protection features without indiscriminate test exclusions.
  4. A connected endpoint receives the revised web filter behavior and EMS reports its applied policy.

Explanation

Correct Answer

C:

This is the direct verification evidence: Production pilot endpoints apply the desired protection features without indiscriminate test exclusions. It supports the engineering change to build product-supported malware protection profiles based on the approved endpoint risk and software environment. The relevant principle is that default profiles should be reviewed against deployment requirements rather than treated as universal production policy.

Incorrect Answers

A:

Evidence that “Only the intended user/device population registers under the approved policy scope” occurred would not by itself establish resolution of the reported problem: an enterprise copies a laboratory default malware profile to production without evaluating different risk exposures. The specific reason is default profiles should be reviewed against deployment requirements rather than treated as universal production policy. The applicable verification is “Production pilot endpoints apply the desired protection features without indiscriminate test exclusions”.

B:

Evidence that “After normal supported synchronization the endpoint reports the intended scan settings” occurred would not by itself establish resolution of the reported problem: an enterprise copies a laboratory default malware profile to production without evaluating different risk exposures. The specific reason is default profiles should be reviewed against deployment requirements rather than treated as universal production policy. The applicable verification is “Production pilot endpoints apply the desired protection features without indiscriminate test exclusions”.

D:

Evidence that “A connected endpoint receives the revised web filter behavior and EMS reports its applied policy” occurred would not by itself establish resolution of the reported problem: an enterprise copies a laboratory default malware profile to production without evaluating different risk exposures. The specific reason is default profiles should be reviewed against deployment requirements rather than treated as universal production policy. The applicable verification is “Production pilot endpoints apply the desired protection features without indiscriminate test exclusions”.

Question 583

At fictional Maple Housing, an endpoint security engineer responsible for facilities support is reviewing endpoint provisioning, security modules and profile delivery during a fleet compliance inspection (FCT-7.4-2.2-146). The observed endpoint management issue is: An enterprise copies a laboratory default malware profile to production without evaluating different risk exposures. Which endpoint-management or security principle best explains the proper response?

  1. Bulk endpoint installer distribution can affect site capacity separately from normal security telemetry.
  2. Profile-based policy exceptions should be scoped to the smallest affected user or resource population.
  3. Moving a device between groups can change its policy and security-profile assignments.
  4. Default profiles should be reviewed against deployment requirements rather than treated as universal production policy.

Explanation

Correct Answer

D:

The governing principle is: Default profiles should be reviewed against deployment requirements rather than treated as universal production policy. Here the appropriate correction is to build product-supported malware protection profiles based on the approved endpoint risk and software environment. Confirmation would be that production pilot endpoints apply the desired protection features without indiscriminate test exclusions.

Incorrect Answers

A:

“Bulk endpoint installer distribution can affect site capacity separately from normal security telemetry” is not the controlling explanation for an enterprise copies a laboratory default malware profile to production without evaluating different risk exposures. The cited causal relationship is default profiles should be reviewed against deployment requirements rather than treated as universal production policy. The matching answer is “Default profiles should be reviewed against deployment requirements rather than treated as universal production policy”.

B:

“Profile-based policy exceptions should be scoped to the smallest affected user or resource population” is not the controlling explanation for an enterprise copies a laboratory default malware profile to production without evaluating different risk exposures. The cited causal relationship is default profiles should be reviewed against deployment requirements rather than treated as universal production policy. The matching answer is “Default profiles should be reviewed against deployment requirements rather than treated as universal production policy”.

C:

“Moving a device between groups can change its policy and security-profile assignments” is not the controlling explanation for an enterprise copies a laboratory default malware profile to production without evaluating different risk exposures. The cited causal relationship is default profiles should be reviewed against deployment requirements rather than treated as universal production policy. The matching answer is “Default profiles should be reviewed against deployment requirements rather than treated as universal production policy”.

Question 584

At fictional Maple Housing, an endpoint security engineer responsible for facilities support is reviewing endpoint provisioning, security modules and profile delivery during a fleet compliance inspection (FCT-7.4-2.2-146). The observed endpoint management issue is: An enterprise copies a laboratory default malware profile to production without evaluating different risk exposures. Which recurring preventive or detective safeguard would best reduce recurrence?

  1. Review inherited and customized profile differences before promoting laboratory settings.
  2. Include representative allowed and blocked URLs in each group policy test.
  3. Monitor time from policy publication to successful endpoint application.
  4. Record object identifiers and group-policy references in change tickets.

Explanation

Correct Answer

A:

The recurring safeguard is to review inherited and customized profile differences before promoting laboratory settings. It mitigates the actual failure: An enterprise copies a laboratory default malware profile to production without evaluating different risk exposures. A suitable correction is to build product-supported malware protection profiles based on the approved endpoint risk and software environment; its proof is that production pilot endpoints apply the desired protection features without indiscriminate test exclusions.

Incorrect Answers

B:

“Include representative allowed and blocked URLs in each group policy test” checks a different ongoing risk rather than the reported failure: an enterprise copies a laboratory default malware profile to production without evaluating different risk exposures. The relevant mechanism is default profiles should be reviewed against deployment requirements rather than treated as universal production policy. The directly matched preventive control is “Review inherited and customized profile differences before promoting laboratory settings”.

C:

“Monitor time from policy publication to successful endpoint application” checks a different ongoing risk rather than the reported failure: an enterprise copies a laboratory default malware profile to production without evaluating different risk exposures. The relevant mechanism is default profiles should be reviewed against deployment requirements rather than treated as universal production policy. The directly matched preventive control is “Review inherited and customized profile differences before promoting laboratory settings”.

D:

“Record object identifiers and group-policy references in change tickets” checks a different ongoing risk rather than the reported failure: an enterprise copies a laboratory default malware profile to production without evaluating different risk exposures. The relevant mechanism is default profiles should be reviewed against deployment requirements rather than treated as universal production policy. The directly matched preventive control is “Review inherited and customized profile differences before promoting laboratory settings”.

Question 585

At fictional Granite Distribution, an endpoint security engineer responsible for warehouse endpoints is reviewing FortiGate integration, posture tags, ZTNA and containment during a managed endpoint onboarding exercise (FCT-7.4-3.2-147). The observed endpoint management issue is: An analyst sees a malware event from an endpoint but assumes every security indicator warrants full network isolation without assessing confidence. Which observation best verifies that the proposed correction worked?

  1. The repaired endpoint is removed from quarantine and resumes only approved network connectivity.
  2. Access changes after posture reevaluation and stale devices receive the intended restricted outcome.
  3. Confirmed high-risk endpoints are contained while benign controlled events follow appropriate handling.
  4. The incident and quarantine logs identify the same intended endpoint ID and correct owner.

Explanation

Correct Answer

C:

This is the direct verification evidence: Confirmed high-risk endpoints are contained while benign controlled events follow appropriate handling. It supports the engineering change to apply the documented incident severity and authorization criteria before using disruptive endpoint quarantine. The relevant principle is that automated response should use evidence and risk thresholds rather than indiscriminate disruption.

Incorrect Answers

A:

Evidence that “The repaired endpoint is removed from quarantine and resumes only approved network connectivity” occurred would not by itself establish resolution of the reported problem: an analyst sees a malware event from an endpoint but assumes every security indicator warrants full network isolation without assessing confidence. The specific reason is automated response should use evidence and risk thresholds rather than indiscriminate disruption. The applicable verification is “Confirmed high-risk endpoints are contained while benign controlled events follow appropriate handling”.

B:

Evidence that “Access changes after posture reevaluation and stale devices receive the intended restricted outcome” occurred would not by itself establish resolution of the reported problem: an analyst sees a malware event from an endpoint but assumes every security indicator warrants full network isolation without assessing confidence. The specific reason is automated response should use evidence and risk thresholds rather than indiscriminate disruption. The applicable verification is “Confirmed high-risk endpoints are contained while benign controlled events follow appropriate handling”.

D:

Evidence that “The incident and quarantine logs identify the same intended endpoint ID and correct owner” occurred would not by itself establish resolution of the reported problem: an analyst sees a malware event from an endpoint but assumes every security indicator warrants full network isolation without assessing confidence. The specific reason is automated response should use evidence and risk thresholds rather than indiscriminate disruption. The applicable verification is “Confirmed high-risk endpoints are contained while benign controlled events follow appropriate handling”.

Question 586

At fictional Granite Distribution, an endpoint security engineer responsible for warehouse endpoints is reviewing FortiGate integration, posture tags, ZTNA and containment during a managed endpoint onboarding exercise (FCT-7.4-3.2-147). The observed endpoint management issue is: An analyst sees a malware event from an endpoint but assumes every security indicator warrants full network isolation without assessing confidence. Which endpoint-management or security principle best explains the proper response?

  1. Identity and device trust are complementary access signals rather than interchangeable checks.
  2. Automated response should use evidence and risk thresholds rather than indiscriminate disruption.
  3. Application proxy policy must be tested at its actual enforcement point, not an unrelated direct route.
  4. Incident detection and endpoint containment are separate actions that require configured enforcement.

Explanation

Correct Answer

B:

The governing principle is: Automated response should use evidence and risk thresholds rather than indiscriminate disruption. Here the appropriate correction is to apply the documented incident severity and authorization criteria before using disruptive endpoint quarantine. Confirmation would be that confirmed high-risk endpoints are contained while benign controlled events follow appropriate handling.

Incorrect Answers

A:

“Identity and device trust are complementary access signals rather than interchangeable checks” is not the controlling explanation for an analyst sees a malware event from an endpoint but assumes every security indicator warrants full network isolation without assessing confidence. The cited causal relationship is automated response should use evidence and risk thresholds rather than indiscriminate disruption. The matching answer is “Automated response should use evidence and risk thresholds rather than indiscriminate disruption”.

C:

“Application proxy policy must be tested at its actual enforcement point, not an unrelated direct route” is not the controlling explanation for an analyst sees a malware event from an endpoint but assumes every security indicator warrants full network isolation without assessing confidence. The cited causal relationship is automated response should use evidence and risk thresholds rather than indiscriminate disruption. The matching answer is “Automated response should use evidence and risk thresholds rather than indiscriminate disruption”.

D:

“Incident detection and endpoint containment are separate actions that require configured enforcement” is not the controlling explanation for an analyst sees a malware event from an endpoint but assumes every security indicator warrants full network isolation without assessing confidence. The cited causal relationship is automated response should use evidence and risk thresholds rather than indiscriminate disruption. The matching answer is “Automated response should use evidence and risk thresholds rather than indiscriminate disruption”.

Question 587

At fictional Granite Distribution, an endpoint security engineer responsible for warehouse endpoints is reviewing FortiGate integration, posture tags, ZTNA and containment during a managed endpoint onboarding exercise (FCT-7.4-3.2-147). The observed endpoint management issue is: An analyst sees a malware event from an endpoint but assumes every security indicator warrants full network isolation without assessing confidence. Which corrective engineering action best addresses the specific problem?

  1. Verify connector synchronization and policy object membership for the current endpoint posture.
  2. Apply the documented incident severity and authorization criteria before using disruptive endpoint quarantine.
  3. Restrict EMS quarantine and release privileges to appropriate authorized responder roles with auditability.
  4. Validate the documented Security Fabric topology and authorized EMS integration for participating devices.

Explanation

Correct Answer

B:

The targeted correction is to apply the documented incident severity and authorization criteria before using disruptive endpoint quarantine. The diagnosed issue is: An analyst sees a malware event from an endpoint but assumes every security indicator warrants full network isolation without assessing confidence. Evidence of success is: Confirmed high-risk endpoints are contained while benign controlled events follow appropriate handling. The underlying endpoint-security principle is that automated response should use evidence and risk thresholds rather than indiscriminate disruption.

Incorrect Answers

A:

“Verify connector synchronization and policy object membership for the current endpoint posture” would address a different implementation objective; the stated problem is an analyst sees a malware event from an endpoint but assumes every security indicator warrants full network isolation without assessing confidence. The actual control boundary is automated response should use evidence and risk thresholds rather than indiscriminate disruption. The directly responsive action is “Apply the documented incident severity and authorization criteria before using disruptive endpoint quarantine”.

C:

“Restrict EMS quarantine and release privileges to appropriate authorized responder roles with auditability” would address a different implementation objective; the stated problem is an analyst sees a malware event from an endpoint but assumes every security indicator warrants full network isolation without assessing confidence. The actual control boundary is automated response should use evidence and risk thresholds rather than indiscriminate disruption. The directly responsive action is “Apply the documented incident severity and authorization criteria before using disruptive endpoint quarantine”.

D:

“Validate the documented Security Fabric topology and authorized EMS integration for participating devices” would address a different implementation objective; the stated problem is an analyst sees a malware event from an endpoint but assumes every security indicator warrants full network isolation without assessing confidence. The actual control boundary is automated response should use evidence and risk thresholds rather than indiscriminate disruption. The directly responsive action is “Apply the documented incident severity and authorization criteria before using disruptive endpoint quarantine”.

Question 588

At fictional Granite Distribution, an endpoint security engineer responsible for warehouse endpoints is reviewing FortiGate integration, posture tags, ZTNA and containment during a managed endpoint onboarding exercise (FCT-7.4-3.2-147). The observed endpoint management issue is: An analyst sees a malware event from an endpoint but assumes every security indicator warrants full network isolation without assessing confidence. Which recurring preventive or detective safeguard would best reduce recurrence?

  1. Review quarantines for false positives and refine trigger conditions with security owners.
  2. Confirm authorization and connector status on both ends whenever integrating a new FortiGate.
  3. Test rule ordering and unexpected catch-all access after FortiGate policy changes.
  4. Rehearse logging, alert propagation and containment on a nonproduction test endpoint.

Explanation

Correct Answer

A:

The recurring safeguard is to review quarantines for false positives and refine trigger conditions with security owners. It mitigates the actual failure: An analyst sees a malware event from an endpoint but assumes every security indicator warrants full network isolation without assessing confidence. A suitable correction is to apply the documented incident severity and authorization criteria before using disruptive endpoint quarantine; its proof is that confirmed high-risk endpoints are contained while benign controlled events follow appropriate handling.

Incorrect Answers

B:

“Confirm authorization and connector status on both ends whenever integrating a new FortiGate” checks a different ongoing risk rather than the reported failure: an analyst sees a malware event from an endpoint but assumes every security indicator warrants full network isolation without assessing confidence. The relevant mechanism is automated response should use evidence and risk thresholds rather than indiscriminate disruption. The directly matched preventive control is “Review quarantines for false positives and refine trigger conditions with security owners”.

C:

“Test rule ordering and unexpected catch-all access after FortiGate policy changes” checks a different ongoing risk rather than the reported failure: an analyst sees a malware event from an endpoint but assumes every security indicator warrants full network isolation without assessing confidence. The relevant mechanism is automated response should use evidence and risk thresholds rather than indiscriminate disruption. The directly matched preventive control is “Review quarantines for false positives and refine trigger conditions with security owners”.

D:

“Rehearse logging, alert propagation and containment on a nonproduction test endpoint” checks a different ongoing risk rather than the reported failure: an analyst sees a malware event from an endpoint but assumes every security indicator warrants full network isolation without assessing confidence. The relevant mechanism is automated response should use evidence and risk thresholds rather than indiscriminate disruption. The directly matched preventive control is “Review quarantines for false positives and refine trigger conditions with security owners”.

Question 589

At fictional Northgate Security, an endpoint security engineer responsible for field responders is reviewing FortiGate integration, posture tags, ZTNA and containment during a server maintenance validation (FCT-7.4-3.2-148). The observed endpoint management issue is: A SOC receives a high-confidence endpoint compromise alert but assumes marking the incident closed automatically isolates the device. Which observation best verifies that the proposed correction worked?

  1. The matching tag appears in FortiGate dynamic address or ZTNA tag inventory for a compliant endpoint.
  2. The FortiGate tag membership updates and the corresponding protected application access decision changes.
  3. The affected managed device enters quarantine and network connectivity is limited as expected.
  4. Privileged response actions are limited to approved staff and retain a traceable action history.

Explanation

Correct Answer

C:

This is the direct verification evidence: The affected managed device enters quarantine and network connectivity is limited as expected. It supports the engineering change to configure and test the supported EMS endpoint quarantine workflow for the incident conditions. The relevant principle is that incident detection and endpoint containment are separate actions that require configured enforcement.

Incorrect Answers

A:

Evidence that “The matching tag appears in FortiGate dynamic address or ZTNA tag inventory for a compliant endpoint” occurred would not by itself establish resolution of the reported problem: a SOC receives a high-confidence endpoint compromise alert but assumes marking the incident closed automatically isolates the device. The specific reason is incident detection and endpoint containment are separate actions that require configured enforcement. The applicable verification is “The affected managed device enters quarantine and network connectivity is limited as expected”.

B:

Evidence that “The FortiGate tag membership updates and the corresponding protected application access decision changes” occurred would not by itself establish resolution of the reported problem: a SOC receives a high-confidence endpoint compromise alert but assumes marking the incident closed automatically isolates the device. The specific reason is incident detection and endpoint containment are separate actions that require configured enforcement. The applicable verification is “The affected managed device enters quarantine and network connectivity is limited as expected”.

D:

Evidence that “Privileged response actions are limited to approved staff and retain a traceable action history” occurred would not by itself establish resolution of the reported problem: a SOC receives a high-confidence endpoint compromise alert but assumes marking the incident closed automatically isolates the device. The specific reason is incident detection and endpoint containment are separate actions that require configured enforcement. The applicable verification is “The affected managed device enters quarantine and network connectivity is limited as expected”.

Question 590

At fictional Northgate Security, an endpoint security engineer responsible for field responders is reviewing FortiGate integration, posture tags, ZTNA and containment during a server maintenance validation (FCT-7.4-3.2-148). The observed endpoint management issue is: A SOC receives a high-confidence endpoint compromise alert but assumes marking the incident closed automatically isolates the device. Which corrective engineering action best addresses the specific problem?

  1. Verify connector health, rule evaluation and FortiGate receipt of the intended posture tag.
  2. Configure and test the supported EMS endpoint quarantine workflow for the incident conditions.
  3. Require approved remediation evidence and a tracked EMS-administered quarantine-release decision.
  4. Validate all version-appropriate security monitoring and response prerequisites before enabling automatic containment.

Explanation

Correct Answer

B:

The targeted correction is to configure and test the supported EMS endpoint quarantine workflow for the incident conditions. The diagnosed issue is: A SOC receives a high-confidence endpoint compromise alert but assumes marking the incident closed automatically isolates the device. Evidence of success is: The affected managed device enters quarantine and network connectivity is limited as expected. The underlying endpoint-security principle is that incident detection and endpoint containment are separate actions that require configured enforcement.

Incorrect Answers

A:

“Verify connector health, rule evaluation and FortiGate receipt of the intended posture tag” would address a different implementation objective; the stated problem is a SOC receives a high-confidence endpoint compromise alert but assumes marking the incident closed automatically isolates the device. The actual control boundary is incident detection and endpoint containment are separate actions that require configured enforcement. The directly responsive action is “Configure and test the supported EMS endpoint quarantine workflow for the incident conditions”.

C:

“Require approved remediation evidence and a tracked EMS-administered quarantine-release decision” would address a different implementation objective; the stated problem is a SOC receives a high-confidence endpoint compromise alert but assumes marking the incident closed automatically isolates the device. The actual control boundary is incident detection and endpoint containment are separate actions that require configured enforcement. The directly responsive action is “Configure and test the supported EMS endpoint quarantine workflow for the incident conditions”.

D:

“Validate all version-appropriate security monitoring and response prerequisites before enabling automatic containment” would address a different implementation objective; the stated problem is a SOC receives a high-confidence endpoint compromise alert but assumes marking the incident closed automatically isolates the device. The actual control boundary is incident detection and endpoint containment are separate actions that require configured enforcement. The directly responsive action is “Configure and test the supported EMS endpoint quarantine workflow for the incident conditions”.

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