Question 20
At fictional Juniper Publishing, an endpoint security engineer responsible for hybrid staff is reviewing endpoint provisioning, security modules and profile delivery during a device support triage (FCT-7.4-2.1-005). The observed endpoint management issue is: An administrator installs a new agent over an existing client without examining whether selected modules and configuration survive an upgrade. Which recurring preventive or detective safeguard would best reduce recurrence?
Explanation
Correct Answer
The recurring safeguard is to include before-and-after agent version, registration and module checks in upgrade gates. It mitigates the actual failure: An administrator installs a new agent over an existing client without examining whether selected modules and configuration survive an upgrade. A suitable correction is to use the supported FortiClient upgrade package and test retained management configuration before mass deployment; its proof is that pilot devices finish the upgrade with the intended modules, registration and assigned profiles intact.
Incorrect Answers
“Track vulnerability-to-remediation closure using repeated scans and change evidence” checks a different ongoing risk rather than the reported failure: an administrator installs a new agent over an existing client without examining whether selected modules and configuration survive an upgrade. The relevant mechanism is endpoint upgrade workflows must account for existing client state and module compatibility. The directly matched preventive control is “Include before-and-after agent version, registration and module checks in upgrade gates”.
“Reconcile installed security agent status with EMS registrations and removal approvals” checks a different ongoing risk rather than the reported failure: an administrator installs a new agent over an existing client without examining whether selected modules and configuration survive an upgrade. The relevant mechanism is endpoint upgrade workflows must account for existing client state and module compatibility. The directly matched preventive control is “Include before-and-after agent version, registration and module checks in upgrade gates”.
“Maintain an operating-system compatibility inventory for all remote deployment packages” checks a different ongoing risk rather than the reported failure: an administrator installs a new agent over an existing client without examining whether selected modules and configuration survive an upgrade. The relevant mechanism is endpoint upgrade workflows must account for existing client state and module compatibility. The directly matched preventive control is “Include before-and-after agent version, registration and module checks in upgrade gates”.