Question 110
At fictional Cedar Stores, an endpoint security engineer responsible for retail workstations is reviewing endpoint provisioning, security modules and profile delivery during a supervised production migration (FCT-7.4-2.1-028). The observed endpoint management issue is: A clinic deploys endpoint protection through an operating system software tool but never installs the telemetry component needed for EMS onboarding. Which recurring preventive or detective safeguard would best reduce recurrence?
Explanation
Correct Answer
The recurring safeguard is to compare package feature sets, registration and applied policy in installation acceptance. It mitigates the actual failure: A clinic deploys endpoint protection through an operating system software tool but never installs the telemetry component needed for EMS onboarding. A suitable correction is to confirm the FortiClient installed feature selection and supported connection-registration prerequisites; its proof is that the managed device appears in EMS and receives endpoint policy rather than only local software.
Incorrect Answers
“Validate installed module inventory on a pilot device before campus rollout” checks a different ongoing risk rather than the reported failure: a clinic deploys endpoint protection through an operating system software tool but never installs the telemetry component needed for EMS onboarding. The relevant mechanism is software distribution and activation of EMS-managed endpoint telemetry are related but separate stages. The directly matched preventive control is “Compare package feature sets, registration and applied policy in installation acceptance”.
“Maintain an operating-system compatibility inventory for all remote deployment packages” checks a different ongoing risk rather than the reported failure: a clinic deploys endpoint protection through an operating system software tool but never installs the telemetry component needed for EMS onboarding. The relevant mechanism is software distribution and activation of EMS-managed endpoint telemetry are related but separate stages. The directly matched preventive control is “Compare package feature sets, registration and applied policy in installation acceptance”.
“Reconcile pending software jobs with installed-agent telemetry during each rollout wave” checks a different ongoing risk rather than the reported failure: a clinic deploys endpoint protection through an operating system software tool but never installs the telemetry component needed for EMS onboarding. The relevant mechanism is software distribution and activation of EMS-managed endpoint telemetry are related but separate stages. The directly matched preventive control is “Compare package feature sets, registration and applied policy in installation acceptance”.