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 41

Question 400

At fictional Alder Community, an endpoint security engineer responsible for employee enrollment is reviewing EMS, endpoint and secure-access troubleshooting during a Security Fabric integration test (FCT-7.4-4.1-100). The observed endpoint management issue is: A FortiClient endpoint shows profile sync pending and an administrator keeps editing policy instead of reviewing the disconnected telemetry path. Which observation best verifies that the proposed correction worked?

  1. Monitoring searches and client telemetry recover after approved server resource remediation.
  2. The expected device identity and authorized ZTNA handshake are restored after connection prerequisites are met.
  3. The server handles staged registrations with acceptable resource levels and no destructive reset.
  4. The endpoint reconnects and receives the unchanged approved policy without speculative policy edits.

Explanation

Correct Answer

D:

This is the direct verification evidence: The endpoint reconnects and receives the unchanged approved policy without speculative policy edits. It supports the engineering change to examine current management connectivity, policy assignment and last successful client synchronization. The relevant principle is that policy synchronization depends on agent reachability and can lag even when configuration itself is valid.

Incorrect Answers

A:

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 FortiClient endpoint shows profile sync pending and an administrator keeps editing policy instead of reviewing the disconnected telemetry path. The specific reason is policy synchronization depends on agent reachability and can lag even when configuration itself is valid. The applicable verification is “The endpoint reconnects and receives the unchanged approved policy without speculative policy edits”.

B:

Evidence that “The expected device identity and authorized ZTNA handshake are restored after connection prerequisites are met” occurred would not by itself establish resolution of the reported problem: a FortiClient endpoint shows profile sync pending and an administrator keeps editing policy instead of reviewing the disconnected telemetry path. The specific reason is policy synchronization depends on agent reachability and can lag even when configuration itself is valid. The applicable verification is “The endpoint reconnects and receives the unchanged approved policy without speculative policy edits”.

C:

Evidence that “The server handles staged registrations with acceptable resource levels and no destructive reset” occurred would not by itself establish resolution of the reported problem: a FortiClient endpoint shows profile sync pending and an administrator keeps editing policy instead of reviewing the disconnected telemetry path. The specific reason is policy synchronization depends on agent reachability and can lag even when configuration itself is valid. The applicable verification is “The endpoint reconnects and receives the unchanged approved policy without speculative policy edits”.

Question 401

At fictional Harbor Arts, an endpoint security engineer responsible for visitor systems is reviewing EMS, endpoint and secure-access troubleshooting during a security policy acceptance test (FCT-7.4-4.1-101). The observed endpoint management issue is: An administrator sees an empty threat event report and concludes all devices are clean without confirming malware modules are active. Which corrective engineering action best addresses the specific problem?

  1. Compare FortiClient Web Filter results with gateway firewall or application events for the same request.
  2. Use the supported EMS host diagnostic and service logs or CLI tools to investigate the failed management interface.
  3. Inspect installed protection modules, profile activation and event ingestion before assessing the apparent absence of incidents.
  4. Inspect host capacity, concurrent deployment load and application service logs before choosing a disruptive repair.

Explanation

Correct Answer

C:

The targeted correction is to inspect installed protection modules, profile activation and event ingestion before assessing the apparent absence of incidents. The diagnosed issue is: An administrator sees an empty threat event report and concludes all devices are clean without confirming malware modules are active. Evidence of success is: A controlled test on an authorized pilot generates a corresponding protection event in monitoring. The underlying endpoint-security principle is that monitoring conclusions require complete sources and healthy telemetry, not merely a blank report.

Incorrect Answers

A:

“Compare FortiClient Web Filter results with gateway firewall or application events for the same request” would address a different implementation objective; the stated problem is an administrator sees an empty threat event report and concludes all devices are clean without confirming malware modules are active. The actual control boundary is monitoring conclusions require complete sources and healthy telemetry, not merely a blank report. The directly responsive action is “Inspect installed protection modules, profile activation and event ingestion before assessing the apparent absence of incidents”.

B:

“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 administrator sees an empty threat event report and concludes all devices are clean without confirming malware modules are active. The actual control boundary is monitoring conclusions require complete sources and healthy telemetry, not merely a blank report. The directly responsive action is “Inspect installed protection modules, profile activation and event ingestion before assessing the apparent absence of incidents”.

D:

“Inspect host capacity, concurrent deployment load and application service logs before choosing a disruptive repair” would address a different implementation objective; the stated problem is an administrator sees an empty threat event report and concludes all devices are clean without confirming malware modules are active. The actual control boundary is monitoring conclusions require complete sources and healthy telemetry, not merely a blank report. The directly responsive action is “Inspect installed protection modules, profile activation and event ingestion before assessing the apparent absence of incidents”.

Question 402

At fictional Harbor Arts, an endpoint security engineer responsible for visitor systems is reviewing EMS, endpoint and secure-access troubleshooting during a security policy acceptance test (FCT-7.4-4.1-101). The observed endpoint management issue is: An administrator sees an empty threat event report and concludes all devices are clean without confirming malware modules are active. Which recurring preventive or detective safeguard would best reduce recurrence?

  1. Monitor last agent check-in and policy application timestamps together.
  2. Audit telemetry coverage, enabled modules and event freshness each reporting period.
  3. Review access, retention and sharing of EMS and FortiClient support bundles.
  4. Include agent connection and certificate status in protected application support checklists.

Explanation

Correct Answer

B:

The recurring safeguard is to audit telemetry coverage, enabled modules and event freshness each reporting period. It mitigates the actual failure: An administrator sees an empty threat event report and concludes all devices are clean without confirming malware modules are active. A suitable correction is to inspect installed protection modules, profile activation and event ingestion before assessing the apparent absence of incidents; its proof is that a controlled test on an authorized pilot generates a corresponding protection event in monitoring.

Incorrect Answers

A:

“Monitor last agent check-in and policy application timestamps together” checks a different ongoing risk rather than the reported failure: an administrator sees an empty threat event report and concludes all devices are clean without confirming malware modules are active. The relevant mechanism is monitoring conclusions require complete sources and healthy telemetry, not merely a blank report. The directly matched preventive control is “Audit telemetry coverage, enabled modules and event freshness each reporting period”.

C:

“Review access, retention and sharing of EMS and FortiClient support bundles” checks a different ongoing risk rather than the reported failure: an administrator sees an empty threat event report and concludes all devices are clean without confirming malware modules are active. The relevant mechanism is monitoring conclusions require complete sources and healthy telemetry, not merely a blank report. The directly matched preventive control is “Audit telemetry coverage, enabled modules and event freshness each reporting period”.

D:

“Include agent connection and certificate status in protected application support checklists” checks a different ongoing risk rather than the reported failure: an administrator sees an empty threat event report and concludes all devices are clean without confirming malware modules are active. The relevant mechanism is monitoring conclusions require complete sources and healthy telemetry, not merely a blank report. The directly matched preventive control is “Audit telemetry coverage, enabled modules and event freshness each reporting period”.

Question 403

At fictional Harbor Arts, an endpoint security engineer responsible for visitor systems is reviewing EMS, endpoint and secure-access troubleshooting during a security policy acceptance test (FCT-7.4-4.1-101). The observed endpoint management issue is: An administrator sees an empty threat event report and concludes all devices are clean without confirming malware modules are active. Which observation best verifies that the proposed correction worked?

  1. The expected device identity and authorized ZTNA handshake are restored after connection prerequisites are met.
  2. FortiClient data traffic succeeds while a separate management endpoint connection is identified as failing.
  3. A controlled test on an authorized pilot generates a corresponding protection event in monitoring.
  4. The support bundle contains relevant device logs under access controls without unrelated personal records.

Explanation

Correct Answer

C:

This is the direct verification evidence: A controlled test on an authorized pilot generates a corresponding protection event in monitoring. It supports the engineering change to inspect installed protection modules, profile activation and event ingestion before assessing the apparent absence of incidents. The relevant principle is that monitoring conclusions require complete sources and healthy telemetry, not merely a blank report.

Incorrect Answers

A:

Evidence that “The expected device identity and authorized ZTNA handshake are restored after connection prerequisites are met” occurred would not by itself establish resolution of the reported problem: an administrator sees an empty threat event report and concludes all devices are clean without confirming malware modules are active. The specific reason is monitoring conclusions require complete sources and healthy telemetry, not merely a blank report. The applicable verification is “A controlled test on an authorized pilot generates a corresponding protection event in monitoring”.

B:

Evidence that “FortiClient data traffic succeeds while a separate management endpoint connection is identified as failing” occurred would not by itself establish resolution of the reported problem: an administrator sees an empty threat event report and concludes all devices are clean without confirming malware modules are active. The specific reason is monitoring conclusions require complete sources and healthy telemetry, not merely a blank report. The applicable verification is “A controlled test on an authorized pilot generates a corresponding protection event in monitoring”.

D:

Evidence that “The support bundle contains relevant device logs under access controls without unrelated personal records” occurred would not by itself establish resolution of the reported problem: an administrator sees an empty threat event report and concludes all devices are clean without confirming malware modules are active. The specific reason is monitoring conclusions require complete sources and healthy telemetry, not merely a blank report. The applicable verification is “A controlled test on an authorized pilot generates a corresponding protection event in monitoring”.

Question 404

At fictional Harbor Arts, an endpoint security engineer responsible for visitor systems is reviewing EMS, endpoint and secure-access troubleshooting during a security policy acceptance test (FCT-7.4-4.1-101). The observed endpoint management issue is: An administrator sees an empty threat event report and concludes all devices are clean without confirming malware modules are active. Which endpoint-management or security principle best explains the proper response?

  1. TLS authentication can fail due to client time or certificate validity independent of identity credentials.
  2. Multi-stage endpoint provisioning produces distinct failure points that require targeted diagnostics.
  3. Security access should require positively evaluated current posture, not an assumption from missing events.
  4. Monitoring conclusions require complete sources and healthy telemetry, not merely a blank report.

Explanation

Correct Answer

D:

The governing principle is: Monitoring conclusions require complete sources and healthy telemetry, not merely a blank report. Here the appropriate correction is to inspect installed protection modules, profile activation and event ingestion before assessing the apparent absence of incidents. Confirmation would be that a controlled test on an authorized pilot generates a corresponding protection event in monitoring.

Incorrect Answers

A:

“TLS authentication can fail due to client time or certificate validity independent of identity credentials” is not the controlling explanation for an administrator sees an empty threat event report and concludes all devices are clean without confirming malware modules are active. The cited causal relationship is monitoring conclusions require complete sources and healthy telemetry, not merely a blank report. The matching answer is “Monitoring conclusions require complete sources and healthy telemetry, not merely a blank report”.

B:

“Multi-stage endpoint provisioning produces distinct failure points that require targeted diagnostics” is not the controlling explanation for an administrator sees an empty threat event report and concludes all devices are clean without confirming malware modules are active. The cited causal relationship is monitoring conclusions require complete sources and healthy telemetry, not merely a blank report. The matching answer is “Monitoring conclusions require complete sources and healthy telemetry, not merely a blank report”.

C:

“Security access should require positively evaluated current posture, not an assumption from missing events” is not the controlling explanation for an administrator sees an empty threat event report and concludes all devices are clean without confirming malware modules are active. The cited causal relationship is monitoring conclusions require complete sources and healthy telemetry, not merely a blank report. The matching answer is “Monitoring conclusions require complete sources and healthy telemetry, not merely a blank report”.

Question 405

At fictional Oakridge Energy, an endpoint security engineer responsible for operations consoles is reviewing EMS, endpoint and secure-access troubleshooting during a remote access rollout (FCT-7.4-4.2-102). The observed endpoint management issue is: A FortiGate administrator receives no dynamic posture tags because the EMS Fabric connector is reachable but not approved. Which observation best verifies that the proposed correction worked?

  1. The missing tag is traced to a rule mismatch and returns after approved condition correction.
  2. The server handles staged registrations with acceptable resource levels and no destructive reset.
  3. FortiGate displays the expected current EMS posture tag objects after the connector is approved.
  4. Monitoring searches and client telemetry recover after approved server resource remediation.

Explanation

Correct Answer

C:

This is the direct verification evidence: FortiGate displays the expected current EMS posture tag objects after the connector is approved. It supports the engineering change to complete device authorization and verify subsequent tag synchronization without disabling policy enforcement. The relevant principle is that authorization state can prevent synchronization despite healthy network transport.

Incorrect Answers

A:

Evidence that “The missing tag is traced to a rule mismatch and returns after approved condition correction” occurred would not by itself establish resolution of the reported problem: a FortiGate administrator receives no dynamic posture tags because the EMS Fabric connector is reachable but not approved. The specific reason is authorization state can prevent synchronization despite healthy network transport. The applicable verification is “FortiGate displays the expected current EMS posture tag objects after the connector is approved”.

B:

Evidence that “The server handles staged registrations with acceptable resource levels and no destructive reset” occurred would not by itself establish resolution of the reported problem: a FortiGate administrator receives no dynamic posture tags because the EMS Fabric connector is reachable but not approved. The specific reason is authorization state can prevent synchronization despite healthy network transport. The applicable verification is “FortiGate displays the expected current EMS posture tag objects after the connector is approved”.

D:

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 FortiGate administrator receives no dynamic posture tags because the EMS Fabric connector is reachable but not approved. The specific reason is authorization state can prevent synchronization despite healthy network transport. The applicable verification is “FortiGate displays the expected current EMS posture tag objects after the connector is approved”.

Question 406

At fictional Oakridge Energy, an endpoint security engineer responsible for operations consoles is reviewing EMS, endpoint and secure-access troubleshooting during a remote access rollout (FCT-7.4-4.2-102). The observed endpoint management issue is: A FortiGate administrator receives no dynamic posture tags because the EMS Fabric connector is reachable but not approved. Which endpoint-management or security principle best explains the proper response?

  1. Policy distribution is constrained by actual endpoint check-in and client reachability.
  2. Trusted certificate identity must follow the advertised management server name.
  3. Security access should require positively evaluated current posture, not an assumption from missing events.
  4. Authorization state can prevent synchronization despite healthy network transport.

Explanation

Correct Answer

D:

The governing principle is: Authorization state can prevent synchronization despite healthy network transport. Here the appropriate correction is to complete device authorization and verify subsequent tag synchronization without disabling policy enforcement. Confirmation would be that fortiGate displays the expected current EMS posture tag objects after the connector is approved.

Incorrect Answers

A:

“Policy distribution is constrained by actual endpoint check-in and client reachability” is not the controlling explanation for a FortiGate administrator receives no dynamic posture tags because the EMS Fabric connector is reachable but not approved. The cited causal relationship is authorization state can prevent synchronization despite healthy network transport. The matching answer is “Authorization state can prevent synchronization despite healthy network transport”.

B:

“Trusted certificate identity must follow the advertised management server name” is not the controlling explanation for a FortiGate administrator receives no dynamic posture tags because the EMS Fabric connector is reachable but not approved. The cited causal relationship is authorization state can prevent synchronization despite healthy network transport. The matching answer is “Authorization state can prevent synchronization despite healthy network transport”.

C:

“Security access should require positively evaluated current posture, not an assumption from missing events” is not the controlling explanation for a FortiGate administrator receives no dynamic posture tags because the EMS Fabric connector is reachable but not approved. The cited causal relationship is authorization state can prevent synchronization despite healthy network transport. The matching answer is “Authorization state can prevent synchronization despite healthy network transport”.

Question 407

At fictional Oakridge Energy, an endpoint security engineer responsible for operations consoles is reviewing EMS, endpoint and secure-access troubleshooting during a remote access rollout (FCT-7.4-4.2-102). The observed endpoint management issue is: A FortiGate administrator receives no dynamic posture tags because the EMS Fabric connector is reachable but not approved. Which recurring preventive or detective safeguard would best reduce recurrence?

  1. Review mutual Fabric connector approval after new firewall onboarding.
  2. Trend EMS host capacity and alert before database storage limits are reached.
  3. Add EMS transport to the documented required-communications acceptance matrix.
  4. Reconcile required profile features against installed modules during each software rollout.

Explanation

Correct Answer

A:

The recurring safeguard is to review mutual Fabric connector approval after new firewall onboarding. It mitigates the actual failure: A FortiGate administrator receives no dynamic posture tags because the EMS Fabric connector is reachable but not approved. A suitable correction is to complete device authorization and verify subsequent tag synchronization without disabling policy enforcement; its proof is that fortiGate displays the expected current EMS posture tag objects after the connector is approved.

Incorrect Answers

B:

“Trend EMS host capacity and alert before database storage limits are reached” checks a different ongoing risk rather than the reported failure: a FortiGate administrator receives no dynamic posture tags because the EMS Fabric connector is reachable but not approved. The relevant mechanism is authorization state can prevent synchronization despite healthy network transport. The directly matched preventive control is “Review mutual Fabric connector approval after new firewall onboarding”.

C:

“Add EMS transport to the documented required-communications acceptance matrix” checks a different ongoing risk rather than the reported failure: a FortiGate administrator receives no dynamic posture tags because the EMS Fabric connector is reachable but not approved. The relevant mechanism is authorization state can prevent synchronization despite healthy network transport. The directly matched preventive control is “Review mutual Fabric connector approval after new firewall onboarding”.

D:

“Reconcile required profile features against installed modules during each software rollout” checks a different ongoing risk rather than the reported failure: a FortiGate administrator receives no dynamic posture tags because the EMS Fabric connector is reachable but not approved. The relevant mechanism is authorization state can prevent synchronization despite healthy network transport. The directly matched preventive control is “Review mutual Fabric connector approval after new firewall onboarding”.

Question 408

At fictional Oakridge Energy, an endpoint security engineer responsible for operations consoles is reviewing EMS, endpoint and secure-access troubleshooting during a remote access rollout (FCT-7.4-4.2-102). The observed endpoint management issue is: A FortiGate administrator receives no dynamic posture tags because the EMS Fabric connector is reachable but not approved. 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. Correlate directory synchronization status, group mapping and current registered device evidence before making deletions.
  3. Use a supported authorized software distribution method with sufficient endpoint installation permissions.
  4. Complete device authorization and verify subsequent tag synchronization without disabling policy enforcement.

Explanation

Correct Answer

D:

The targeted correction is to complete device authorization and verify subsequent tag synchronization without disabling policy enforcement. The diagnosed issue is: A FortiGate administrator receives no dynamic posture tags because the EMS Fabric connector is reachable but not approved. Evidence of success is: FortiGate displays the expected current EMS posture tag objects after the connector is approved. The underlying endpoint-security principle is that authorization state can prevent synchronization despite healthy network transport.

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 a FortiGate administrator receives no dynamic posture tags because the EMS Fabric connector is reachable but not approved. The actual control boundary is authorization state can prevent synchronization despite healthy network transport. The directly responsive action is “Complete device authorization and verify subsequent tag synchronization without disabling policy enforcement”.

B:

“Correlate directory synchronization status, group mapping and current registered device evidence before making deletions” would address a different implementation objective; the stated problem is a FortiGate administrator receives no dynamic posture tags because the EMS Fabric connector is reachable but not approved. The actual control boundary is authorization state can prevent synchronization despite healthy network transport. The directly responsive action is “Complete device authorization and verify subsequent tag synchronization without disabling policy enforcement”.

C:

“Use a supported authorized software distribution method with sufficient endpoint installation permissions” would address a different implementation objective; the stated problem is a FortiGate administrator receives no dynamic posture tags because the EMS Fabric connector is reachable but not approved. The actual control boundary is authorization state can prevent synchronization despite healthy network transport. The directly responsive action is “Complete device authorization and verify subsequent tag synchronization without disabling policy enforcement”.

Question 409

At fictional Zenith Tourism, an endpoint security engineer responsible for visitor kiosks is reviewing endpoint provisioning, security modules and profile delivery during a server maintenance validation (FCT-7.4-2.1-103). The observed endpoint management issue is: A branch uses a single installation command across unmanaged personal machines without obtaining device enrollment approval. Which observation best verifies that the proposed correction worked?

  1. Each target endpoint reports a completed client installation and current EMS connection.
  2. Managed endpoints show timely protection intelligence updates and no persistent update failures.
  3. Authorized devices register under the intended group while unapproved devices do not gain managed access.
  4. Pilot devices finish the upgrade with the intended modules, registration and assigned profiles intact.

Explanation

Correct Answer

C:

This is the direct verification evidence: Authorized devices register under the intended group while unapproved devices do not gain managed access. It supports the engineering change to use a supported invitation or approved device onboarding process with identity and authorization checks. The relevant principle is that endpoint registration should represent approved device ownership and enrollment rather than arbitrary installer execution.

Incorrect Answers

A:

Evidence that “Each target endpoint reports a completed client installation and current EMS connection” occurred would not by itself establish resolution of the reported problem: a branch uses a single installation command across unmanaged personal machines without obtaining device enrollment approval. The specific reason is endpoint registration should represent approved device ownership and enrollment rather than arbitrary installer execution. The applicable verification is “Authorized devices register under the intended group while unapproved devices do not gain managed access”.

B:

Evidence that “Managed endpoints show timely protection intelligence updates and no persistent update failures” occurred would not by itself establish resolution of the reported problem: a branch uses a single installation command across unmanaged personal machines without obtaining device enrollment approval. The specific reason is endpoint registration should represent approved device ownership and enrollment rather than arbitrary installer execution. The applicable verification is “Authorized devices register under the intended group while unapproved devices do not gain managed access”.

D:

Evidence that “Pilot devices finish the upgrade with the intended modules, registration and assigned profiles intact” occurred would not by itself establish resolution of the reported problem: a branch uses a single installation command across unmanaged personal machines without obtaining device enrollment approval. The specific reason is endpoint registration should represent approved device ownership and enrollment rather than arbitrary installer execution. The applicable verification is “Authorized devices register under the intended group while unapproved devices do not gain managed access”.

Question 410

At fictional Zenith Tourism, an endpoint security engineer responsible for visitor kiosks is reviewing endpoint provisioning, security modules and profile delivery during a server maintenance validation (FCT-7.4-2.1-103). The observed endpoint management issue is: A branch uses a single installation command across unmanaged personal machines without obtaining device enrollment approval. Which recurring preventive or detective safeguard would best reduce recurrence?

  1. Audit new endpoint registrations against procurement and authorization records.
  2. Test representative allowed and denied categories after policy publishing.
  3. Revalidate embedded EMS registration values whenever management service names change.
  4. Review inherited and customized profile differences before promoting laboratory settings.

Explanation

Correct Answer

A:

The recurring safeguard is to audit new endpoint registrations against procurement and authorization records. It mitigates the actual failure: A branch uses a single installation command across unmanaged personal machines without obtaining device enrollment approval. A suitable correction is to use a supported invitation or approved device onboarding process with identity and authorization checks; its proof is that authorized devices register under the intended group while unapproved devices do not gain managed access.

Incorrect Answers

B:

“Test representative allowed and denied categories after policy publishing” checks a different ongoing risk rather than the reported failure: a branch uses a single installation command across unmanaged personal machines without obtaining device enrollment approval. The relevant mechanism is endpoint registration should represent approved device ownership and enrollment rather than arbitrary installer execution. The directly matched preventive control is “Audit new endpoint registrations against procurement and authorization records”.

C:

“Revalidate embedded EMS registration values whenever management service names change” checks a different ongoing risk rather than the reported failure: a branch uses a single installation command across unmanaged personal machines without obtaining device enrollment approval. The relevant mechanism is endpoint registration should represent approved device ownership and enrollment rather than arbitrary installer execution. The directly matched preventive control is “Audit new endpoint registrations against procurement and authorization records”.

D:

“Review inherited and customized profile differences before promoting laboratory settings” checks a different ongoing risk rather than the reported failure: a branch uses a single installation command across unmanaged personal machines without obtaining device enrollment approval. The relevant mechanism is endpoint registration should represent approved device ownership and enrollment rather than arbitrary installer execution. The directly matched preventive control is “Audit new endpoint registrations against procurement and authorization records”.

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